Reviews:
 ·Cox HSI
| reply to odog
Re: [ALL] Blizzard traceroutes to Chicago I see. glad that you made a right adjustments to turn the cox customers away from the hosed of AT&T network to other place that i have tested this 208.18.148.176 and it goes away from the AT&T network hosed. good work.
Tracing route to 208.18.148.176 over a maximum of 30 hops
1 6 ms 17 ms 8 ms 10.32.32.1
2 7 ms 11 ms 6 ms 70.183.70.181
3 15 ms 13 ms 13 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
4 16 ms 17 ms 19 ms 70.183.71.62
5 15 ms 13 ms 14 ms 70.183.71.109
6 * * * Request timed out.
7 30 ms 52 ms 27 ms ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.19
4.173]
8 25 ms 54 ms 51 ms ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.2
33]
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C |
|
| Just noticed the ip address to trace was incorrect.
Cogent is still on the path from Cox in Scottsdale AZ. Can't even trace past their network!
Tracing route to 208.18.148.176 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 8 ms 10 ms 10.85.0.1
3 9 ms 9 ms 8 ms 172.21.1.116
4 27 ms 15 ms 18 ms 70.169.75.116
5 10 ms 12 ms 11 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 75 ms 26 ms 23 ms 68.1.5.139
7 24 ms 25 ms 23 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out. |
|
