Post here the ping times to your gateway Page 2

Author

All Replies

pheebau

join:2001-12-12
El Cerrito, CA

reply to ChuC
Re: Post here the ping times to your gateway

The usual...bad...and at midnight...

Pinging 12.233.156.1 with 32 bytes of data:

Reply from 12.233.156.1: bytes=32 time=160ms TTL=255
Reply from 12.233.156.1: bytes=32 time=128ms TTL=255
Reply from 12.233.156.1: bytes=32 time=254ms TTL=255
Reply from 12.233.156.1: bytes=32 time=40ms TTL=255
Reply from 12.233.156.1: bytes=32 time=81ms TTL=255
Reply from 12.233.156.1: bytes=32 time=359ms TTL=255
Reply from 12.233.156.1: bytes=32 time=137ms TTL=255
Reply from 12.233.156.1: bytes=32 time=25ms TTL=255
Reply from 12.233.156.1: bytes=32 time=145ms TTL=255
Reply from 12.233.156.1: bytes=32 time=136ms TTL=255
Reply from 12.233.156.1: bytes=32 time=73ms TTL=255
Reply from 12.233.156.1: bytes=32 time=243ms TTL=255
Reply from 12.233.156.1: bytes=32 time=172ms TTL=255
Reply from 12.233.156.1: bytes=32 time=135ms TTL=255
Reply from 12.233.156.1: bytes=32 time=191ms TTL=255
Reply from 12.233.156.1: bytes=32 time=326ms TTL=255
Reply from 12.233.156.1: bytes=32 time=164ms TTL=255
Reply from 12.233.156.1: bytes=32 time=326ms TTL=255
Reply from 12.233.156.1: bytes=32 time=386ms TTL=255
Reply from 12.233.156.1: bytes=32 time=343ms TTL=255
Reply from 12.233.156.1: bytes=32 time=139ms TTL=255
Reply from 12.233.156.1: bytes=32 time=337ms TTL=255
Reply from 12.233.156.1: bytes=32 time=240ms TTL=255
Reply from 12.233.156.1: bytes=32 time=147ms TTL=255
Reply from 12.233.156.1: bytes=32 time=39ms TTL=255
Reply from 12.233.156.1: bytes=32 time=226ms TTL=255
Reply from 12.233.156.1: bytes=32 time=192ms TTL=255
Reply from 12.233.156.1: bytes=32 time=221ms TTL=255
Reply from 12.233.156.1: bytes=32 time=222ms TTL=255
Reply from 12.233.156.1: bytes=32 time=120ms TTL=255
Reply from 12.233.156.1: bytes=32 time=268ms TTL=255
Reply from 12.233.156.1: bytes=32 time=219ms TTL=255
Reply from 12.233.156.1: bytes=32 time=201ms TTL=255
Reply from 12.233.156.1: bytes=32 time=172ms TTL=255
Reply from 12.233.156.1: bytes=32 time=134ms TTL=255
Reply from 12.233.156.1: bytes=32 time=145ms TTL=255
Reply from 12.233.156.1: bytes=32 time=203ms TTL=255
Reply from 12.233.156.1: bytes=32 time=195ms TTL=255
Reply from 12.233.156.1: bytes=32 time=141ms TTL=255
Reply from 12.233.156.1: bytes=32 time=218ms TTL=255
Reply from 12.233.156.1: bytes=32 time=34ms TTL=255
Reply from 12.233.156.1: bytes=32 time=42ms TTL=255
Reply from 12.233.156.1: bytes=32 time=163ms TTL=255
Reply from 12.233.156.1: bytes=32 time=141ms TTL=255

Ping statistics for 12.233.156.1:
Packets: Sent = 44, Received = 44, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 386ms, Average = 181ms

to forum · permalink · 2002-09-25 03:16:09 · (locked)

pheebau

join:2001-12-12
El Cerrito, CA

reply to ChuC
ChuC,

Good luck - I tried and am even talking to local tech everyday...always the same song...still nothing...headend is bad but everytime I ask precised questions, I get no answer and the local tier2 tell me they don't know much about what the headend people are doing - I also asked about the upstreams channel width 15 times and still have not gotten any answer...

if you want data, I can send you A LOT of data - I traced data for the last 4 weeks so I got some interesting ones for the bay area

Anyhow...Am so pissed-off and frustrated that my DSL will come soon...to give you some idea - all my friends with their DSL ping CONSTANTLY the same low value to my ATT gateway (even 1 friend in Oregon with a slow DSL gets good ping time...)...I think Cable is particular as the line is shared by everyone so it might work in a good day or if your neighborhood is not too crowded and then change all of a sudden dramatically overnight leaving you perplex about the thing...PM me if you wanna discuss/know more...

