  dsaliem Arrested Development Premium join:2002-07-17 Visalia, CA
| reply to ChuC Re: Post here the ping times to your gateway
Here is the ping time to attbi gateway @ IP 10.242.240.1
C:\>ping -n 10 10.242.240.1
Pinging 10.242.240.1 with 32 bytes of data:
Reply from 10.242.240.1: bytes=32 time=11ms TTL=255 Reply from 10.242.240.1: bytes=32 time=9ms TTL=255 Reply from 10.242.240.1: bytes=32 time=10ms TTL=255 Reply from 10.242.240.1: bytes=32 time=10ms TTL=255 Reply from 10.242.240.1: bytes=32 time=8ms TTL=255 Reply from 10.242.240.1: bytes=32 time=11ms TTL=255 Reply from 10.242.240.1: bytes=32 time=10ms TTL=255 Reply from 10.242.240.1: bytes=32 time=12ms TTL=255 Reply from 10.242.240.1: bytes=32 time=26ms TTL=255 Reply from 10.242.240.1: bytes=32 time=11ms TTL=255
Ping statistics for 10.242.240.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 26ms, Average = 11ms
C:\>time The current time is: 14:08:53.65 Visalia, CA [text was edited by author 2002-09-30 19:47:48]
[text was edited by author 2002-09-30 19:49:49] |
|
 cury19
join:2002-09-02 Weatogue, CT
| reply to ChuC Pinging 12.243.112.1 with 32 bytes of data:
Reply from 12.243.112.1: bytes=32 time=24ms TTL=255 Reply from 12.243.112.1: bytes=32 time=8ms TTL=255 Reply from 12.243.112.1: bytes=32 time=9ms TTL=255 Reply from 12.243.112.1: bytes=32 time=11ms TTL=255 Reply from 12.243.112.1: bytes=32 time=7ms TTL=255 Reply from 12.243.112.1: bytes=32 time=12ms TTL=255 Reply from 12.243.112.1: bytes=32 time=10ms TTL=255 Reply from 12.243.112.1: bytes=32 time=10ms TTL=255 Reply from 12.243.112.1: bytes=32 time=11ms 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 = 7ms, Maximum = 24ms, Average = 11ms |
|
  airwingjim Euclid314 Premium join:2001-08-05 Denver, CO | reply to ChuC »/quality/nil/875720 |
|
 pheebau
join:2001-12-12 El Cerrito, CA
| reply to ChuC Wow - el cerrito, ca - Monday 3am 
Something must have happened!
Pinging 12.233.156.1 with 32 bytes of data:
Reply from 12.233.156.1: bytes=32 time=9ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=9ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=12ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=19ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=15ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=12ms TTL=255 Reply from 12.233.156.1: bytes=32 time=15ms TTL=255 Reply from 12.233.156.1: bytes=32 time=9ms TTL=255 Reply from 12.233.156.1: bytes=32 time=24ms TTL=255
Ping statistics for 12.233.156.1: Packets: Sent = 27, Received = 27, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 24ms, Average = 11ms |
|
  INHCNN
join:2001-12-15 Lansing, MI
| reply to ChuC Pinging 12.245.205.1 with 32 bytes of data:
Reply from 12.245.205.1: bytes=32 time=728ms TTL=255 Reply from 12.245.205.1: bytes=32 time=758ms TTL=255 Reply from 12.245.205.1: bytes=32 time=706ms TTL=255 Reply from 12.245.205.1: bytes=32 time=11ms TTL=255
Ping statistics for 12.245.205.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 758ms, Average = 550ms
The current time is: 10 52 53.93 |
|
  SlyBry Slyest Of All The Brys Premium join:2002-08-26 Manchester, NH
