This has been happening intermittantly for 6 months or so. Click a link and sometimes it just dies. Click it again and it maybe works. Here is a trace route after a timeout. Any get more out of it than I do? Thanks.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\>tracert www.post-gazette.com
Tracing route to www.post-gazette.com [208.22.33.46]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 4 ms L100.PITBPA-VFTTP-34.verizon-gni.net [173.75.30.1]
3 5 ms 5 ms 4 ms 1-0-7-334.PITBPA-LCR-03.verizon-gni.net [130.81.140.106]
4 12 ms 12 ms 19 ms so-15-3-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.28.204]
5 13 ms 12 ms 12 ms 0.so-4-1-0.XL3.IAD8.ALTER.NET [152.63.30.2]
6 10 ms 12 ms 12 ms 0.xe-11-0-0.BR1.IAD8.ALTER.NET [152.63.41.153]
7 14 ms 14 ms 14 ms 204.255.168.30
8 36 ms 34 ms 34 ms cr1.wswdc.ip.att.net [12.122.135.18]
9 35 ms 34 ms 37 ms cr2.phlpa.ip.att.net [12.122.4.53]
10 36 ms 39 ms 37 ms cr2.cl2oh.ip.att.net [12.122.2.209]
11 35 ms 41 ms 35 ms cr84.cl2oh.ip.att.net [12.123.151.133]
12 35 ms 34 ms 34 ms gar6.cl2oh.ip.att.net [12.123.150.73]
13 12.89.98.130 reports: Destination net unreachable.
Trace complete.
H:\Documents and Settings\>
pablo59,
Regarding this particular TRACERT, it would appear that you're making it out of the Verizon backbone with no problems and you're only running into an issue somewhere in the AT&T backbone (hop 13). I ran a TRACERT here as well and got an almost identical result (packets lost at hop 14, but at the same IP 12.123.150.73). It looks like that AT&T router is taking a bad route at that point. As for why this has been going on for 6 months, I honestly don't know why that is. It's possible that there is an issue with that gateway router. I can't imagine that a major gateway router would have issues for that long and go unaddressed, but you never know. Bottom line- issue is either with the AT&T router at hop 12 sending or the would-be router at hop 13 receiving.
Regards,
Chris
Any way to open a ticket with ATT on this? I imagine the reason it has been going on for so long is that everybody has been shrugging it off.
Does Verizon have any control over the route chosen? Would it be possible to Verizon to choose other routes when presented with a node having a history of timeouts? Isn't "the net" supposed to be smart like that?
Alternatively, after a recent outage at my CO, the problem was gone ... for a while. Any chance that understanding more about the equipment replaced/repaired over the course of that outage would shed some light on the issue? Also note that it is not always an ATT node that appears to be the offender. I have seen alter.net in there as well as others.
My CO is McMurray, PA.
pablo59,
Unfortunately, since this is an isolated incident, it would be virtually impossible to get this escalated on our end, especially since the issue is not occurring in the Verizon backbone. Typically these bad routes work themselves out over time. Six months does seem like a long time, however. Truth be told, the best course of action at this point in time would be for you to contact either AT&T or AlterNet and alert them of the timeouts.
Regards,
Chris
Wouldn't some piece of Verizon network equipment generate a log of timed out requests? Wouldn't a bit of analysis of that log not only confirm or bust the ATT-node-broken theory, but if confirmed provide all sorts a good data that would be far more likely to generate an actual solution from ATT than would a mere customer of another ISP reporting something so easily dismissed as an "isolated incident"?
Still happening...
@pablo59 wrote:This has been happening intermittantly for 6 months or so. Click a link and sometimes it just dies. Click it again and it maybe works. Here is a trace route after a timeout. Any get more out of it than I do? Thanks.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\>tracert www.post-gazette.com
Tracing route to www.post-gazette.com [208.22.33.46]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 4 ms L100.PITBPA-VFTTP-34.verizon-gni.net [173.75.30.1]
3 5 ms 5 ms 4 ms 1-0-7-334.PITBPA-LCR-03.verizon-gni.net [130.81.140.106]
4 12 ms 12 ms 19 ms so-15-3-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.28.204]
5 13 ms 12 ms 12 ms 0.so-4-1-0.XL3.IAD8.ALTER.NET [152.63.30.2]
6 10 ms 12 ms 12 ms 0.xe-11-0-0.BR1.IAD8.ALTER.NET [152.63.41.153]
7 14 ms 14 ms 14 ms 204.255.168.30
8 36 ms 34 ms 34 ms cr1.wswdc.ip.att.net [12.122.135.18]
9 35 ms 34 ms 37 ms cr2.phlpa.ip.att.net [12.122.4.53]
10 36 ms 39 ms 37 ms cr2.cl2oh.ip.att.net [12.122.2.209]
11 35 ms 41 ms 35 ms cr84.cl2oh.ip.att.net [12.123.151.133]
12 35 ms 34 ms 34 ms gar6.cl2oh.ip.att.net [12.123.150.73]
13 12.89.98.130 reports: Destination net unreachable.
Trace complete.
H:\Documents and Settings\>
I did a whois on the last hop IP there 12.89.98.130. This IP belongs to ATT worldnet. Hops are controled by the previous hop. So for example. hop 9 has no idea what hop 11 will be. It only knows hop 10. So in this case, Hop 13 is bad and hop 12 keeps routing the info to it. Hop 12 needs correction. Therefore ATT needs to be contacted and they have to address their routing table at hop 12. They need to log into that router and have it re-route to bypass 12.89.98.130. unfortunatly, you will need to contact ATT regading this and hope they will actually listen. I've been having a similar issue with Sprintlink and been fighting them for years on it now and still no resolution.
Start a new topic or ask questions in the open forum.