to forum · permalink · 2002-09-25 03:22:06 · (locked)

LarryE

join:2000-07-29
Chicago, IL

reply to ChuC
Thanks for your help in finding my gateway!

Ping statistics for 12.247.166.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 13ms, Average = 9ms

to forum · permalink · 2002-09-25 03:29:01 · (locked)

teck9

join:2002-05-02
Fort Lauderdale, FL

reply to ChuC
The best on here

Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=9ms TTL=255
Reply from 66.176.24.1: bytes=32 time=8ms TTL=255
Reply from 66.176.24.1: bytes=32 time=8ms TTL=255
Reply from 66.176.24.1: bytes=32 time=6ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=9ms TTL=255
Reply from 66.176.24.1: bytes=32 time=11ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255
Reply from 66.176.24.1: bytes=32 time=7ms TTL=255

Ping statistics for 66.176.24.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 11ms, Average = 7ms

to forum · permalink · 2002-09-25 13:17:54 · (locked)

13120635
Watching in silence
Premium
join:2001-01-03
Aurora, CO

reply to ChuC
Pinging gateway.attbi.com [63.240.76.6] with 32 bytes of data:

Reply from 63.240.76.6: bytes=32 time=63ms TTL=49
Reply from 63.240.76.6: bytes=32 time=66ms TTL=49
Reply from 63.240.76.6: bytes=32 time=64ms TTL=49
Reply from 63.240.76.6: bytes=32 time=64ms TTL=49

Ping statistics for 63.240.76.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 66ms, Average = 64ms

Okay I guess.

--
Put them in the iron maiden!

to forum · permalink · 2002-09-25 13:37:07 · (locked)

stevelee0

join:2002-03-27
Bellevue, WA

reply to ChuC
Pinging 12.230.159.1 with 32 bytes of data:

Ping statistics for 12.230.159.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 30ms, Average = 8ms

The current time is: 10:48:58.39 (PDT)

to forum · permalink · 2002-09-25 13:49:03 · (locked)

Holyearth
I Like This Forum

join:2002-07-18
Atlanta, GA

reply to pheebau
1:50 PM -- Atlanta, GA 30308

C:\>ping -n 10 10.238.136.1

Pinging 10.238.136.1 with 32 bytes of data:

Reply from 10.238.136.1: bytes=32 time=73ms TTL=255
Reply from 10.238.136.1: bytes=32 time=16ms TTL=255
Reply from 10.238.136.1: bytes=32 time=33ms TTL=255
Reply from 10.238.136.1: bytes=32 time=27ms TTL=255
Reply from 10.238.136.1: bytes=32 time=25ms TTL=255
Reply from 10.238.136.1: bytes=32 time=27ms TTL=255
Reply from 10.238.136.1: bytes=32 time=17ms TTL=255
Reply from 10.238.136.1: bytes=32 time=85ms TTL=255
Reply from 10.238.136.1: bytes=32 time=24ms TTL=255
Reply from 10.238.136.1: bytes=32 time=15ms TTL=255

Ping statistics for 10.238.136.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 85ms, Average = 34ms

to forum · permalink · 2002-09-25 13:50:48 · (locked)

blacey

join:2000-10-26
San Mateo, CA

reply to ChuC

As of Wed Sep 25 13:40:48 2002

[mac:~] blacey% ping -c 20 -i 5 attbi-gateway

--- ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 7.549/12.807/42.998 ms

[text was edited by author 2002-09-25 17:09:18]

to forum · permalink · 2002-09-25 16:46:51 · (locked)

rfisher4

join:2002-09-25
Santa Barbara, CA

reply to ChuC
Ping statistics for 10.216.96.1:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 1172ms, Average = 116ms

This is at 5:45 EDT, in Amherst, MA 01002

Unacceptable, as soon as I get a little cash togeather I will be switching to DSL.

to forum · permalink · 2002-09-25 17:52:25 · (locked)

cury19

join:2002-09-02
Weatogue, CT

reply to pheebau
Here's my pings.

Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=12ms TTL=255
Reply from 12.243.112.1: bytes=32 time=44ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=8ms TTL=255
Reply from 12.243.112.1: bytes=32 time=26ms TTL=255
Reply from 12.243.112.1: bytes=32 time=18ms TTL=255
Reply from 12.243.112.1: bytes=32 time=18ms TTL=255
Reply from 12.243.112.1: bytes=32 time=10ms TTL=255

Ping statistics for 12.243.112.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 44ms, Average = 16ms

