figmund
join:2000-11-01
Sammamish, WA | reply to NoOneButMe
Re: Washington State Speed problems Just for the record, I'm in Sammamish and my speeds have been this way for a week now:
Your download speed : 3358446 bps, or 3279 kbps.
A 409.9 KB/sec transfer rate.
Your upload speed : 750469 bps, or 732 kbps.
Upload speed - cool beans... download speed? Not even close to the "standard" tier. But how can you get customer service to do anything about it? They just say the network is "normal". |
|
1 edit | right now thay wont becuse not enuf people have sead its broken i get less then 400k down here  so your kinda lucky i get less then a meg to the east of Wa so its something that thay know of its just them fixing it |
|
|
|
 W7PSKJust MePremium
join:2000-12-04
Everett, WA
 ·Comcast
| reply to cable prob
In everett here is my test just now
2005-05-31 21:00:58 EST: 3625 / 357
Your download speed : 3712849 bps, or 3625 kbps.
A 453.2 KB/sec transfer rate.
Your upload speed : 366000 bps, or 357 kbps.
--
Rick Scott Everett, WashingtonLiving in the land of NEVER FIOS. |
|
KevTechPremium
join:2002-08-22
Seattle, WA
1 edit | reply to cable prob
YUK
Pinging www.comcast.net [63.240.76.72] with 32 bytes of data:
Reply from 63.240.76.72: bytes=32 time=328ms TTL=50
Reply from 63.240.76.72: bytes=32 time=316ms TTL=50
Reply from 63.240.76.72: bytes=32 time=321ms TTL=50
Reply from 63.240.76.72: bytes=32 time=338ms TTL=50
Ping statistics for 63.240.76.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 316ms, Maximum = 338ms, Average = 325ms
|
|
| reply to W7PSK
i moved here and i cant get full speeds im not to far from the airport but im getting crazy slow speeds |
|
| reply to cable prob
Ok i live in lacey and well my speeds SUCK A FAT ONE. i get at the most 1 to 2 megs on a good day and 300's on my upstream. I cant play battlefield or other online games other than EQ. The latency it WAY TO HIGH. Im really thinking on switching to DSL. Well if anyone has an idea i would love to hear it. |
|
| i play Task Force Dagger and i cant play i get kicked ping times are high it seems to have something to do with goin east i dont know what though i dont think thay where ready for all the bandwith bein used |
|
| reply to cable prob
West olympia here...
:::.. Download Stats ..:::
Connection is:: 1104 Kbps about 1.1 Mbps (tested with 579 kB)
Download Speed is:: 135 kB/s
Tested From:: »testmy.net/ (server1)
Test Time:: Tue May 31 2005 21:49:35 GMT-0700 (Pacific Standard Time)
Bottom Line:: 20X faster than 56K 1MB download in 7.59 sec
Diagnosis: May need help : running at only 30.68 % of your hosts average (comcast.net)
Validation Link:: »testmy.net/stats/id-AVNO90Z1F
not good..... i usually get like 4200 kb/s... but the last 2-3 days have been horrible. Definately a router issue. |
|
 mdmaddoxPremium
join:2002-12-29
Federal Way, WA | reply to cable prob
So much for speed and pings
»/speedtests/10···17601035
Tracing route to www.comcast.net [204.127.205.8]
over a maximum of 30 hops:
1 * * * Request timed out.
2 55 ms 38 ms 11 ms 68.86.98.213
3 11 ms 15 ms 11 ms 68.86.96.33
4 15 ms 11 ms 31 ms 68.86.96.29
5 * 14 ms 13 ms 68.86.96.21
6 11 ms 12 ms 34 ms 68.86.96.26
7 12 ms 44 ms 64 ms 68.86.96.121
8 40 ms 13 ms 12 ms 68.86.96.126
9 160 ms 163 ms 244 ms 68.86.96.242
10 182 ms 190 ms 192 ms 12.118.60.9
11 148 ms 186 ms 144 ms 12.123.44.198
12 234 ms 236 ms 238 ms tbr2-cl1.cgcil.ip.att.net [12.122.10.61]
13 224 ms 219 ms 220 ms tbr1-cl2.cgcil.ip.att.net [12.122.9.133]
14 216 ms 236 ms 214 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
15 212 ms 210 ms 211 ms gbr2-p10.n54ny.ip.att.net [12.122.11.6]
16 234 ms 213 ms 213 ms gar1-p370.n54ny.ip.att.net [12.123.1.133]
17 210 ms 220 ms 211 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255
.162]
18 202 ms 201 ms 193 ms sccsbix12-1-6.attbi.com [63.240.64.50]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 223 ms 221 ms 220 ms www.comcast.net [204.127.205.8] |
|
| reply to missionsix
i been getting less then 1 meg east of washington its hard to game when most of the servers are back east |
|
| yikes!! 2005-06-01 00:55:12 EST: 2450 / 340
Your download speed : 2509201 bps, or 2450 kbps.
A 306.2 KB/sec transfer rate.
Your upload speed : 348373 bps, or 340 kbps.
Yikes!! this is definately not cool. |
|
 shimonmorPremium