| reply to ChuC I guess I still can't complain...
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=2ms TTL=255 Reply from 24.147.72.1: bytes=32 time=2ms TTL=255 Reply from 24.147.72.1: bytes=32 time=2ms TTL=255 Reply from 24.147.72.1: bytes=32 time=5ms TTL=255 Reply from 24.147.72.1: bytes=32 time=2ms 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
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 = 5ms, Average = 2ms |
|
  lordie My new year resolution is 1080P
join:2001-11-13 Sunnyvale, CA
·Comcast
·Skype
| reply to ChuC Sunnyvale Ca (Bay Area)
C:\>ping 12.234.160.1 -t
Pinging 12.234.160.1 with 32 bytes of data:
Reply from 12.234.160.1: bytes=32 time=62ms TTL=254 Reply from 12.234.160.1: bytes=32 time=47ms TTL=254 Reply from 12.234.160.1: bytes=32 time=15ms TTL=254 Reply from 12.234.160.1: bytes=32 time10ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=47ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=63ms TTL=254 Reply from 12.234.160.1: bytes=32 time=47ms TTL=254 Reply from 12.234.160.1: bytes=32 time=32ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=32ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=63ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=47ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time10ms TTL=254 Reply from 12.234.160.1: bytes=32 time=47ms TTL=254 Reply from 12.234.160.1: bytes=32 time=16ms TTL=254 Reply from 12.234.160.1: bytes=32 time=32ms TTL=254 Reply from 12.234.160.1: bytes=32 time=32ms TTL=254
Ping statistics for 12.234.160.1: Packets: Sent = 31, Received = 31, Lost = 0 (0% Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 63ms, Average = 26ms |
|
  Illiniwek Go Illini
join:2002-08-19 Draper, UT clubs:
| reply to ChuC Chicago Area...
Reply from 12.251.226.1: bytes=32 time=8ms TTL=255 Reply from 12.251.226.1: bytes=32 time=8ms TTL=255 Reply from 12.251.226.1: bytes=32 time=8ms TTL=255 Reply from 12.251.226.1: bytes=32 time=10ms TTL=255 Reply from 12.251.226.1: bytes=32 time=9ms TTL=255 Reply from 12.251.226.1: bytes=32 time=9ms TTL=255 Reply from 12.251.226.1: bytes=32 time=8ms TTL=255 Reply from 12.251.226.1: bytes=32 time=9ms TTL=255 Reply from 12.251.226.1: bytes=32 time=8ms TTL=255
Ping statistics for 12.251.226.1: Packets: Sent = 9, Received = 9, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 10ms, Average = 8ms |
|
  Chip Premium join:2001-12-23 Connecticut
| reply to ChuC C:\>ping 12.243.108.129
Pinging 12.243.108.129 with 32 bytes of data:
Reply from 12.243.108.129: bytes=32 time=9ms TTL=255 Reply from 12.243.108.129: bytes=32 time=8ms TTL=255 Reply from 12.243.108.129: bytes=32 time=14ms TTL=255 Reply from 12.243.108.129: bytes=32 time=8ms TTL=255
Ping statistics for 12.243.108.129: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 14ms, Average = 9ms -- Elevators smell different to midgets. |
|
 moofather
join:2000-10-05 Mechanicsville, VA
| reply to ChuC I have the greatest cable ever. I'm on a counter-strike team that placed 13-16th at the last CPL. I will be fully prepared this winter at the next event. Thanks ATTBI.
1 66 ms 111 ms 141 ms 10.226.136.1
1 26 ms 36 ms 451 ms 10.226.136.1
3 283 ms 36 ms 403 ms 10.226.136.1 |
|
  gpurv
join:2000-10-16 Garland, TX clubs:
| reply to ChuC C:\>ping -n 10 12.237.194.1
Pinging 12.237.194.1 with 32 bytes of data:
Reply from 12.237.194.1: bytes=32 time=14ms TTL=255 Reply from 12.237.194.1: bytes=32 time=15ms TTL=255 Reply from 12.237.194.1: bytes=32 time=42ms TTL=255 Reply from 12.237.194.1: bytes=32 time=35ms TTL=255 Reply from 12.237.194.1: bytes=32 time=65ms TTL=255 Reply from 12.237.194.1: bytes=32 time=42ms TTL=255 Reply from 12.237.194.1: bytes=32 time=22ms TTL=255 Reply from 12.237.194.1: bytes=32 time=42ms TTL=255 Reply from 12.237.194.1: bytes=32 time=45ms TTL=255 Reply from 12.237.194.1: bytes=32 time=30ms TTL=255
Ping statistics for 12.237.194.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 65ms, Average = 35ms [text was edited by author 2002-09-28 15:06:58] |
|
 pheebau
join:2001-12-12 El Cerrito, CA
| reply to ChuC Saturday 9/28/2002 at 11:30am - EL CERRITO, CA
Pinging 12.233.156.1 with 32 bytes of data:
Reply from 12.233.156.1: bytes=32 time=44ms TTL=255 Reply from 12.233.156.1: bytes=32 time=105ms TTL=255 Reply from 12.233.156.1: bytes=32 time=87ms TTL=255 Reply from 12.233.156.1: bytes=32 time=10ms TTL=255 Reply from 12.233.156.1: bytes=32 time=73ms TTL=255 Reply from 12.233.156.1: bytes=32 time=84ms TTL=255 Reply from 12.233.156.1: bytes=32 time=105ms TTL=255 Reply from 12.233.156.1: bytes=32 time=11ms TTL=255 Reply from 12.233.156.1: bytes=32 time=80ms TTL=255 Reply from 12.233.156.1: bytes=32 time=46ms TTL=255 Reply from 12.233.156.1: bytes=32 time=100ms TTL=255 Reply from 12.233.156.1: bytes=32 time=41ms TTL=255 Reply from 12.233.156.1: bytes=32 time=98ms TTL=255 Reply from 12.233.156.1: bytes=32 time=35ms TTL=255 Reply from 12.233.156.1: bytes=32 time=242ms TTL=255 Reply from 12.233.156.1: bytes=32 time=89ms TTL=255 Reply from 12.233.156.1: bytes=32 time=45ms TTL=255 Reply from 12.233.156.1: bytes=32 time=18ms TTL=255 Reply from 12.233.156.1: bytes=32 time=103ms TTL=255 Reply from 12.233.156.1: bytes=32 time=33ms TTL=255 Reply from 12.233.156.1: bytes=32 time=14ms TTL=255 Reply from 12.233.156.1: bytes=32 time=32ms TTL=255 Reply from 12.233.156.1: bytes=32 time=100ms TTL=255 Reply from 12.233.156.1: bytes=32 time=16ms TTL=255 Reply from 12.233.156.1: bytes=32 time=25ms TTL=255 Reply from 12.233.156.1: bytes=32 time=15ms TTL=255 Reply from 12.233.156.1: bytes=32 time=23ms TTL=255 Reply from 12.233.156.1: bytes=32 time=17ms TTL=255 Reply from 12.233.156.1: bytes=32 time=217ms TTL=255 Reply from 12.233.156.1: bytes=32 time=35ms TTL=255 Reply from 12.233.156.1: bytes=32 time=72ms TTL=255
Ping statistics for 12.233.156.1: Packets: Sent = 31, Received = 31, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 242ms, Average = 65ms
Always those spikes - why going from 10ms to 242ms - what's the reason? upstreams? it is better from what I've been seeing in the last 4 weeks but still those pings can go high during the week-end and guess what *not* during the week... |
|
  CherryIcee Winter
join:2001-10-25 Bellevue, WA
| reply to ChuC Here's mine. [text was edited by author 2002-09-27 16:01:42] |
|
  Al Kolka Premium join:2002-08-30 Livermore, CA
| reply to ChuC Pinging 10.145.32.1 with 32 bytes of data: Ping statistics for 10.145.32.1: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 10ms, Average = 7ms
For about 10 days this has been my experience: decent ping times except for the lost packets. |
|
  pplchamp1 Great One Premium join:2002-01-25 East Hartford, CT
| reply to ChuC Pinging 12.243.105.1 with 32 bytes of data:
Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=15ms TTL=255 Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=12ms TTL=255 Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=11ms TTL=255 Reply from 12.243.105.1: bytes=32 time=10ms TTL=255 Reply from 12.243.105.1: bytes=32 time=20ms TTL=255
Ping statistics for 12.243.105.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 20ms, Average = 12ms -- I ain't got time to bleed! |
|
  americanada VIP join:2001-12-19 Covina, CA
| reply to ChuC Covina, CA...Rockin' right along as usual 
C:\Documents and Settings>ping 24.130.xxx.1
Pinging 24.130.162.1 with 32 bytes of data:
Reply from 24.130.xxx.1: bytes=32 time=7ms TTL=255 Reply from 24.130.xxx.1: bytes=32 time=7ms TTL=255 Reply from 24.130.xxx.1: bytes=32 time=8ms TTL=255 Reply from 24.130.xxx.1: bytes=32 time=6ms TTL=255
Ping statistics for 24.130.xxx.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 8ms, Average = 7ms -- Anything I say not directly related to a customer's Pipeline service in CA/NV is strictly my own opinion, and not that of my employer, Charter Communications. |
|
  Revcb Orbis non sufficit Premium,Mod join:2001-07-05 Springport, MI
Host: AT&T Broadband Michigan VOIP Tech Chat
| reply to ChuC Pinging 12.***.***.1 with 32 bytes of data:
Reply from 12.***.***.1: bytes=32 time=9ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=9ms TTL=255 Reply from 12.***.***.1: bytes=32 time=7ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=8ms TTL=255 Reply from 12.***.***.1: bytes=32 time=9ms TTL=255
Ping statistics for 12.***.***.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 8ms -- I do whatever the little voices in my head tell me to do. [text was edited by author 2002-09-27 03:41:01] |
|
  The_Tinkerer$ Cast From The Darkness
join:2001-12-31 Denver, CO
| reply to Nohope I've seen snails move faster.....
said by Nohope :
Pinging 12.231.18.1 with 32 bytes of data:
Reply from 12.231.18.1: bytes=32 time=3378ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3236ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3295ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3172ms TTL=254
Ping statistics for 12.231.18.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3172ms, Maximum = 3378ms, Average = 3270ms
Gahhh...I don't know about any saturation, but those are HORRIBLE! I wonder what it looks like from the other end going down TO the modem. If it shows slowdown at what appears to be the modem, then I'd be for scheduling a service call for sure, so that way they can FIX it. -- Yes, I am at the mothership of AT&T, but am merely a mortal, not a magician. Anything I say is not to be construed as an "official" company standpoint. |
|
 Nohope
join:2001-12-01 Seattle, WA
| reply to ChuC Re: Post here the ping times to your gateway
Have to love ATT......They are saturating the router in my area. All pings to anywhere are horrible. Even first hop.....*sigh*
Pinging 12.231.18.1 with 32 bytes of data:
Reply from 12.231.18.1: bytes=32 time=3378ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3236ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3295ms TTL=254 Reply from 12.231.18.1: bytes=32 time=3172ms TTL=254
Ping statistics for 12.231.18.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3172ms, Maximum = 3378ms, Average = 3270ms |
|
 bluebottle$ Premium join:2002-09-04 Richmond, CA
| reply to ChuC Ping statistics for 12.232.176.1: Packets: Sent = 44, Received = 44, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 32ms, Maximum = 396ms, Average = 142ms
11:05 PM Thursday, 9/26 > San Francisco/Bay Area
My usual pings--it's always like this!! -- "That's some catch, that Catch-22," Yossarian observed. "It's the best there is," Doc Daneeka agreed. |
|