Office of Information Technology

Show Activity

Activity ID: 3082

Activity type

ACTIVITY/OUTAGE: UPDATED: 

Subject


AT&T Emergency Network Outage
 
  

Short description

Internet and WAN traffic for Barrow, most UAF, and both UAS remote campus sites. 

Scope

21:35 Update: called AT&T NOC in Anchorage  Frank said AT&T configured a replacementM10 router and swapped out the bad router.  They are in the process of getting all of their routing tables updated.  This failure dropped an OC-12
circuit.
Still no firm recovery time specified.  They hope to have everything back on
line by early morning.
---
21:30 Update: AT&T has found the root cause of the issue being a failed router, and they are currently working on the issue.
---
There is no ETA for recovery from AT&T technicians, however, they believe that they have found the root cause of the issue and are working on correcting the network routing issues.
Internet and WAN traffic for Barrow, most UAF, and both UAS remote campus
sites.
UAS Sitka
UAS Ketchikan
UAF Matsu
UAF Dillingham
UAF Bethel
UAF Nome
UAF Kotzebue
UAF Kodiak FITC
Barrow

Status 1

Emergency Repair 

Start day

Tuesday, 4-16-2013 Time: 03:30 pm 

Recovery day

Wednesday, 4-17-2013 Time: 12:30 am 

Duration

There is no ETA for recovery from AT&T technicians, however, they believe that they have found the root cause of the issue and are working on correcting the network routing issues.
Unknown

Description

AT&T has routing failure in their core network.
At this time AT&T Engineers believe this is a hardware related failure.
Estimated repair/recovery time is unknown.

Circuits

UAS Sitka
UAS Ketchikan
UAF Matsu
UAF Dillingham
UAF Bethel
UAF Nome
UAF Kotzebue
UAF Kodiak FITC
Barrow

Comments

There is no ETA for recovery from AT&T technicians, however, they believe that they have found the root cause of the issue and are working on correcting the network routing issues.
Circuits have been toggling on and off line for the last hour.

Affected customers

Listed sites

Authorized by

Earl Voorhis OIT Network Operations 

Back to Top