Charter Spectrum → Re: Ping times in Janesville area

Here is my Tracert:Tracing route to www.yahoo.akadns.net [64.58.76.229]

over a maximum of 30 hops:

1 107 ms 10 ms 61 ms 10.40.0.1
2 70 ms 24 ms 54 ms 172.18.98.66
3 68 ms 99 ms 151 ms 172.18.97.42
4 266 ms 65 ms 101 ms 12.125.143.113
5 41 ms 193 ms 38 ms gbr2-p100.cgcil.ip.att.net [12.123.5.78]
6 93 ms 59 ms 86 ms gr2-p3100.cgcil.ip.att.net [12.123.5.138]
7 49 ms 44 ms 33 ms ibr02-p0-0.okbr01.exodus.net [209.1.169.173]
8 154 ms 87 ms 30 ms bbr01-g4-0.okbr01.exodus.net [216.34.183.97]
9 304 ms 102 ms 58 ms bbr01-p2-0.whkn01.exodus.net [206.79.9.134]
10 188 ms 115 ms 69 ms bbr02-p1-0.nycm01.exodus.net [206.79.9.165]
11 54 ms 108 ms 260 ms 64.15.224.17
12 98 ms 59 ms 128 ms bbr01-p0-0.stng01.exodus.net [206.79.9.102]
13 123 ms 111 ms 59 ms dcr03-g9-0.stng01.exodus.net [216.33.96.145]
14 255 ms 152 ms 301 ms csr22-ve241.stng01.exodus.net [216.33.98.19]
15 109 ms 108 ms 272 ms 216.35.210.126
16 722 ms 178 ms 373 ms w8.dcx.yahoo.com [64.58.76.229]

Trace complete.

And here is my ping to 10.40.0.1:

Reply from 10.40.0.1: bytes=32 time=86ms TTL=255
Reply from 10.40.0.1: bytes=32 time=92ms TTL=255
Reply from 10.40.0.1: bytes=32 time=38ms TTL=255
Reply from 10.40.0.1: bytes=32 time=61ms TTL=255
Reply from 10.40.0.1: bytes=32 time=107ms TTL=255
Reply from 10.40.0.1: bytes=32 time=111ms TTL=255
Reply from 10.40.0.1: bytes=32 time=93ms TTL=255
Reply from 10.40.0.1: bytes=32 time=18ms TTL=255
Reply from 10.40.0.1: bytes=32 time=35ms TTL=255
Reply from 10.40.0.1: bytes=32 time=71ms TTL=255
Reply from 10.40.0.1: bytes=32 time=33ms TTL=255
Reply from 10.40.0.1: bytes=32 time=156ms TTL=255
Reply from 10.40.0.1: bytes=32 time=27ms TTL=255
Reply from 10.40.0.1: bytes=32 time=419ms TTL=255
Reply from 10.40.0.1: bytes=32 time=129ms TTL=255
Reply from 10.40.0.1: bytes=32 time=130ms TTL=255
Reply from 10.40.0.1: bytes=32 time=52ms TTL=255
Reply from 10.40.0.1: bytes=32 time=34ms TTL=255
Reply from 10.40.0.1: bytes=32 time=333ms TTL=255
Reply from 10.40.0.1: bytes=32 time=459ms TTL=255
Reply from 10.40.0.1: bytes=32 time=85ms TTL=255
Reply from 10.40.0.1: bytes=32 time=314ms TTL=255
Reply from 10.40.0.1: bytes=32 time=77ms TTL=255
Reply from 10.40.0.1: bytes=32 time=119ms TTL=255
Reply from 10.40.0.1: bytes=32 time=81ms TTL=255
Reply from 10.40.0.1: bytes=32 time=374ms TTL=255
Reply from 10.40.0.1: bytes=32 time=40ms TTL=255
Reply from 10.40.0.1: bytes=32 time=61ms TTL=255

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

as you can see my pings are all over the place.

said by Jayzin:

---

here is my ping to 10.40.0.1:
Ping statistics for 10.40.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 741ms, Average = 119ms
as you can see my pings are all over the place.

---

Well, the pings to your first hop are very high.
(Maximum = 741ms, Average = 119ms)

This would cause any other tracerts to look bad.

Just to rule out your end and if you are running Win9x/ME
hold down Ctrl/Alt/Del and "End Task" on all programs except for Explorer and Systray and try the first hop ping test again. If they are still high then it looks like a problem with your first hop.

The great techs in your area and posting here can help with that problem.

We are on it. Keep an eye on your IM here. JVLTech will get you an update.