to forum · permalink · 2002-09-25 19:08:30 · (locked)

DA OH
Do, Or Do Not. There Is No 'try'.

join:2002-01-07
Denver, CO
clubs:

reply to ChuC

code:


C:\>ping -n 10 12.253.156.1

Pinging 12.253.156.1 with 32 bytes of data:

Reply from 12.253.156.1: bytes=32 time=9ms TTL=254
Reply from 12.253.156.1: bytes=32 time=8ms TTL=254
Reply from 12.253.156.1: bytes=32 time=11ms TTL=254
Reply from 12.253.156.1: bytes=32 time=21ms TTL=254
Reply from 12.253.156.1: bytes=32 time=13ms TTL=254
Reply from 12.253.156.1: bytes=32 time=12ms TTL=254
Reply from 12.253.156.1: bytes=32 time=12ms TTL=254
Reply from 12.253.156.1: bytes=32 time=9ms TTL=254
Reply from 12.253.156.1: bytes=32 time=9ms TTL=254
Reply from 12.253.156.1: bytes=32 time=9ms TTL=254

Ping statistics for 12.253.156.1:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 21ms, Average = 11ms

C:\>

Lakewood, CO 8:16 PM
[text was edited by author 2002-09-25 22:18:23]

to forum · permalink · 2002-09-25 22:16:55 · (locked)

RandoCal

join:2002-08-26
Seattle, WA

reply to ChuC
C:\>ping 12.242.16.34 -t

Pinging 12.242.16.34 with 32 bytes of data:

Reply from 12.242.16.34: bytes=32 time=184ms TTL=249
Reply from 12.242.16.34: bytes=32 time=86ms TTL=249
Reply from 12.242.16.34: bytes=32 time=128ms TTL=249
Reply from 12.242.16.34: bytes=32 time=259ms TTL=249
Reply from 12.242.16.34: bytes=32 time=331ms TTL=249
Reply from 12.242.16.34: bytes=32 time=212ms TTL=249
Reply from 12.242.16.34: bytes=32 time=231ms TTL=249
Reply from 12.242.16.34: bytes=32 time=204ms TTL=249
Reply from 12.242.16.34: bytes=32 time=343ms TTL=249
Reply from 12.242.16.34: bytes=32 time=227ms TTL=249
Request timed out.
Reply from 12.242.16.34: bytes=32 time=334ms TTL=249
Reply from 12.242.16.34: bytes=32 time=184ms TTL=249
Reply from 12.242.16.34: bytes=32 time=466ms TTL=249
Reply from 12.242.16.34: bytes=32 time=221ms TTL=249
Reply from 12.242.16.34: bytes=32 time=153ms TTL=249
Reply from 12.242.16.34: bytes=32 time=272ms TTL=249
Reply from 12.242.16.34: bytes=32 time=276ms TTL=249
Reply from 12.242.16.34: bytes=32 time=237ms TTL=249
Reply from 12.242.16.34: bytes=32 time=50ms TTL=249

Ping statistics for 12.242.16.34:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 466ms, Average = 231ms

This is Seattle @ 7:45pm

to forum · permalink · 2002-09-25 22:43:19 · (locked)

KenInSac

join:2002-06-28
Folsom, CA

reply to ChuC
Ping statistics for 12.246.0.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 210ms, Average = 45ms

(This was the worst of 5 runs; the best was Average = 14ms)

to forum · permalink · 2002-09-25 22:45:05 · (locked)

USA Zombie
Premium
join:2002-08-22
Seattle, WA

reply to ChuC
Pinging 12.231.18.1 with 32 bytes of data:

Reply from 12.231.18.1: bytes=32 time=370ms TTL=255
Reply from 12.231.18.1: bytes=32 time=219ms TTL=255
Reply from 12.231.18.1: bytes=32 time=345ms TTL=255
Reply from 12.231.18.1: bytes=32 time=182ms TTL=255
Reply from 12.231.18.1: bytes=32 time=250ms TTL=255
Reply from 12.231.18.1: bytes=32 time=436ms TTL=255
Reply from 12.231.18.1: bytes=32 time=226ms TTL=255
Reply from 12.231.18.1: bytes=32 time=530ms TTL=255
Reply from 12.231.18.1: bytes=32 time=239ms TTL=255
Reply from 12.231.18.1: bytes=32 time=182ms TTL=255

Ping statistics for 12.231.18.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 182ms, Maximum = 530ms, Average = 297ms

7:47 PM 9/25/2002-Seattle

to forum · permalink · 2002-09-25 22:50:05 · (locked)

SlyBry
Slyest Of All The Brys
Premium
join:2002-08-26
Manchester, NH

