ChuC
join:2001-12-18
|  Post here the ping times to your gateway
Let us post here our ping times to the gateway so that ATT can do something positive about it. They need data. I will start with mine. Include timestamp and your area.
>ping -n 10 12.234.176.1
Pinging 12.234.176.1 with 32 bytes of data:
Ping statistics for 12.234.176.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 251ms, Average = 133ms
>time
The current time is: 15:24:55.85 PDT (San Francisco Bay Area) |
|
Mark IV
Premium
join:2002-09-22
Montreal, QC | Ping statistics for 12.233.44.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 40ms, Average = 15ms
in the bay area too (berkeley) |
|
prwood
Premium
join:2001-09-04
Danvers, MA
| reply to ChuC
>ping -n 10 66.31.24.1
Pinging 66.31.24.1 with 32 bytes of data:
Ping statistics for 66.31.24.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 78ms, Average = 26ms
---
This is the Boston, Mass area around 6:30 pm EDT.
--
[ boston ] [ my site ] [ photos ] |
|
jeremy27
join:2001-11-29
Grand Rapids, MI | reply to ChuC
Ping statistics for 12.245.88.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 94ms, Average = 14ms |
|
KeNsHiN x
join:2001-10-19
Elk Grove, CA
| reply to ChuC
Ping statistics for 12.246.188.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 17ms, Average = 11ms
This is in the Sacramento Area (95624) at 5:56 PM. |
|
urd
join:2001-07-26
Oakland, CA
| reply to ChuC
Pinging 12.233.50.1 with 32 bytes of data:
Reply from 12.233.50.1: bytes=32 time=8ms TTL=255
Reply from 12.233.50.1: bytes=32 time=7ms TTL=255
Reply from 12.233.50.1: bytes=32 time=8ms TTL=255
Reply from 12.233.50.1: bytes=32 time=9ms TTL=255
Ping statistics for 12.233.50.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 8ms
Bay Area |
|
EastLansing
@attbi.com
| reply to ChuC
>ping -n 10 10.186.160.1
Ping statistics for 10.186.160.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 463ms, Average = 277ms
East Lansing, Michigan...I'm tired of these ping times =/ |
|
LarryE
join:2000-07-29
Chicago, IL
| reply to ChuC
What's the gateway and how do I find out what mine is?
el gringo
[text was edited by author 2002-09-24 21:40:01] |
|
titanium
Titanium
join:2000-05-25
West Richland, WA
 ·Verizon Online DSL
| reply to ChuC
C:\>ping 24.98.2.1
Pinging 24.98.2.1 with 32 bytes of data:
Reply from 24.98.2.1: bytes=32 time=271ms TTL=255
Reply from 24.98.2.1: bytes=32 time=390ms TTL=255
Reply from 24.98.2.1: bytes=32 time=431ms TTL=255
Reply from 24.98.2.1: bytes=32 time=500ms TTL=255
Ping statistics for 24.98.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 271ms, Maximum = 500ms, Average = 398ms
C:\>
not normally this bad... but has been over 100ms for me on average lately.. tonight just completely blows though.. the one night i really need to use my internet in a while and its crawling slow enough it might as well be completely down.
[text was edited by author 2002-09-24 21:59:55] |
|
titanium
Titanium
join:2000-05-25
West Richland, WA
·Verizon Online DSL
| C:\>ping 24.98.2.1
Pinging 24.98.2.1 with 32 bytes of data:
Reply from 24.98.2.1: bytes=32 time=411ms TTL=255
Reply from 24.98.2.1: bytes=32 time=350ms TTL=255
Reply from 24.98.2.1: bytes=32 time=321ms TTL=255
Reply from 24.98.2.1: bytes=32 time=761ms TTL=255
Ping statistics for 24.98.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 321ms, Maximum = 761ms, Average = 460ms
C:\>
one run right after posting... hey, atleast i have 0% loss... yippie (pfft)
[text was edited by author 2002-09-24 22:00:25] |
|
ihaddsl
join:2001-12-05
/dev/hda0
 ·Comcast
