wesg9
join:2001-05-21
Weirton, WV
| W.V. speeds went in the tubes last night
This seems to be the best test i have gotten in the last 12 hours. normally pretty good here. what went wrong ?
»/speedtests/40···45826374
packet loss is also from 25% - 100%
Pinging portal.comcast.net [24.153.64.7] with 32 bytes of data:
Reply from 24.153.64.7: bytes=32 time=1721ms TTL=241
Reply from 24.153.64.7: bytes=32 time=103ms TTL=241
Reply from 24.153.64.7: bytes=32 time=2145ms TTL=241
Reply from 24.153.64.7: bytes=32 time=39ms TTL=241
Reply from 24.153.64.7: bytes=32 time=54ms TTL=241
Reply from 24.153.64.7: bytes=32 time=28ms TTL=241
Reply from 24.153.64.7: bytes=32 time=1946ms TTL=241
Reply from 24.153.64.7: bytes=32 time=22ms TTL=241
Reply from 24.153.64.7: bytes=32 time=1439ms TTL=241
Reply from 24.153.64.7: bytes=32 time=21ms TTL=241
Reply from 24.153.64.7: bytes=32 time=23ms TTL=241
Reply from 24.153.64.7: bytes=32 time=1768ms TTL=241
Reply from 24.153.64.7: bytes=32 time=23ms TTL=241
Reply from 24.153.64.7: bytes=32 time=58ms TTL=241
Reply from 24.153.64.7: bytes=32 time=26ms TTL=241
Reply from 24.153.64.7: bytes=32 time=25ms TTL=241
Request timed out.
Request timed out.
Reply from 24.153.64.7: bytes=32 time=2209ms TTL=241
Request timed out.
Reply from 24.153.64.7: bytes=32 time=22ms TTL=241
Request timed out.
Reply from 24.153.64.7: bytes=32 time=24ms TTL=241
Reply from 24.153.64.7: bytes=32 time=26ms TTL=241
Reply from 24.153.64.7: bytes=32 time=22ms TTL=241
Ping statistics for 24.153.64.7:
Packets: Sent = 25, Received = 21, Lost = 4 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 2209ms, Average = 559ms
Pinging www.attbi.com [216.148.227.69] with 32 bytes of data:
Request timed out.
Reply from 216.148.227.69: bytes=32 time=1022ms TTL=50
Reply from 216.148.227.69: bytes=32 time=115ms TTL=50
Reply from 216.148.227.69: bytes=32 time=84ms TTL=50
Reply from 216.148.227.69: bytes=32 time=104ms TTL=50
Reply from 216.148.227.69: bytes=32 time=86ms TTL=50
Request timed out.
Reply from 216.148.227.69: bytes=32 time=81ms TTL=50
Reply from 216.148.227.69: bytes=32 time=1173ms TTL=50
Reply from 216.148.227.69: bytes=32 time=83ms TTL=50
Reply from 216.148.227.69: bytes=32 time=80ms TTL=50
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Request timed out.
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Reply from 216.148.227.69: bytes=32 time=89ms TTL=50
Reply from 216.148.227.69: bytes=32 time=83ms TTL=50
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Reply from 216.148.227.69: bytes=32 time=100ms TTL=50
Reply from 216.148.227.69: bytes=32 time=89ms TTL=50
Reply from 216.148.227.69: bytes=32 time=110ms TTL=50
Reply from 216.148.227.69: bytes=32 time=82ms TTL=50
Ping statistics for 216.148.227.69:
Packets: Sent = 23, Received = 20, Lost = 3 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 1173ms, Average = 189ms
Tracing route to www.attbi.com [216.148.227.69]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 13 ms 11 ms 14 ms 12.244.65.18
5 * 18 ms 18 ms 12.244.72.70
6 18 ms 24 ms 19 ms tbr1-p012401.phlpa.ip.att.net [12.123.137.45]
7 23 ms 20 ms 23 ms tbr2-p012301.n54ny.ip.att.net [12.122.10.97]
8 20 ms 62 ms 21 ms tbr1-p012501.n54ny.ip.att.net [12.122.9.129]
9 2528 ms * 151 ms tbr1-p013801.cgcil.ip.att.net [12.122.10.50]
10 1508 ms * * tbr1-cl1.sffca.ip.att.net [12.122.10.6]
11 * 172 ms 80 ms gar4-p300.sffca.ip.att.net [12.123.13.174]
12 216 ms 82 ms 85 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
13 * 81 ms 87 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
14 82 ms * 124 ms www.attbi.com [216.148.227.69]
Trace complete.
[text was edited by author 2003-02-21 06:42:31] |
