It Was AT&T, With An Outage, For A Week

AT&T, Your World, Destroyed
The picture above just about sums up the past week from last Thursday until today.

What happened?

My aircard stopped working. My Apple iPhone stopped working. I was traveling from San Francisco to New York for my conference session at Interop/Mobile Business Expo as well as a few meetings and no email, no blog access. WTF?!?!?! But why was I able to access other email and websites such as Google, Yahoo, Facebook and LinkedIn? I think AT&T has it out for me. Though I’ve been a pretty loyal customer for quite some time (if you include me as a Cingular subscriber), for some reason they chose to block access from the AT&T network to mobileslate.com.

So last Thursday after noticing that it wasn’t just my iPhone and that my aircard was not able to access it either, I first called up my webhost and asked if there was a problem. The response: No, everything is functioning normally. So from my hotel in near Central Park and Columbus Circle in New York City, I walk down to the closest Starbucks and plug into the T-Mobile Hotspot access. No problems. Works great. I can get to my email and my blog’s admin page to post and respond to comments. I head over to Javitz Convention Center using the free Interop WiFi access and no issues. But as in New York, when you are a bit more mobile, you tend to be more dependent on mobile technology. But where ever I went, AT&T would not let me access my email or website. Safari didn’t allow me. Last Friday, after my speaking session, I went to visit a friend at his office, asked to plug into their network to do some work and everything worked great.

Meanwhile on the AT&T network, no dice. I finally call Technical Support and explain my situation to them. They bounced me around several times from iPhone support to Laptop Connect support, and finally I had enough and just told a Tech to file to support issue.

Back Home

I enjoyed the rest of the weekend and Sunday when I got back home, I plugged into my DSL connection at home and was able to access everything related to my domain. Perhaps there was some issue in New York and being in San Francisco, it might be an isolated regional issue. So I tried to connect using my iPhone and my Laptop Connect card, but still no luck. Ummm, am I that popular that AT&T has decided to block me? Is my content offensive to AT&T? So I call again to file another complaint. This time, I try and perform a few more tests from my laptop. Traceroute fails. It doesn’t even see past the first router that I connect to. Ping fails. But all other websites and email accounts — no issues. Hmmm, they’re out to get me.

Problem Resolution ASAP

Wednesday with still no access from my iPhone or Laptop Connect card, I call again. This time I am on the phone with the Tech rep for over 2 hours trying to convince him that I have tried everything to isolate the problem. He doesn’t believe me. He tells me to reboot my laptop with all drivers off. He tells me to contact my webhost (I web chat with my webhost — no issues). I run traceroute (it fails) to prove to him there is an issue. I then tell him to try and connect. He cannot either. We go round and round. He keeps telling me, it’s your fault. Or your web host. They are block us (AT&T network) from access your site. I ask for a Supervisor or Manager. He tells me that it won’t help. I ask him if it’s possible that there is something wrong with the router/firewall that is blocking my site. He says *NO*. Obviously this guys is just reading the script. I ask again for a Manager. Finally, after 90 minutes with this guy, he transfers me. 15 minutes more of being on hold and I speak to a Supervisor. I explain the issue again and she tells me, “yup, it’s an issue on our side. I will contact the network group and see what’s up.”

Automagicaly Resolved

Today around 13:00, my iPhone starts beeping and I see that mobileslate email is working. I try my Laptop Connect card. It’s working.

So after a week of service outage for just my website and email server, looks like things are back to normal. I never did get a call back or email as to an explanation. But now that the problem *is* resolved, I believe it to be an AT&T router issue that blocked access to this site.

Related Posts:
  1. EVENT: MetaPlaces – How To Monetize Location Data & Services...

  2. Eluma, Flip And A Party in NYC...

  3. Mobile Business Expo Presentation...

  4. Mobileslate Outage – Web Traffic Exceeded...

  5. Mobileslate Service Outage...

  6. Filed under: AT&T, Cingular, Interop, Mobile, T-Mobile, WiFi, aircard, conference, data services, email, event, handsets, iPhone, mobileslate, wordpress
blog comments powered by Disqus

Powered in part by Linkshare Merchandiser WP Plugin google.load("language", "1"); var curstate = 0; var hasloaded = 0; function bnc_show_translated() { if (hasloaded == 0) { bnc_lang_callback(); hasloaded = 1; } for (i = 0; i < 0; i++) { var elem = $("bnc_original_" + i); if (elem) { if (curstate) { elem.show(); } else { elem.hide(); } } } for (i = 0; i < 0; i++) { var elem = $("bnc_trans_" + i); if (elem) { if (curstate) { elem.hide(); } else { elem.show(); } } } if (curstate) { $("bnc_trans_state1").show(); $("bnc_trans_state2").hide(); curstate = 0; } else { $("bnc_trans_state1").hide(); $("bnc_trans_state2").show(); curstate = 1; } } function bnc_detect_div(div_id) { var text = document.getElementById(div_id); if (text) { text = text.innerHTML; if (text.length > 0) { google.language.detect(text, function(result) { if (!result.error) { if (result.language != "en") { if (result.confidence > 0.25) { $("bnc_translating").show(); bnc_xlate_div(result.language, div_id, "en"); } } } } ); } } } function bnc_xlate_div(src_lang,div_id,o_lang) { var text = document.getElementById(div_id); if (text) { text = text.innerHTML; google.language.translate(text, src_lang, o_lang, function(result) { var translated = document.getElementById(div_id); if (result.translation) { translated.innerHTML = result.translation; } }); } } function bnc_lang_callback() { } function bnc_startup() { bnc_xlate_div("en", "bnc_translate_info", "en"); bnc_xlate_div("en", "bnc_translate_info2", "en"); } google.setOnLoadCallback(bnc_startup);