| reply to ChuC
Pinging 12.248.0.1 with 32 bytes of data:
Reply from 12.248.0.1: bytes=32 time=20ms TTL=254
Reply from 12.248.0.1: bytes=32 time10ms TTL=254
Reply from 12.248.0.1: bytes=32 time=10ms TTL=254
Reply from 12.248.0.1: bytes=32 time=10ms TTL=254
Ping statistics for 12.248.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 20ms, Average = 10ms |
|
KeNsHiN x
join:2001-10-19
Elk Grove, CA
| reply to LarryE
said by LarryE  :
What's the gateway and how do I find out what mine is?
Find out your IP by going to »www.ipchicken.com (or some other IP place).
Your gateway is whatever your ping is but last set of numbers is a 1. (For example, IP 123.123.123.123 has a gateway of 123.123.123.1 - so *.*.*.1 is the gateway.
I hope this helps ya... |
|
migxxv
join:2002-04-30
Citrus Heights, CA | reply to ChuC
Not always Kenshin, sometimes if you have a 123.123.123.123 address than your gateway can have a different second to last number (123.123.122.1; 123.123.121.1; etc...) |
|
Mordy
Comfortably Numb
Premium,MVM,ExMod 2004-07
join:2001-12-02
Denver, CO
·Comcast Formerly ..
| reply to ChuC
Pinging 12.253.30.1 with 32 bytes of data:
Reply from 12.253.30.1: bytes=32 time=11ms TTL=255
Reply from 12.253.30.1: bytes=32 time=15ms TTL=255
Reply from 12.253.30.1: bytes=32 time=62ms TTL=255
Reply from 12.253.30.1: bytes=32 time=13ms TTL=255
Ping statistics for 12.253.30.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 62ms, Average = 25ms
Denver CO (80234) 8:30 pm MDT
--
The Hokey Pokey - What if that's what it's all about? |
|
wheelzoff
join:2001-02-14
Irving, TX
clubs:
| reply to migxxv
True, my ip is 12.239.241.247 and my gateway is 12.239.240.1, so that isn't always the case. Too find your gateway open a command prompt and type "ipconfig" or "ipconfig/all"
Ping statistics for 12.239.240.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 37ms, Average = 13ms
Pretty damn good numbers for 9pm.
--
"The Stars win the Stanley Cup, The Stars win the Stanley Cup" Ralph Strangis!! |
|
biff420
Premium
join:2002-01-26
Richmond, CA
·AT&T Yahoo
| reply to ChuC
Gateway pings in Berkeley
C:\Documents and Settings\biff>ping 12.233.44.1
Pinging 12.233.44.1 with 32 bytes of data:
Reply from 12.233.44.1: bytes=32 time=35ms TTL=255
Reply from 12.233.44.1: bytes=32 time=34ms TTL=255
Reply from 12.233.44.1: bytes=32 time=10ms TTL=255
Reply from 12.233.44.1: bytes=32 time=13ms TTL=255
Ping statistics for 12.233.44.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 35ms, Average = 23ms |
|
moshua
join:2001-03-13
Stow, MA
| reply to ChuC
>ping 24.91.216.1
Pinging 24.91.216.1 with 32 bytes of data:
Reply from 24.91.216.1: bytes=32 time=91ms TTL=254
Reply from 24.91.216.1: bytes=32 time=148ms TTL=254
Reply from 24.91.216.1: bytes=32 time=57ms TTL=254
Reply from 24.91.216.1: bytes=32 time=97ms TTL=254
Ping statistics for 24.91.216.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 148ms, Average = 98ms
Boston, MA area @ 10:45 EDT |
|
laprjns
Premium
join:2002-03-11
Ellington, CT
·AT&T Yahoo
·Comcast Formerly ..
| reply to ChuC
sorry about the graphics, don't know how to copy from a dos window.
ping'ed around 10:40pm. ellington ct.
[text was edited by author 2002-09-24 22:53:33] |
|
jdir
join:2001-05-04
Santa Clara, CA | reply to ChuC
Geez, wouldnt it make more sense to ping some known host - ie Yahoo.com rather than your gateway? |
|
ChuC
join:2001-12-18
| jdir, in a reasonable system, the ping time to one's own gateway will be very low, say below 30 ms or so. Everything has to go thru one's gateway, before getting to anywhere. The ping time being so bad at some places shows a fundamental problem. BTW, associated with this high ping time here, is a very slow net experience in general. This started about two weeks ago.
Tonight the ping time has improved a bit for me (compared to the last few evenings), and the net appears a bit better. |
|
