NTS and OIT System Status Page

Oct 2, 2026 · resolved Oct 5

The IAM team has resolved the issue with the UAOnline service, and confirmed the fix to be stable. The certificate update that caused the issue was reverted. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!

Sep 22, 2026 · resolved Sep 22

The services reported as affected have remained stable since the AWS fix yesterday evening, and we are considering this incident to be resolved. Please report any continued issues with UA sites and services to your campus's IT helpdesk, and thank you again for your patience during the resolution of this issue!

Sep 21, 2026 · resolved Sep 21

University Website and VPN External Accessibility Problem Impact Analysis Event Occurrence: 20260921 # Background University of Alaska provides Virtual Private Network \(VPN\) connectivity for university affiliated users located remotely and needing access to university network resources.  Additionally the university hosts public facing websites intended to be accessed globaly.  These services, as well as others, are dependent upon connectivity between the university network and the wider internet, provided by our commodity internet service provider, Alaska Communications Systems \(ACS\). # Break Down of the Problem On 09/21/2026 at approximately 3:30pm, remote users outside of the university network reported issues loading university websites, and additionally reported interruption in connectivity to the university VPN.  Technicians onsite reported that both VPN and web resources were accessible from within the university network.  The OIT Telecommunications Services investigated and found that websites and VPN connectivity were working from within the university network, and that our network peering with ACS appeared to be up and recieving/advertising routes normally.  An OIT technician from another workgroup on remote work and experiencing the connectivity issue reported that a traceroute from their home location to multiple university resources failed within the university's commodity internet service provider, Alaska Communications Systems \(ACS\) network prior to reaching the university network.  OIT Telecommunications services at approximately 4:30pm received email communication from ACS confirming a network event within their network, followed by a subsequent email just prior to 5:30pm that the network event was resolved and services were stabilized. # Target State / Goal  University of Alaska network connectivity to the internet at large should remain online at all times, providing remote access to UA network resources such as websites and VPN connectivity. # Root Cause Analysis  This was determined to be caused by an event outside of the university network, within the commodity internet service provider \(ACS\) network, with ACS reporting upon resolution "_The network event impacting services has stabilized, and service restoration is complete._"  While no point-to-point WAN circuits or commodity internet peerings were _directly_ affected, some network traffic transiting the ACS network via those commodity internet peerings was impacted during the provider event.   # Develop Countermeasures  Commodity internet service provider \(ACS\) resolved internal network event. # Implementation of Countermeasures OIT Telecommunications Services will reach out to service providers in the future as we become aware of potential issues impacting commodity internet connectivity. # Follow Up / Review ACS Provided email confirmation of internal network event resolution.

Aug 28, 2026 · resolved Aug 28

This disruption was caused by a vendor outage and not related to University operations.

Aug 25, 2026 · resolved Aug 28

Canvas LMS Degradation of Service Problem Impact Analysis Event Occurrence: 8/25/26 # Background The Canvas LMS platform provides web based digital classroom features to instructors and students. Courses, terms, and enrollments on the platform are managed through a direct connection to UAF’s SIS platform and Registrar processes. For most online courses and some in person courses, the associated Canvas course shell is the centralized location for all coursework, references, and grades. # Break Down of the Problem On 8/21/26 we received canvas support tickets from less than 5 users reporting that their course rosters were missing students or an instructor. Upon investigation, we found the configuration of the Canvas LMS to Banner SIS integration to have a timing issue. The integration, called ILP, does realtime updates of course enrollments when they meet certain criteria. The issue occurred because the enrollments in the course were changing before the course itself met the requirements to be monitored and updated by ILP. The fix for this issue was to reprovision the course. Reprovisioning treats the course information as ‘new’ regardless of if it had already been updated, making the Canvas course info match the Banner SIS course info. This solved the individual reported issues, but we needed to reprovision all of the courses, and continue to reprovision throughout the semester. Based on research in ILP forums, this is the solution for most institutions who encounter this issue. ‌ On 8/24/26 around 3 PM, we reprovisioned all UAF courses using the ‘bulk job’ tool in ILP. We then validated course enrollments from a few new tickets that had come in to ensure the fix had the intended effect. Courses that had been missing enrollments were corrected. ‌ On 8/24/26 at 5 PM we received reports of Canvas courses disappearing from students and instructors. Upon investigation, we found the courses affected were all cross-listed and the instructor had manually changed the system generated configuration by either cross-listing additional courses, or de-cross-listing courses. Instructors are able to do this in the Canvas platform with any courses they are listed as the instructor in. When we reprovisioned, the system changed the configurations of the Canvas courses to match Banner and this undid whatever the instructor had done. ‌ On 8/25/26 9 AM we began a degradation of service outage for Canvas as more Canvas service tickets came in. We communicated with all administrators advising them of the situation and to not cross-list courses in Canvas until we had more information. We posted an announcement to instructors and admins on the Canvas platform about the outage. We removed the permission for instructors in Canvas to be able to cross-list/de-cross-list their courses. We assessed the number of courses potentially impacted, and communicated with the instructors of record for each course.  ‌ On 8/25/26 at 12 PM NTS-SE put out guidance to instructors to contact the Registrar if the system generated Canvas courses did not match what the instructor wanted. We discovered that instructors frequently cross-list courses across modalities in Canvas so they can manage all sections for a course in a single course shell. Canvas sections functionality allows them to do this without requiring them to expose cross-listed enrollments to each other. This is an important distinction between Canvas cross-listing and Registrar cross-listing: the term cross-listing/stacking for the Registrar means the enrollments are pooled together and it is expected that the students will be exposed to each other. Registrar policy prohibits cross-listing across modalities. This is a result of Faculty Senate concerns for anonymity in student course evaluations where a student could be identified by the modality of their response. Additional guidance was provided telling instructors to contact the NTS help desk for the recovery of any lost Canvas course content. These solutions did not work for many instructors who rely on the ability to cross-list in Canvas. ‌ On 8/25/26 at 4 PM  NTS-SE, Registrar, and OIT-EAS working group met to review and test settings and options in ILP to get instructors out of work stoppage. The group identified a way to do reprovisioning without affecting cross-listed courses. The group identified the existing real-time update process that changes Canvas cross-list configurations. The group tested a fix to allow instructors to manually cross-list in Canvas, and then validated it in our test environment. The fix was to allow instructors to re-cross-list and/or submit NTS help desk tickets to have our teams re-cross-list and restore lost content. All future reprovisions will use a configuration that excludes cross-list information.The fix was communicated in an outage update and through a Canvas LMS platform announcement. The permissions for an instructor to be able to cross-list in Canvas were re-enabled. Administrators were informed that they could now cross-list for instructors. By 12 PM 8/26/26 The outage was moved to monitoring while we worked through tickets. By 9 AM 8/28/26 The outage was resolved. # Target State / Goal  This issue changed the target state. Instructors should be able to manually cross-list or de-cross-list their course shells in Canvas, regardless of how the courses are coded in Banner. The cross-listing configuration should NOT be altered or set by the Banner ILP feed, nor should the cross-list status be watched nor updated from real-time monitoring. Active users should experience consistent access to the same Canvas course shell after the initial provisioning by the Banner ILP system except when manually changed by the instructor, or by an administrator.

Is NTS and OIT System down right now?

Yes — NTS and OIT System is reporting a minor incident as of Oct 12, 4:54 AM UTC.

What is NTS and OIT System's current status?

NTS and OIT System: Partially Degraded Service. Alert24 checks NTS and OIT System's status page continuously and can notify you the moment it changes.

How do I get alerted when NTS and OIT System goes down?

Alert24 monitors NTS and OIT System and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.