said by plummber2461 :5 83 ms 83 ms 83 ms cdm-66-76-168-13.bssr.cox-internet.com [66.76.168.13]
Isn't that router evil? I haven't seen it resolve in less than 50ms since a few weeks after the ip changes. It used to be less than 30ms. Either way, it's not helping their level3 problem.
- local-routing - [8ms] bssr.cox-internet.com - [Lose 1 Turn] level3 addressing block - [Go Back 3 Spaces] destination address - [Not enough packets. Do not pass go. Do not collect $200]
Your second hop is a private network between the modem and the CMTS. It works, it's just not responding to ICMP. 192.168.1.1 is your router (hop 1).
My second hop has strange results... Two weeks ago, it was responding "Request Timed Out" One week ago, it was responding 10.x.x.x (like it should) This week it responds as my router. Go figure.
-edit- Well, that's what I get for tabbed browsing. I'm an idiot. I'll just shut up now...
Tracing route to google.com [64.233.187.99] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1] 2 18 ms 23 ms 27 ms 10.95.0.1 3 11 ms 11 ms 22 ms 24.197.3.42 4 53 ms 47 ms 61 ms 12.126.167.129 5 95 ms 72 ms 69 ms gbr2-p70.wswdc.ip.att.net [12.123.9.46] 6 64 ms 56 ms 61 ms tbr2-p013701.wswdc.ip.att.net [12.122.11.189] 7 67 ms 101 ms 122 ms 12.122.84.201 8 250 ms 242 ms 197 ms 192.205.34.42 9 189 ms 203 ms 204 ms ix-12-2.core3.AEQ-Ashburn.teleglobe.net [63.243. 149.102] 10 141 ms 148 ms 157 ms 209.85.130.16 11 87 ms 96 ms 87 ms 72.14.238.136 12 84 ms 156 ms 119 ms 72.14.236.15 13 109 ms 91 ms 67 ms 216.239.49.222 14 191 ms 173 ms 142 ms jc-in-f99.google.com [64.233.187.99]