reply to teck9

said by teck9 :
The best on here

Correction.... you were. =)

Pinging 24.147.72.1 with 32 bytes of data:

Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=2ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255
Reply from 24.147.72.1: bytes=32 time=4ms TTL=255
Reply from 24.147.72.1: bytes=32 time=3ms TTL=255

Ping statistics for 24.147.72.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4ms, Average = 3ms

to forum · permalink · 2002-09-26 01:17:20 · (locked)

djk
Premium
join:2000-11-05
Grapevine, TX

·Verizon FIOS

reply to ChuC
Not too bad :)

C:\>ping -n 10 12.238.232.1

Pinging 12.238.232.1 with 32 bytes of data:

Reply from 12.238.232.1: bytes=32 time=10ms TTL=255
Reply from 12.238.232.1: bytes=32 time10ms TTL=255
Reply from 12.238.232.1: bytes=32 time10ms TTL=255
Reply from 12.238.232.1: bytes=32 time10ms TTL=255
Reply from 12.238.232.1: bytes=32 time10ms TTL=255
Reply from 12.238.232.1: bytes=32 time=10ms TTL=255
Reply from 12.238.232.1: bytes=32 time=10ms TTL=255
Reply from 12.238.232.1: bytes=32 time=10ms TTL=255
Reply from 12.238.232.1: bytes=32 time=10ms TTL=255
Reply from 12.238.232.1: bytes=32 time=10ms TTL=255

Ping statistics for 12.238.232.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 6ms

to forum · permalink · 2002-09-26 02:40:54 · (locked)

ki1o
Premium
join:2001-04-12
Atlanta, GA

reply to ChuC
Re: Post here the ping times to your gateway

I'm in Atlanta, and they FINALLY fixed the request time out problem with my gateway.

Pinging 24.98.136.1 with 32 bytes of data:

Reply from 24.98.136.1: bytes=32 time=10ms TTL=255
Reply from 24.98.136.1: bytes=32 time=10ms TTL=255
Reply from 24.98.136.1: bytes=32 time=10ms TTL=255
Reply from 24.98.136.1: bytes=32 time=10ms TTL=255

Ping statistics for 24.98.136.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 7ms

to forum · permalink · 2002-09-26 03:02:04 · (locked)

Dimspyder

join:2002-09-13
Portland, OR

reply to ChuC
--- 12.231.244.1 ping statistics ---
3336 packets transmitted, 3245 packets received, 2% packet loss
round-trip min/avg/max/std-dev = 8.324/182.949/4341.463/285.997 ms

As you can see, a couple were over 4 seconds, and a couple timed out, hence the 2% packet loss. My connection has been down 2 times tonight as well, for about a total of 1 hour. This was from earlier, at around 10pm in Portland, Oregon (97229).

to forum · permalink · 2002-09-26 03:33:40 · (locked)

SitFlyer

join:2001-12-21
Pittsburg, CA

Ping statistics for 12.233.117.129:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 40ms, Average = 14ms

[text was edited by author 2002-09-26 13:05:46]

to forum · permalink · 2002-09-26 13:05:01 · (locked)

deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE

reply to ChuC
This is what I get on DSL. Granted, they're higher than the minimum most people get on ATTBI, but they're consistently low which is what is more important to me.

floyd:~$ ping -c 10 gw
PING gw (168.150.236.1): 56 data bytes
64 bytes from 168.150.236.1: icmp_seq=0 ttl=64 time=34.9 ms
64 bytes from 168.150.236.1: icmp_seq=1 ttl=64 time=24.1 ms
64 bytes from 168.150.236.1: icmp_seq=2 ttl=64 time=23.6 ms
64 bytes from 168.150.236.1: icmp_seq=3 ttl=64 time=22.9 ms
64 bytes from 168.150.236.1: icmp_seq=4 ttl=64 time=23.5 ms
64 bytes from 168.150.236.1: icmp_seq=5 ttl=64 time=23.1 ms
64 bytes from 168.150.236.1: icmp_seq=6 ttl=64 time=23.4 ms
64 bytes from 168.150.236.1: icmp_seq=7 ttl=64 time=23.2 ms
64 bytes from 168.150.236.1: icmp_seq=8 ttl=64 time=23.3 ms
64 bytes from 168.150.236.1: icmp_seq=9 ttl=64 time=22.8 ms

--- gw ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 22.8/24.4/34.9 ms
--
"I drank what?" -Socrates

to forum · permalink · 2002-09-26 18:00:49 · (locked)


Wednesday, 09-Dec 17:50:24	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com. page compression OFF