University of Alaska incident

UA Network Disruption

Major Resolved View vendor source →

University of Alaska experienced a major incident on October 2, 2025 affecting UAF Campus Connectivity and Statewide Network Connectivity and 1 more component, lasting 20h 58m. The incident has been resolved; the full update timeline is below.

Started
Oct 02, 2025, 07:42 PM UTC
Resolved
Oct 03, 2025, 04:41 PM UTC
Duration
20h 58m
Detected by Pingoru
Oct 02, 2025, 07:42 PM UTC

Affected components

UAF Campus ConnectivityStatewide Network ConnectivityUAF/SW VPNUAF Wireless

Update timeline

  1. investigating Oct 02, 2025, 07:42 PM UTC

    We are currently investigating reports of major disruptions with the UA network. Thank you for your patience as our networking technicians troubleshoot. Our next scheduled update will be at 12:10PM.

  2. monitoring Oct 02, 2025, 08:12 PM UTC

    Our networking technicians have implemented a workaround to restore internet access to UA. We'll continuing monitoring the situation and report here when the outage is fully resolved. Thank you for your patience.

  3. monitoring Oct 03, 2025, 06:24 AM UTC

    ACS has resolved the circuit issue and the OIT Data and Communications team have reverted the workaround. We'll continue monitoring network service overnight for stability. Have a good night!

  4. monitoring Oct 03, 2025, 04:25 PM UTC

    The UA Network has remained stable following OIT Networking's reversion of their workaround; they will be continuing to monitor the stability through the morning and encourage reporting any network issues as you normally would. Thanks so much for your time!

  5. resolved Oct 03, 2025, 04:41 PM UTC

    OIT Networking is content with the current status of the UA Network and we are happy to report that the outage is now considered closed. Please report any issues with campus internet or the UA VPN to your campus's IT helpdesk, and thank you again for your time and patience during the resolution of this issue!

  6. postmortem Oct 08, 2025, 06:33 PM UTC

    This disruption was the result of an outage with our vendor, ACS.