Trouble reaching my site from Comcast, but not other networks.

Portal Home > Knowledgebase > Articles Database > Trouble reaching my site from Comcast, but not other networks.

Posted by Philbot, 05-12-2010, 05:14 PM
>>>> LOCAL TRACERT from my PC Tracing route to mr-phil.com [161.58.232.253] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms mr-phil.com [161.58.232.253] 2 * * * Request timed out. 3 9 ms 7 ms 10 ms 68.85.72.65 4 10 ms 9 ms 14 ms te-9-1-ur02.morgantown.wv.pitt.comcast.net [68.86.146.113] 5 11 ms 9 ms 12 ms te-9-1-ur01.morgantown.wv.pitt.comcast.net [68.86.146.13] 6 13 ms 13 ms 11 ms te-3-3-ar01.pittsburgh.pa.pitt.comcast.net [68.86.146.18] 7 13 ms 11 ms 11 ms 68.85.75.169 8 28 ms 27 ms 25 ms te-2-0-0-0-cr01.chicago.il.ibone.comcast.net [68.86.91.85] 9 26 ms 37 ms 26 ms pos-0-2-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.78] 10 26 ms 32 ms 35 ms as6453-pe01.350ecermak.il.ibone.comcast.net [75.149.228.250] 11 26 ms 25 ms 30 ms if-2-0-0-18.core1.CT8-Chicago.as6453.net [66.110.14.33] 12 26 ms 26 ms 25 ms ix-6-1-0.core1.CT8-Chicago.as6453.net [66.110.14.26] 13 64 ms 65 ms 61 ms as-1.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.17] 14 87 ms 100 ms 95 ms p64-0-0-0.r20.atlnga04.us.bb.gin.ntt.net [129.250.5.27] 15 59 ms 59 ms 85 ms p64-4-2-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.3.18] 16 65 ms 64 ms 60 ms xe-1-1.r01.stngva01.us.bb.gin.ntt.net [129.250.2.85] 17 * * * Request timed out. 18 67 ms * 61 ms ge-25.a0807.stngva01.us.wh.verio.net [204.2.123.34] 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. >>>> REMOTE TRACERT from Network-Tools.com TraceRoute to 161.58.232.253 [mr-phil.com] Hop (ms) (ms) (ms) IP Address Host name 1 14 13 8 72.249.128.105 - 2 11 19 6 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net 3 21 25 33 4.69.145.12 ae-1-60.edge2.dallas3.level3.net 4 105 51 67 129.250.3.43 as-1.r20.asbnva02.us.bb.gin.ntt.net 5 45 14 49 129.250.2.128 ae-3.r21.asbnva01.us.bb.gin.ntt.net 6 47 53 60 129.250.2.85 xe-1-1.r01.stngva01.us.bb.gin.ntt.net 7 46 53 52 129.250.27.187 ge-0-0-0.r00.stngva01.us.wh.verio.net 8 44 48 43 204.2.123.34 ge-25.a0807.stngva01.us.wh.verio.net 9 53 46 48 129.250.27.187 ge-0-0-0.r00.stngva01.us.wh.verio.net 10 64 47 53 204.2.123.34 ge-25.a0807.stngva01.us.wh.verio.net 11 50 46 51 161.58.232.253 mr-phil.com Trace complete * Local TRACERT from my PC. Tracing route to google.com [72.14.204.99] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms iad04s01-in-f99.1e100.net [72.14.204.99] 2 * * * Request timed out. 3 8 ms 7 ms 10 ms 68.85.72.65 4 9 ms 9 ms 9 ms te-9-1-ur01.grantsville.md.pitt.comcast.net [68.86.146.118] 5 10 ms 11 ms 21 ms 68.87.173.122 6 14 ms 17 ms 13 ms 68.87.173.126 7 18 ms 13 ms 13 ms 68.85.75.193 8 20 ms 19 ms 24 ms te-0-4-0-5-cr01.mclean.va.ibone.comcast.net [68.86.91.129] 9 21 ms 23 ms 20 ms pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.70] 10 47 ms 49 ms 48 ms 75.149.231.62 11 26 ms 25 ms 25 ms 209.85.240.136 12 42 ms 33 ms 35 ms 66.249.94.54 13 27 ms 26 ms 27 ms iad04s01-in-f99.1e100.net [72.14.204.99] Trace complete.
Posted by Andrew Moore, 05-12-2010, 09:38 PM
There has been some posts in the premium members thread about comcast.
Posted by Tyl3r, 05-13-2010, 12:48 PM
Why don't you contact your provider?
Posted by ai-danno, 06-17-2010, 02:17 PM
That's just a nice traceroute- that indicates nothing wrong at all. The missed hop response is non-cumulative, and the latency remains low throughout the trace. And the trace completes. If you think you have a problem, you should run a winMTR, which will show packet loss and latency trending issues over time. tracert is like pathping- it sucks. EDIT- I'm not speaking about the first trace... just all the others... hadn't seen that trace lol.
Posted by woods01, 06-18-2010, 07:02 PM
In regards to the original first traceroute theres nothing about comcast in that traceroute that's an issue. Your issue (if any) is that your site is hosted @ ntt. Comcast doesn't appear to have peeing with or for some reason your route didn't go from comcast to ntt since they are also a backbone. In any event, doesn't appear to be a comcast issue to me unless your server or verio has you on some kind of block list.
Posted by Sekweta, 06-18-2010, 10:14 PM
What does the reverse path look like when you run a traceroute from your web server back to your Comcast connection?