join:2000-12-30
Sedro Woolley, WA | reply to cable prob
Re: Washington State Speed problems Anacortes. Been having problems for about 10 days.
I don't even bother calling anymore. Why put myself through the agony? That's how these big companies get away with bad service: beat the customers into submission by making "customer service" a painful experience.
2005-06-01 00:53:50 EST: 719 / 290
Your download speed : 737044 bps, or 719 kbps.
A 89.9 KB/sec transfer rate.
Your upload speed : 297026 bps, or 290 kbps. |
|
| Have also had problems in Seattle for days. Speed tests give around 2500 down. In-game pings are nothing less than 200ms, where they are usually 20ms. |
|
mdmaddoxPremium
join:2002-12-29
Federal Way, WA
1 edit | reply to cable prob
I'm trying something new. I'm starting to e-mail my speed and ping to Comcast from their help page.
»www.comcast.net/help/contact/
Don't do it! |
|
| reply to cable prob
I've had bad pings, slow speeds and packet loss for a month now. My pings flucuate from 150-200ms in most games, my packet loss causes rubberbanding and my speeds are about 1/4 - 1/2 of the advertised 4mb. About a month ago, everything was fine... pings hovered around 20-60ms (depending on EC or WC) and I had no packet loss at all. Calling Comcast yeilds no results, they say everything is fine, but yet I know 5 people in my area (1 living 2 doors down from me) that are having the exact same problem. I'm seriously going to switch back to DSL if things don't clear up. I can get 2.5/3mb(depending on distance) reliable DSL speeds for only $10 more than I'm paying for this.
-Tacoma is getting screwed by it's cable company- |
|
 tshirtPremium,MVM
