1-28-2014 - AT&T outage in Maryland area

We've got a managed MPLS site down in MD, I've been given the following update from AT&T: 01/28/2014,11:41:26:[AT&T ] Activity Type Code Desc: GENERAL COMMENTS Activity Type Code: GEN THE FOLLOWING STATUS INFORMATION ON YOUR TROUBLE HAS BEEN SENT FROM AT&T NETWORK OPERATIONS. Currently 22 T3's still down, no further restoration ability, at least 1hr eta f or tech troubleshooting. My guess is either a fiber fault somewhere or significant equipment failure. - Matt

Our AT&T service delivery manager just updated the list for us: * 7 OC192s * 7 OC48 * 22 Core T3/DS3s * 8 additional T3/DS3s Ouch. - Matt From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Bertram, Matthew Sent: Tuesday, January 28, 2014 12:52 PM To: OUTAGES Mailing List Subject: [outages] 1-28-2014 - AT&T outage in Maryland area We've got a managed MPLS site down in MD, I've been given the following update from AT&T: 01/28/2014,11:41:26:[AT&T ] Activity Type Code Desc: GENERAL COMMENTS Activity Type Code: GEN THE FOLLOWING STATUS INFORMATION ON YOUR TROUBLE HAS BEEN SENT FROM AT&T NETWORK OPERATIONS. Currently 22 T3's still down, no further restoration ability, at least 1hr eta f or tech troubleshooting. My guess is either a fiber fault somewhere or significant equipment failure. - Matt

WOW! 7 OC192's down! On Tue, Jan 28, 2014 at 10:03 AM, Bertram, Matthew <mbertram@acuative.com>wrote:
Our AT&T service delivery manager just updated the list for us:
· 7 OC192s
· 7 OC48
· 22 Core T3/DS3s
· 8 additional T3/DS3s
Ouch.
- Matt
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Bertram, Matthew *Sent:* Tuesday, January 28, 2014 12:52 PM *To:* OUTAGES Mailing List *Subject:* [outages] 1-28-2014 - AT&T outage in Maryland area
We've got a managed MPLS site down in MD, I've been given the following update from AT&T:
*01/28/2014,11:41:26:[AT&T ] * Activity Type Code Desc: GENERAL COMMENTS Activity Type Code: GEN THE FOLLOWING STATUS INFORMATION ON YOUR TROUBLE HAS BEEN SENT FROM AT&T NETWORK OPERATIONS. Currently 22 T3's still down, no further restoration ability, at least 1hr eta f or tech troubleshooting.
My guess is either a fiber fault somewhere or significant equipment failure.
- Matt
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

It is (as you know) abnormally cold here in Maryland, and that means that lots of aging infrastructure under Baltimore and DC is prone to failure. When "aging infrastructure" == "big water main" and blinky things are downstream, problems ensue. Don't know if that was the case here, but I doubt the backhoes were out. Anyway, is there any update on the status of this? Thanks, Rich

Sorry, meant to update this morning, but I've been fighting with an independent telco out in Texas all day. We were told that a "cable repair" team had been deployed to resolve this outage. We saw our circuit come up around 12:00 AM ET. At the time AT&T stated they were still actively working the trouble. The last update on our ticket states (timestamp is CST by the way): 01/29/2014,01:21:07:[AT&T ] Activity Type Code Desc: GENERAL COMMENTS Activity Type Code: GEN THE FOLLOWING STATUS INFORMATION ON YOUR TROUBLE HAS BEEN SENT FROM AT&T NETWORK OPERATIONS. ...per GNOC, TCB has been closed...check ed muliple T3's and see them up as of 23 :00 on 1/28...closing tickets... I chatted in with AT&T and they state the RFO was simply "repaired fiber cut." Wish I could get a little more detail on the event, but that's probably going to be it. I'll try to bug our service manager for any additional info, but I'm not sure if he'll be able to. - Matt -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Rich Kulawiec Sent: Wednesday, January 29, 2014 11:26 AM To: outages@outages.org Subject: Re: [outages] 1-28-2014 - AT&T outage in Maryland area It is (as you know) abnormally cold here in Maryland, and that means that lots of aging infrastructure under Baltimore and DC is prone to failure. When "aging infrastructure" == "big water main" and blinky things are downstream, problems ensue. Don't know if that was the case here, but I doubt the backhoes were out. Anyway, is there any update on the status of this? Thanks, Rich _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Bertram, Matthew
-
Luke Rockwell
-
Rich Kulawiec