[General] Some Sites Unreachable on AT&T DSL Network!
Ever since Friday morning, one site I access is getting timeouts. Still. There's nothing wrong with the site and others on Comcast or Uverse or whatever are able to access the site. Traceroute shows a problem. I called support and managed to get someone real to talk to. They too were unable to access the site on their PC but they could on their phone! But so far nothing has changed.
Here's the traceroute to the site otherminds.org in San Francisco. (I'm in Oakland on legacy AT&T DSL):
traceroute to otherminds.org (220.127.116.11), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.608 ms 0.489 ms 0.450 ms
2 adsl-70-137-159-254.dsl.snfc21.sbcglobal.net (18.104.22.168) 42.264 ms 42.918 ms 4 1.724 ms
3 dist2-vlan62.snfcca.sbcglobal.net (22.214.171.124) 42.553 ms 41.485 ms 42.356 ms
4 bb2-10g2-0.snfcca.sbcglobal.net (126.96.36.199) 41.261 ms 41.837 ms 41.988 ms
5 * * *
6 * * *
Ironically, the same problem occurs when trying to access repair.att.com:
traceroute to repair.att.com (188.8.131.52), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.588 ms 0.365 ms 0.414 ms
2 adsl-70-137-159-254.dsl.snfc21.sbcglobal.net (184.108.40.206) 42.232 ms 42.515 ms 4 1.559 ms
3 dist1-vlan52.snfcca.sbcglobal.net (220.127.116.11) 41.841 ms 41.945 ms 41.936 ms
4 18.104.22.168 (22.214.171.124) 41.622 ms 50.910 ms 41.624 ms
5 cgcil401me3.ip.att.net (126.96.36.199) 91.868 ms 92.431 ms 91.837 ms
6 188.8.131.52 (184.108.40.206) 99.452 ms 99.005 ms 99.802 ms
7 * * *
Anyone have any hints as to what's going on and how to get them to recognize there's a problem and even fix it?
I should add that all other sites I visit so far do not seem to have this problem, altho sometimes a google search will hang and I'll have to try bing.com instead!
actions · 2012-Sep-29 5:35 pm · (locked)
Just to add, I am unable to access the site via At&t Uverse and from my colocation provider in NYC. Seems like this might be a bigger problem than just At&t (legacy) DSL:
From Uverse in Sunnyvale, CA:
Tracing route to otherminds.org [220.127.116.11]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms gw-condo.domain.home.bivek.net[192.168.1.1]
2 * * * Request timed out.
3 24 ms 21 ms 22 ms 99-104-124-2.lightspeed.sntcca.sbcglobal.net [18.104.22.168]
4 * * * Request timed out.
5 32 ms 22 ms 22 ms 22.214.171.124
6 * * * Request timed out.
7 22 ms 21 ms 21 ms 126.96.36.199
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
From colo provider in NYC:
traceroute to otherminds.org (188.8.131.52), 30 hops max, 40 byte packets
1 ip131.67-202-103.static.steadfastdns.net (184.108.40.206) 2.399 ms 2.592 ms 2.807 ms
2 ip61.67-202-117.static.steadfastdns.net (220.127.116.11) 2.040 ms 2.218 ms 2.447 ms
3 ip25.67-202-117.static.steadfastdns.net (18.104.22.168) 0.350 ms 0.406 ms 0.490 ms
4 xe-10-0-1-142.cr1.nyc3.us.nlayer.net (22.214.171.124) 0.228 ms 0.200 ms 0.214 ms
5 ae1-50g.ar1.nyc3.us.nlayer.net (126.96.36.199) 1.790 ms 1.711 ms 3.358 ms
6 telx.10ge.nyc.bboi.net (188.8.131.52) 0.503 ms 0.426 ms 0.478 ms
7 nj-ten2-1-ny60-ten1-4.bboi.net (184.108.40.206) 1.607 ms 1.705 ms 1.688 ms
8 ash-ten1-5-nj-ten2-2.bboi.net (220.127.116.11) 14.578 ms 14.514 ms 14.645 ms
9 pit-ten2-1-ash-ten7-2.bboi.net (18.104.22.168) 13.656 ms 13.008 ms 12.947 ms
10 22.214.171.124 (126.96.36.199) 17.643 ms 17.864 ms 17.825 ms
11 myhostcenter-gw-primary.cust.e-xpedient.com (188.8.131.52) 18.597 ms 18.733 ms 18.216 ms
12 * * *
13 * * *
14 * * *
15 * * *
actions · 2012-Sep-30 2:15 am · (locked)
So when stuff like this happens, what are you supposed to do? The website hosting service says everything seems to be working at their end. AT&T says "Hmmmm."
What I don't understand is shouldn't the request be routed around servers that aren't responding?
Who do you call?
actions · 2012-Sep-30 2:26 am · (locked)
I tried again to get AT&T to understand and recognize that there is a problem here. I called the DSL Internet support line. The person at the other end struggled to understand why just rebooting my modem was not going to solve the problem. When I asked if there was a networking expert I could call, they sent me to their web hosting support. That person was sympathetic and tried to find someone to call, but only came back with the same DSL Support line I started with (877-722-3755).
As a result, I'm extremely frustrated. I spent over an hour on the phone with AT&T this afternoon, and got nowhere.
Personally, I am moving my DSL off AT&T and over to Sonic.net, a local SF Bay Area supplier. And unless I can do better tomorrow with making another foray into the AT&T support circus, I'm going to recommend that our organization, OtherMinds.org, do the same and move their office DSL over to Sonic.net.
But does anyone out there have a secret number I can use to try to get somewhere deeper into the AT&T network support? Or at least try to find someone more understanding and willing to investigate the problem? This is crazy!
actions · 2012-Oct-2 6:44 am · (locked)
|reply to rchrd |
Sometimes the problem is the opposite of what you might think.
It might not be a problem with your packets reaching the destination. It might be a problem with packets from the destination reaching you.
AT&T Uverse; Zyxel NBG334W router (behind the 2wire gateway); openSuSE 12.2; firefox 15.0.1
actions · 2012-Oct-2 9:33 am · (locked)
Anybody resolve? Starting getting the same issue (in SC) - unable to reach bellsouth.net from AT*T uVerse network.
actions · 2012-Oct-13 7:35 pm · (locked)
jmorlanHmm... That's funny.Premium,MVM
|reply to rchrd |
I have the same issue. I cannot reach either of the sites you list. In addition I cannot reach kcsoftwares.com although the site is reachable via Sonic.net fusion.
Is this something for ATT direct?
Issue seems to be resolved as of now. I can surf to all three sites.
"It turns out we're very good at not seeing things" - Jack Hitt
actions · 2012-Oct-18 5:26 pm · (locked)