join:2004-07-11
Snohomish, WA
kudos:3
·Comcast
| reply to cable prob
Seattle area CRAN is FUBAR
speeds below 2 megs and a traceroute shows
68.86.96.253 0% 60 60 192.42 234.53 262.73
68.86.96.65 0% 60 60 190.42 237.38 269.94
68.86.96.70 0% 60 60 192.49 238.24 280.48
68.86.96.74 2% 59 60 194.97 239.52 273.96
these 4 routers were around 20ms for several days now |
|
2 edits | here is a trace route from my place to TX
| Hop | %Loss | IP Address |
| 0 | | 192.168.1.1
| 1 | 100 |
| 2 | 10 | 68.86.98.177
| 3 | 10 | 68.86.96.73
| 4 | 10 | 68.86.96.69
| 5 | 10 | 68.86.96.66
| 6 | 10 | 68.86.96.254
| 7 | 10 | 12.118.60.9
| 8 | 20 | 12.122.80.174
| 9 | 20 | 12.122.12.113
| 10 | 10 | 12.122.10.26
| 11 | 20 | 12.122.10.49
| 12 | 10 | 12.123.196.101
| 13 | 20 | 12.119.136.14
| 14 | | 70.85.127.30
| 15 | | 70.85.127.91
| 16 | 10 | 67.19.255.26
| 17 | | 67.19.126.87 |
|
| reply to cable prob
Slow ping times in Seatac again tonight. Started happening around 22:17
# date
Tue May 31 22:45:47 PDT 2005
# ping google.com -c 10
PING google.com (216.239.39.99): 56 data bytes
64 bytes from 216.239.39.99: icmp_seq=0 ttl=239 time=187.4 ms
64 bytes from 216.239.39.99: icmp_seq=1 ttl=239 time=180.5 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=239 time=186.1 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=239 time=178.4 ms
64 bytes from 216.239.39.99: icmp_seq=4 ttl=239 time=171.3 ms
64 bytes from 216.239.39.99: icmp_seq=5 ttl=239 time=190.9 ms
64 bytes from 216.239.39.99: icmp_seq=6 ttl=239 time=179.2 ms
64 bytes from 216.239.39.99: icmp_seq=7 ttl=239 time=200.7 ms
64 bytes from 216.239.39.99: icmp_seq=8 ttl=239 time=209.2 ms
64 bytes from 216.239.39.99: icmp_seq=9 ttl=239 time=198.5 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 171.3/188.2/209.2 ms
# ping comcast.net -c 10
PING comcast.net (204.127.205.8): 56 data bytes
64 bytes from 204.127.205.8: icmp_seq=0 ttl=52 time=233.8 ms
64 bytes from 204.127.205.8: icmp_seq=1 ttl=52 time=249.4 ms
64 bytes from 204.127.205.8: icmp_seq=2 ttl=52 time=287.4 ms
64 bytes from 204.127.205.8: icmp_seq=3 ttl=52 time=280.4 ms
64 bytes from 204.127.205.8: icmp_seq=4 ttl=52 time=267.1 ms
64 bytes from 204.127.205.8: icmp_seq=5 ttl=52 time=248.6 ms
64 bytes from 204.127.205.8: icmp_seq=6 ttl=52 time=248.5 ms
64 bytes from 204.127.205.8: icmp_seq=7 ttl=52 time=267.5 ms
64 bytes from 204.127.205.8: icmp_seq=8 ttl=52 time=265.5 ms
64 bytes from 204.127.205.8: icmp_seq=9 ttl=52 time=224.4 ms
--- comcast.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 224.4/257.2/287.4 ms
# ping comcast.com -c 10
PING comcast.com (164.109.28.3): 56 data bytes
64 bytes from 164.109.28.3: icmp_seq=0 ttl=108 time=294.5 ms
64 bytes from 164.109.28.3: icmp_seq=1 ttl=108 time=237.9 ms
64 bytes from 164.109.28.3: icmp_seq=2 ttl=108 time=235.3 ms
64 bytes from 164.109.28.3: icmp_seq=3 ttl=108 time=240.8 ms
64 bytes from 164.109.28.3: icmp_seq=4 ttl=108 time=227.7 ms
64 bytes from 164.109.28.3: icmp_seq=5 ttl=108 time=226.4 ms
64 bytes from 164.109.28.3: icmp_seq=6 ttl=108 time=242.0 ms
64 bytes from 164.109.28.3: icmp_seq=7 ttl=108 time=218.0 ms
64 bytes from 164.109.28.3: icmp_seq=8 ttl=108 time=232.5 ms
64 bytes from 164.109.28.3: icmp_seq=9 ttl=108 time=221.3 ms
--- comcast.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 218.0/237.6/294.5 ms # traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 216.239.37.99
traceroute to google.com (216.239.37.99), 30 hops max, 38 byte packets
1 * * *
2 68.86.98.141 (68.86.98.141) 13.733 ms 24.262 ms 8.658 ms
3 68.86.96.121 (68.86.96.121) 20.374 ms 13.553 ms 13.313 ms
4 68.86.96.126 (68.86.96.126) 29.519 ms 28.172 ms 19.896 ms
5 68.86.96.242 (68.86.96.242) 58.941 ms 56.210 ms 54.459 ms
6 12.118.106.5 (12.118.106.5) 166.120 ms 185.439 ms 180.094 ms
7 tbr2-p013802.st6wa.ip.att.net (12.122.5.158) 193.361 ms 195.654 ms 204.672 ms
8 12.123.44.181 (12.123.44.181) 153.121 ms 131.891 ms 129.520 ms
9 so-3-2-0.gar1.Seattle1.Level3.net (4.68.127.109) 236.242 ms 242.618 ms 236.978 ms
10 so-0-0-0.gar2.Seattle1.Level3.net (209.247.8.162) 218.790 ms 179.800 ms 225.596 ms
11 so-7-0-0.mp2.Seattle1.Level3.net (64.159.1.165) 57.948 ms 59.187 ms 62.889 ms
12 4.68.128.201 (4.68.128.201) 320.914 ms 4.68.128.210 (4.68.128.210) 257.559 ms 4.68.1
*28.201 (4.68.128.201) 319.644 ms
13 ge-1-2-52.car1.Washington1.Level3.net (4.68.121.37) 330.735 ms ge-1-2-54.car1.Washing
*ton1.Level3.net (4.68.121.101) 265.828 ms ge-1-1-53.car1.Washington1.Level3.net (4.68.121
*.69) 180.368 ms
14 4.79.228.26 (4.79.228.26) 158.290 ms 157.450 ms 161.849 ms
15 216.239.46.34 (216.239.46.34) 251.402 ms 276.105 ms 277.442 ms
16 64.233.174.130 (64.233.174.130) 277.085 ms 261.021 ms 268.727 ms
17 216.239.48.110 (216.239.48.110) 277.790 ms 268.065 ms 277.262 ms
18 * * *
19 *^C
# traceroute comcast.net
traceroute: Warning: comcast.net has multiple addresses; using 63.240.76.72
traceroute to comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 68.86.98.141 (68.86.98.141) 18.214 ms 8.658 ms 8.673 ms
3 68.86.96.121 (68.86.96.121) 25.465 ms 8.747 ms 12.853 ms
4 68.86.96.126 (68.86.96.126) 30.429 ms 28.276 ms 18.832 ms
5 68.86.96.230 (68.86.96.230) 60.951 ms 48.521 ms 50.916 ms
6 12.118.106.5 (12.118.106.5) 182.718 ms 173.202 ms 141.535 ms
7 12.122.80.50 (12.122.80.50) 128.171 ms 111.091 ms 105.692 ms
8 tbr2-cl1.cgcil.ip.att.net (12.122.10.61) 219.167 ms 213.852 ms 221.612 ms
9 tbr1-cl2.cgcil.ip.att.net (12.122.9.133) 255.159 ms 254.087 ms 256.843 ms
10 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 228.083 ms 208.591 ms 213.573 ms
11 gbr2-p10.n54ny.ip.att.net (12.122.11.6) 131.611 ms 138.523 ms 150.481 ms
12 gar1-p370.n54ny.ip.att.net (12.123.1.133) 207.674 ms 210.948 ms 229.115 ms
13 mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162) 172.741 ms 172.655 ms 170.893
* ms
14 * * *
15 *^C
# traceroute comcast.com
traceroute to comcast.com (164.109.28.3), 30 hops max, 38 byte packets
1 * * *
2 68.86.98.141 (68.86.98.141) 17.539 ms 12.752 ms 10.257 ms
3 68.86.96.121 (68.86.96.121) 19.878 ms 11.405 ms 25.208 ms
4 68.86.96.126 (68.86.96.126) 12.362 ms 20.133 ms 9.873 ms
5 68.86.96.234 (68.86.96.234) 50.524 ms 64.348 ms 109.472 ms
6 12.118.60.5 (12.118.60.5) 112.059 ms 87.225 ms 67.478 ms
7 12.122.80.54 (12.122.80.54) 174.596 ms 170.464 ms 147.501 ms
8 ggr1-p3100.st6wa.ip.att.net (12.123.44.133) 225.626 ms 260.366 ms 313.723 ms
9 POS2-0.BR1.SEA1.ALTER.NET (204.255.174.241) 168.087 ms 153.678 ms 150.061 ms
10 0.so-7-3-0.XL2.SEA1.ALTER.NET (152.63.105.22) 73.931 ms 109.184 ms 102.498 ms
11 0.so-6-0-0.XL2.DCA6.ALTER.NET (152.63.38.74) 232.148 ms 249.449 ms 231.386 ms
12 0.so-7-0-0.GW6.DCA6.ALTER.NET (152.63.41.225) 196.587 ms 204.094 ms 226.690 ms
13 digex-gw.customer.alter.net (157.130.214.102) 257.183 ms 212.876 ms 242.640 ms
14 vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.net (164.109.3.149) 135.090 ms 118.752 ms
* 116.981 ms
15 * * *
16 *^C
(*) WARNING 4 long line(s) split |
|
| im getting 10-20% loss in the comcast network lol its funny and sad at the same time |
|
| reply to cable prob
and for reference, the same pings and traceroutes from a speakeasy DSL line in downtown Seattle...
# date
Tue May 31 22:55:22 PDT 2005
# ping google.com -c 10
PING google.com (216.239.39.99): 56 data bytes
64 bytes from 216.239.39.99: icmp_seq=0 ttl=248 time=88.9 ms
64 bytes from 216.239.39.99: icmp_seq=1 ttl=248 time=87.9 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=248 time=88.1 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=248 time=87.0 ms
64 bytes from 216.239.39.99: icmp_seq=4 ttl=248 time=87.5 ms
64 bytes from 216.239.39.99: icmp_seq=5 ttl=248 time=87.9 ms
64 bytes from 216.239.39.99: icmp_seq=6 ttl=248 time=87.7 ms
64 bytes from 216.239.39.99: icmp_seq=7 ttl=248 time=87.6 ms
64 bytes from 216.239.39.99: icmp_seq=8 ttl=248 time=88.4 ms
64 bytes from 216.239.39.99: icmp_seq=9 ttl=248 time=87.8 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 87.0/87.8/88.9 ms
# ping comcast.net -c 10
PING comcast.net (204.127.205.8): 56 data bytes
64 bytes from 204.127.205.8: icmp_seq=0 ttl=53 time=79.7 ms
64 bytes from 204.127.205.8: icmp_seq=1 ttl=53 time=80.0 ms
64 bytes from 204.127.205.8: icmp_seq=2 ttl=53 time=78.4 ms
64 bytes from 204.127.205.8: icmp_seq=3 ttl=53 time=78.3 ms
64 bytes from 204.127.205.8: icmp_seq=4 ttl=53 time=78.9 ms
64 bytes from 204.127.205.8: icmp_seq=5 ttl=53 time=78.2 ms
64 bytes from 204.127.205.8: icmp_seq=6 ttl=53 time=78.9 ms
64 bytes from 204.127.205.8: icmp_seq=7 ttl=53 time=78.2 ms
64 bytes from 204.127.205.8: icmp_seq=8 ttl=53 time=78.2 ms
64 bytes from 204.127.205.8: icmp_seq=9 ttl=53 time=79.4 ms
--- comcast.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 78.2/78.8/80.0 ms
# ping comcast.com -c 10
PING comcast.com (164.109.28.3): 56 data bytes
64 bytes from 164.109.28.3: icmp_seq=0 ttl=115 time=82.3 ms
64 bytes from 164.109.28.3: icmp_seq=1 ttl=115 time=80.4 ms
64 bytes from 164.109.28.3: icmp_seq=2 ttl=115 time=81.1 ms
64 bytes from 164.109.28.3: icmp_seq=3 ttl=115 time=79.5 ms
64 bytes from 164.109.28.3: icmp_seq=4 ttl=115 time=79.4 ms
64 bytes from 164.109.28.3: icmp_seq=5 ttl=115 time=81.2 ms
64 bytes from 164.109.28.3: icmp_seq=6 ttl=115 time=79.5 ms
64 bytes from 164.109.28.3: icmp_seq=7 ttl=115 time=80.1 ms
64 bytes from 164.109.28.3: icmp_seq=8 ttl=115 time=80.0 ms
64 bytes from 164.109.28.3: icmp_seq=9 ttl=115 time=80.6 ms
--- comcast.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 79.4/80.4/82.3 ms
# traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 216.239.39.99
traceroute to google.com (216.239.39.99), 30 hops max, 38 byte packets
1 er1.sea1.speakeasy.net (216.231.44.1) 9.350 ms 9.225 ms 9.480 ms
2 220.ge-0-1-0.cr2.sea1.speakeasy.net (69.17.83.233) 8.526 ms 7.724 ms 7.736 ms
3 fe-0-3-0.cr2.sfo1.speakeasy.net (69.17.83.150) 25.385 ms 25.321 ms 25.670 ms
4 core2-1-1-0.pao.net.google.com (198.32.176.31) 25.433 ms 24.882 ms 28.165 ms
5 66.249.95.66 (66.249.95.66) 27.107 ms 66.249.94.19 (66.249.94.19) 27.205 ms 30.273
*ms
6 66.249.94.162 (66.249.94.162) 27.375 ms 76.506 ms 67.243 ms
7 216.239.49.251 (216.239.49.251) 34.288 ms 33.685 ms 35.219 ms
8 216.239.47.130 (216.239.47.130) 94.922 ms 132.972 ms 87.540 ms
9 216.239.46.45 (216.239.46.45) 86.695 ms 86.342 ms 86.005 ms
10 216.239.46.54 (216.239.46.54) 85.815 ms 87.037 ms 64.233.174.126 (64.233.174.126) 8
*7.176 ms
11 216.239.48.90 (216.239.48.90) 86.545 ms 87.344 ms 87.216 ms
12 216.239.47.46 (216.239.47.46) 88.285 ms 88.979 ms 88.266 ms
13 * * *
14 *
# traceroute comcast.net
traceroute: Warning: comcast.net has multiple addresses; using 204.127.205.8
traceroute to comcast.net (204.127.205.8), 30 hops max, 38 byte packets
1 er1.sea1.speakeasy.net (216.231.44.1) 8.821 ms 10.458 ms 9.678 ms
2 120.ge-0-0-0.cr2.sea1.speakeasy.net (69.17.83.241) 8.143 ms 7.586 ms 7.770 ms
3 ge-5-1-440.hsa2.Seattle1.Level3.net (209.247.91.169) 7.861 ms 7.053 ms 8.739 ms
4 ge-6-1-1.mp1.Seattle1.Level3.net (209.247.9.53) 14.552 ms 8.356 ms 8.479 ms
5 so-7-0-0.gar1.Seattle1.Level3.net (64.159.1.82) 9.181 ms 8.431 ms 21.484 ms
6 att-level3-oc48.Seattle1.Level3.net (4.68.127.110) 8.604 ms 8.597 ms 9.189 ms
7 12.123.44.182 (12.123.44.182) 9.665 ms 9.177 ms 8.710 ms
8 tbr2-cl1.cgcil.ip.att.net (12.122.10.61) 56.522 ms 55.723 ms 55.725 ms
9 tbr1-cl2.cgcil.ip.att.net (12.122.9.133) 54.786 ms 55.319 ms 55.190 ms
10 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 78.176 ms 77.689 ms 78.356 ms
11 gbr1-p10.n54ny.ip.att.net (12.122.11.2) 77.171 ms 76.178 ms 76.360 ms
12 gar1-p360.n54ny.ip.att.net (12.123.1.129) 77.450 ms 76.409 ms 77.161 ms
13 mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162) 77.489 ms 76.842 ms 77.632 ms
14 * *
# traceroute comcast.com
traceroute to comcast.com (164.109.28.3), 30 hops max, 38 byte packets
1 er1.sea1.speakeasy.net (216.231.44.1) 10.719 ms 11.426 ms 9.916 ms
2 210.ge-0-1-0.cr1.sea1.speakeasy.net (69.17.83.237) 8.261 ms 8.509 ms 7.783 ms
3 444.g8-0.mpr1.sea4.us.above.net (209.249.11.186) 7.646 ms 7.818 ms 7.765 ms
4 POS2-2.BR1.SEA1.ALTER.net (64.125.12.14) 8.566 ms 7.380 ms 7.975 ms
5 0.so-7-3-0.XL2.SEA1.ALTER.NET (152.63.105.22) 7.206 ms 10.851 ms 7.692 ms
6 0.so-6-0-0.XL2.DCA6.ALTER.NET (152.63.38.74) 76.901 ms 76.799 ms 76.931 ms
7 0.so-7-0-0.GW6.DCA6.ALTER.NET (152.63.41.225) 77.416 ms 77.881 ms 76.365 ms
8 digex-gw.customer.alter.net (157.130.214.102) 79.144 ms 78.554 ms 78.134 ms
9 vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.net (164.109.3.149) 79.144 ms 81.686 ms 7
*8.225 ms
10 * *
(*) WARNING 3 long line(s) split |
|
