Störungsverlauf von University Of Alaska

1. 19. August 2026 um 23:57 UTCmonitoring

   Einige AT & T-Mobilfunkkunden können derzeit keine Anrufe an Campus-Telefonnummern abschließen. Dieses problem wurde als mit dem netzwerk von at & t identifiziert, nicht mit unseren telefonsystemen oder diensten. Wir überwachen die situation und werden ein update bereitstellen, sobald bestätigt wird, dass die anrufe wieder normal funktionieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. August 2026 um 20:54 UTCidentified

   Wir haben Berichte erhalten, dass Kartenleser auf dem UAF-Campus derzeit Probleme haben. Das OIT PAWS-Team ist sich dessen bewusst und arbeitet aktiv daran, den Server, der dieses System kontrolliert, wiederherzustellen. Wir werden Updates in Intervallen von einer Stunde machen, während sie auf einen Fix hinarbeiten. Gebäudekoordinatoren kennen möglicherweise alternative Zugangsmethoden und Routen für bestimmte Räume, aber es gibt derzeit keinen weit verbreiteten Workaround. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems!

2. 16. August 2026 um 22:59 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 16. August 2026 um 23:56 UTCresolved

   OIT PAWS berichtet, dass der Server für Lenel Card Swipe Systeme erfolgreich neu gestartet wurde und in Betrieb ist.

4. 19. August 2026 um 21:25 UTCpostmortem

   # **Root Cause Analysis – Argus Server Incident** ## **Executive Summary** Der Argus-Server erlebte einen schnellen Verlust an verfügbarem Speicherplatz auf dem Windows C: Laufwerk. Während der Untersuchung identifizierte PAWS signifikante Festplattenaktivitäten, die innerhalb des Lenel Application Log Verzeichnisses auftreten. Der verfügbare Speicherplatz ging weiter zurück und erreichte schließlich etwa 37 MB. PAWS hat den Server sauber heruntergefahren, um zu verhindern, dass das Betriebssystem 0 verfügbaren Speicherplatz erreicht und möglicherweise zusätzliche Systemprobleme verursacht. PAWS hat das C:-Laufwerk erweitert und den Server erfolgreich wieder in Betrieb genommen. Nach der Wiederherstellung stabilisierte sich die Festplattenauslastung und es blieben etwa 20 GB freier Speicherplatz verfügbar. PAWS ist für die zugrunde liegende Windows-Server-Infrastruktur verantwortlich, verwaltet oder unterstützt die Lenel-Anwendung jedoch nicht. Die Ursache der erhöhten anwendungsgenerierten Festplattenaktivität wurde nicht ermittelt und erfordert eine Untersuchung durch den Anwendungsbesitzer / -anbieter. ## **Incident Impact** Der Argus-Server wurde während des Vorfalls und der Wiederherstellung der Infrastruktur nicht mehr verfügbar, was zu einer Unterbrechung der vom Server abhängigen Dienste führte. Die gemeldeten Auswirkungen umfassten die Funktionalität des Türkartenlesers auf dem Campus. ## ** Timeline ** ** Alle Zeiten sind Alaska Zeit. ** ** Ungefähr 11:04 Uhr - PAWS wurde über ein Problem mit dem Argus-Server informiert und meldete Auswirkungen auf die Türkartenleser auf dem Campus. Der damit verbundene Vorfall war TDX 991008. ** Ungefähr 11:23 Uhr ** - PAWS identifizierte schnell abnehmenden verfügbaren Speicherplatz auf dem Windows C: Laufwerk. Resource Monitor zeigte signifikante Schreibaktivität innerhalb: `C:\ProgramData\Ln\logs` PAWS versuchte, die verfügbare Festplattenkapazität wiederherzustellen; C: Auslastung stieg jedoch weiter an. Das C:-Laufwerk erreichte schließlich etwa **37 MB verfügbaren Platz**. PAWS hat die VM sauber heruntergefahren, um zu verhindern, dass das Windows-Systemlaufwerk 0 verfügbaren Speicherplatz erreicht und möglicherweise zusätzliche Betriebssystemprobleme verursacht. PAWS führte die notwendigen Infrastrukturarbeiten durch, um die Kapazität des Systemantriebs zu erhöhen. ** Ungefähr 15:34 Uhr** – Die Infrastrukturarbeiten wurden abgeschlossen und der Antrieb C: erweitert. Der Server wurde wieder online gebracht und PAWS verifizierte den normalen Server- und Festplattenbetrieb. ** Ungefähr 15.49 Uhr** – Der Server wurde als funktionsfähig gemeldet. Am folgenden Tag, C: blieb stabil bei etwa **19,9 GB frei **, ohne Wiederholung des schnellen Plattenverbrauchs. ## **Wurzelursache** Die unmittelbare Ursache für den Serverausfall war die Erschöpfung der verfügbaren Kapazität auf dem Windows C: Laufwerk. Während des Vorfalls beobachtete PAWS signifikante Festplattenschreibaktivitäten innerhalb des Lenel-Anwendungsprotokollverzeichnisses: `C:\ProgramData\Ln\logs` Diese Aktivität verbrauchte schnell die verbleibende verfügbare Kapazität auf dem Systemlaufwerk. Der Grund für die erhöhte anwendungsgenerierte Festplattenaktivität wurde **nicht ermittelt**. PAWS ist für die Verwaltung der zugrunde liegenden Serverinfrastruktur verantwortlich, verwaltet, konfiguriert oder unterstützt die Lenel-Anwendung jedoch nicht. Die Bestimmung, warum die Anwendung die erhöhte Festplattenaktivität erzeugt hat, erfordert eine Untersuchung durch den Anwendungsbesitzer / -anbieter und liegt außerhalb des Anwendungsbereichs dieser Infrastruktur RCA. ## **Beitragender Faktor** ### **Limited Available System Disk Capacity** Der Server hatte keine ausreichende verbleibende C: Laufwerkskapazität, um den unerwarteten Anstieg der anwendungsgenerierten Festplattenauslastung zu absorbieren. Die verfügbare Kapazität sank schließlich auf etwa **37 MB **, so dass PAWS den Server herunterfahren musste, um zu verhindern, dass Windows 0 verfügbaren Speicherplatz erreicht. ## **Resolution** PAWS hat die folgenden Maßnahmen zur Wiederherstellung der Infrastruktur durchgeführt: * Untersuchte die schnell abnehmende C: Antriebskapazität. * Identifiziert das Quellverzeichnis, das mit der erhöhten Festplattenaktivität verbunden ist. * Laden Sie den Server sauber herunter, bevor das Systemlaufwerk 0 verfügbaren Speicherplatz erreicht hat. * Erhöht die verfügbare Kapazität für das Windows C: Laufwerk. * Der Server wurde wieder in Betrieb genommen. * Verifizierter normaler Server- und Festplattenbetrieb. * Fortsetzung der Überwachung der Festplattenauslastung nach Wiederherstellung. Nach der Erholung blieb das C: Laufwerk stabil bei ca. **19,9 GB frei **. ## ** Korrektive und vorbeugende Maßnahmen** ### **Disk Capacity Monitoring ** PAWS wird die Überwachung der Festplattenkapazität und die Alarmschwellen für den Argus-Server überprüfen, um eine ausreichende Benachrichtigung bereitzustellen, wenn sich die Systemlaufwerkskapazität kritischen Ebenen nähert. ### **Serverkapazität** PAWS wird die C: Drive-Auslastung weiterhin überwachen, um zu überprüfen, ob die zusätzliche Kapazität unter normalen Serverbedingungen ausreichend Betriebsmittel zur Verfügung stellt. ### **Antragsuntersuchung** Der Application Owner/Vendor muss die Ursache für den unerwarteten Anstieg der Lenel-generierten Festplattenaktivität ermitteln und eventuell erforderliche Korrekturmaßnahmen auf Anwendungsebene identifizieren. Anwendungskonfiguration, Protokollierung, Aufbewahrung und Behebung auf Anwendungsebene liegen außerhalb des Rahmens der PAWS-Serververwaltung. ## ** Aktueller Status** Der Argus-Server ist online und betriebsbereit. Das C:-Laufwerk blieb während des Follow-up-Monitorings stabil bei ca. **19,9 GB frei **, ohne dass sich der während des Vorfalls beobachtete schnelle Festplattenverbrauch wiederholte. PAWS betrachtet den **Server-Infrastruktur-Teil des Vorfalls als behoben**. Die zugrunde liegende Ursache des Lenel-Anwendungsverhaltens bleibt unbestimmt und erfordert eine Nachverfolgung durch den Anwendungsbesitzer / -anbieter.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. August 2026 um 19:02 UTCinvestigating

   Wir haben Berichte erhalten, dass Banner derzeit Probleme hat. Das OIT EAS-Team untersucht derzeit, und wir werden Updates in 1-Stunden-Intervallen durchführen. Ein funktionierender Workaround wurde identifiziert: Öffnen Sie ein privates oder inkognito Browserfenster, um auf Banner zuzugreifen. Wenn die Site immer noch langsam / nicht geladen ist, schließen und öffnen Sie ein anderes neues privates oder inkognito Fenster; es kann einige Versuche dauern, aber sobald eine zuverlässige Verbindung hergestellt wurde, können Sie diese Sitzung weiterhin verwenden, bis das Problem behoben ist! Vielen Dank für Ihre Geduld bei der Lösung dieses Problems!

2. 10. August 2026 um 20:03 UTCmonitoring

   Das OIT EAS-Team hat das Problem mit dem Banner identifiziert und einen Fix implementiert, der auf Wirksamkeit und Stabilität überwacht wird. Vielen Dank nochmals für Ihre Geduld bei der Lösung dieses Problems! Weitere Updates können Sie am Ende des Werktages um 17:00 Uhr erwarten oder wenn neue Informationen verfügbar werden.

3. 17. August 2026 um 16:53 UTCresolved

   Das OIT EAS-Team hat das Problem mit dem Banner behoben und bestätigt, dass der Fix stabil ist. Das Problem wurde am 10. August gelöst. Bitte melden Sie alle weiteren Probleme mit diesem Service an den IT-Helpdesk Ihres Campus und danken Sie erneut für Ihre Geduld bei der Lösung dieses Problems!

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. August 2026 um 16:55 UTCinvestigating

   Wir haben Berichte erhalten, dass die Iru-Web-Login-Option derzeit Probleme hat. Das NTS Technology Support Services-Team untersucht derzeit, und wir werden Updates in Abständen von 3 Stunden durchführen. Der Wechsel zum lokalen Login sollte es Ihnen ermöglichen, sich bei Ihrem Mac anzumelden. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems!

2. 3. August 2026 um 17:25 UTCinvestigating

   Das Team der NTS Technology Support Services (TSS) untersucht derzeit die Ursache dieses Problems. Wenn Sie sich nicht bei Ihrem UA Mac anmelden können, versuchen sie, zu Local Login zu wechseln. Um zum lokalen Login zu wechseln: 1. Klicken Sie auf das Profilsymbol (die Person in einem Kreis) in der oberen rechten Ecke des Bildschirms. 2. Wählen Sie Wechsel zum lokalen Login. 3. Geben Sie Ihre Anmeldeinformationen für die Universität in die Felder Benutzername und Passwort ein, die in der Nähe der unteren Mitte des Bildschirms erscheinen. 4. Click Sign Einloggen. Wenn Sie sich immer noch nicht einloggen können, wenden Sie sich bitte an Ihren lokalen IT Help Desk, um weitere Unterstützung zu erhalten. Vielen Dank für Ihre anhaltende Geduld, während wir auf eine vollständige Lösung hinarbeiten; wir werden weitere Updates in Abständen von 3 Stunden durchführen und sobald neue Informationen verfügbar sind.

3. 3. August 2026 um 18:02 UTCinvestigating

   Das NTS TSS-Team untersucht derzeit die Ursache dieser Probleme. Die Iru-Eingabeaufforderung zur Synchronisierung Ihrer Passwörter kann so gut wie möglich ignoriert werden, während wir untersuchen, warum sie aufgefordert wird. Wenn Sie sich nicht bei Ihrem UA Mac anmelden können, versuchen sie, zu Local Login zu wechseln. Um zum lokalen Login zu wechseln: 1. Klicken Sie auf das Profilsymbol (die Person in einem Kreis) in der oberen rechten Ecke des Bildschirms. 2. Wählen Sie Wechsel zum lokalen Login. 3. Geben Sie Ihre Anmeldeinformationen für die Universität in die Felder Benutzername und Passwort ein, die in der Nähe der unteren Mitte des Bildschirms erscheinen. 4. Click Sign Einloggen. Wenn Sie sich immer noch nicht einloggen können, wenden Sie sich bitte an Ihren lokalen IT Help Desk, um weitere Unterstützung zu erhalten. Vielen Dank für Ihre anhaltende Geduld, während wir auf eine vollständige Lösung hinarbeiten; wir werden weitere Aktualisierungen in Abständen von 1 Stunde vornehmen und sobald neue Informationen verfügbar sind.

4. 3. August 2026 um 19:44 UTCinvestigating

   Das NTS TSS-Team untersucht weiterhin die Ursache dieser Probleme. Weitere Updates gibt es derzeit nicht. Die Iru-Eingabeaufforderung zur Synchronisierung Ihrer Passwörter kann so gut wie möglich ignoriert werden, während wir untersuchen, warum sie aufgefordert wird. Wenn Sie sich nicht bei Ihrem UA Mac anmelden können, versuchen sie, zu Local Login zu wechseln. Um zum lokalen Login zu wechseln: 1. Klicken Sie auf das Profilsymbol (die Person in einem Kreis) in der oberen rechten Ecke des Bildschirms. 2. Wählen Sie Wechsel zum lokalen Login. 3. Geben Sie Ihre Anmeldeinformationen für die Universität in die Felder Benutzername und Passwort ein, die in der Nähe der unteren Mitte des Bildschirms erscheinen. 4. Click Sign Einloggen. Wenn Sie sich immer noch nicht einloggen können, wenden Sie sich bitte an Ihren lokalen IT Help Desk, um weitere Unterstützung zu erhalten. Vielen Dank für Ihre anhaltende Geduld, während wir auf eine vollständige Lösung hinarbeiten; wir werden weitere Aktualisierungen in Abständen von 1 Stunde vornehmen und sobald neue Informationen verfügbar sind.

5. 3. August 2026 um 22:35 UTCmonitoring

   Wir haben ein aktuelles Problem behoben, das durch eine unerwartete Änderung der Duo-Authentifizierung verursacht wurde, die sich auf verwaltete macOS-Computeranmeldungen auf dem gesamten Campus ausgewirkt hat. Wenn Sie einen von der Universität verwalteten Mac verwenden, wird Ihre Anmeldeerfahrung jetzt auf den normalen Betrieb wiederhergestellt. Wenn Sie sich jedoch nach diesem Fix zum ersten Mal wieder in Ihren Computer einloggen, werden möglicherweise ein oder zwei zusätzliche Duo-Authentifizierungsaufforderungen angezeigt. Wenn Sie sich heute zum ersten Mal bei Ihrem verwalteten Mac anmelden: 1. Geben Sie Ihre üblichen Kontodaten auf dem primären macOS-Anmeldebildschirm ein. 2. Füllen Sie die Duo-Eingabeaufforderung(en): Sie werden möglicherweise aufgefordert, sich über Duo eine zusätzliche Zeit zu authentifizieren, da die Systemberechtigungen aktualisiert und mit Ihrem Konto neu synchronisiert werden. 3. Genehmigen Sie die Anfrage wie gewohnt auf Ihrer Duo Mobile App, Ihrem Hardware-Token oder über Ihre bevorzugte MFA-Methode. 4. Wählen Sie Weiter unter Lassen Sie uns Ihr Konto sicher eingeben. 5. Wählen Sie Weiter unter der Eingabeaufforderung Anmeldemethode einrichten. Wenn Sie weiterhin Anmeldefehler, wiederholte Aufforderungen zur Synchronisierung von Passwörtern beim Anmelden oder andere Probleme beim Anmelden an Ihrem Mac haben, wenden Sie sich bitte an Ihren Campus IT Helpdesk.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 17:46 UTCidentified

   Der Zugriff auf vdi.alaska.edu ist nicht verfügbar, aber die Ursache des Ausfalls wurde identifiziert. Jeder Desktop-Zugriff über vdi.alaska.edu und möglicherweise der dicke Client können von dieser Adresse aus nicht auf virtuelle Maschinen zugreifen oder diese verwenden, bis das Problem behoben ist.

2. 24. Juli 2026 um 18:55 UTCidentified

   UA hat das Problem mit dem Zugriff auf vdi.alaska.edu identifiziert und arbeitet daran, es zu beheben. Jeder Desktop-Zugriff über vdi.alaska.edu und möglicherweise der dicke Client können virtuelle Maschinen von dieser Adresse aus nicht verwenden. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems. Bitte erwarten Sie ein Update um 11:50 Uhr und stündliche Updates danach.

3. 24. Juli 2026 um 20:12 UTCidentified

   UA hat das Problem mit dem Zugriff auf vdi.alaska.edu identifiziert und arbeitet daran, es zu beheben. Jeder Desktop-Zugriff über vdi.alaska.edu und möglicherweise der dicke Client können virtuelle Maschinen von dieser Adresse aus nicht verwenden. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems. Bitte erwarten Sie ein Update um 12:50 Uhr und stündliche Updates danach.

4. 24. Juli 2026 um 20:55 UTCidentified

   UA hat das Problem mit dem Zugriff auf vdi.alaska.edu identifiziert und arbeitet daran, es zu beheben. Jeder Desktop-Zugriff über vdi.alaska.edu und möglicherweise der dicke Client können virtuelle Maschinen von dieser Adresse aus nicht verwenden. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems. Bitte erwarten Sie ein Update um 1:50 Uhr und stündliche Updates danach.

5. 24. Juli 2026 um 22:35 UTCidentified

   UA hat das Problem mit dem Zugriff auf vdi.alaska.edu identifiziert und arbeitet daran, es zu beheben. Jeder Desktop-Zugriff über vdi.alaska.edu und möglicherweise der dicke Client können virtuelle Maschinen von dieser Adresse aus nicht verwenden. Vielen Dank für Ihre Geduld bei der Lösung dieses Problems. Bitte erwarten Sie ein Update um 17:00 Uhr.

6. 25. Juli 2026 um 00:03 UTCmonitoring

   UA hat das Problem mit vdi.alaska.edu behoben und bestätigt, dass der Fix stabil ist. Dies wird in der Überwachung bis zum Ende des Geschäfts um 17:00 Uhr platziert. Bitte melden Sie alle weiteren Probleme mit diesem Service an den IT-Helpdesk Ihres Campus und danken Sie erneut für Ihre Geduld bei der Lösung dieses Problems!

7. 25. Juli 2026 um 01:06 UTCresolved

   UA hat das Problem mit vdi.alaska.edu behoben und bestätigt, dass der Fix stabil ist. Bitte melden Sie alle anhaltenden Probleme mit diesem Service an den IT-Helpdesk Ihres Campus und danken Sie erneut für Ihre Geduld bei der Lösung dieses Problems!

8. 19. August 2026 um 21:26 UTCpostmortem

   [vdi.alaska.edu](http://vdi.alaska.edu) Abgelaufene Unified Access Gateway Zertifikate. Datum Uhrzeit: 23.07.2026 16.00 Uhr. # Hintergrund [vdi.alaska.edu](http://vdi.alaska.edu) bietet dem Benutzer Zugriff auf die VDI-Umgebung von VMware/Omnissa Horizon. Beide Unified Access Gateway-Appliances (existieren auf der VXrail-Plattform) bieten die externe Zugriffsebene für Benutzer, die sowohl auf dem Campus als auch aus der Ferne auf ihre VDI zugreifen möchten. # Zusammenbruch des Problems Beide Zertifikate für jede UAG liefen am 23. Juli, 15.59 Uhr 2026 ab. Das Problem wurde am Freitagmorgen des 24. Juli um 8:30 Uhr festgestellt, als Benutzer berichteten, dass sie bei der Lösung auf [vdi.alaska.edu] (http://vdi.alaska.edu) nicht auf ihre "My Desktop" VDI-Umgebungen zugreifen konnten. Wenn ein Benutzer versucht hat, über seinen Browser auf [vdi.alaska.edu](http://vdi.alaska.edu) zu antworten, erhielt er eine Benachrichtigung „Ihre Verbindung ist nicht privat und wurde dann daran gehindert, die [vdi.alaska.edu](http://vdi.alaska.edu) zu erreichen. Horizon Page überhaupt. Maßnahmen zur Wiederherstellung des Dienstes: Angeforderte Verlängerungsbescheinigung von PAWS. Dieses Zertifikat enthielt den primären Domainnamen [vdi.alaska.edu](http://vdi.alaska.edu), enthielt aber auch die alternativen Namen \(beide UAG-Namen\) [fbk-uag1.apps.ad.alaska.edu](http://fbk-uag1.apps.ad.alaska.edu) [fbk-uag2.apps.ad.alaska.edu](http://fbk-uag2.apps.ad.alaska.edu) [fbk-uag1.io.apps.ad.alaska.edu](http://fbk-uaf1.io.alaska.edu) [fbk-uag2.io.alaska.edu](http://fbk-uag2.io.alaska.edu) Dauer des Ausfalls und Zeitpunkt, zu dem der Dienst wiederhergestellt wurde: Donnerstag, 23. Juli 4:00 Uhr - Freitag, der 24. 14:00 Uhr. #Zielstaat / Ziel Beide UAGs sollten kontinuierlich gültige, vertrauenswürdige Zertifikate und externen und internen VDI-Zugang vorlegen # Wurzelursachenanalyse # Beide UAG-Appliances präsentierten abgelaufene TLS-Zertifikate. TSS erhielt eine Liste von VXrail-Server-Appliances, die geschätzte Zeiten hatten, zu denen ihre Zertifikate abliefen. Beide UAG-Geräte waren nicht in dieser Liste, so dass wir nicht in der Lage waren zu diktieren, wann ihre Zertifikate ablaufen würden. # Gegenmaßnahmen entwickeln Ich habe eine Master-Zertifikatstabelle erstellt, die jetzt sowohl die Zertifikatsinformationen von UAG als auch das Ablaufdatum enthält. Ich teile es mit unseren TSS-Teamleitern, damit wir die erwarteten Zertifikatsabläufe in Zukunft weiterhin überwachen können. Angeforderter Zugriff auf den Certinext-Service für zukünftige Zertifikatsverlängerungen. Zeitplan für die Durchführung: Die oben genannten sollten es uns ermöglichen, die Zertifikate anzufordern und umzusetzen, bevor sie auf beiden UAGs ablaufen, bevor sie ablaufen. # Follow Up / Review Überprüfen Sie das Ablaufdatum von Zertifikaten auf beiden UAGs, indem Sie die Master-Zertifikatstabelle überwachen. Bitten Sie PAWS, das Zertifikat zu erneuern, einen kurzen CAB-Ausfall zu planen, das Zertifikat auf beide UAGs anzuwenden und dann zu bestätigen, dass die Erneuerung erfolgreich war und der Zugriff erfolgt

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Mai 2026 um 16:26 UTCinvestigating

   We have received reports that Banner Admin is currently experiencing issues at login. A workaround has been identified for some users: attempt to load https://banner.alaska.edu/ in new incognito/private browser windows until the login screen successfully loads. The OIT Enterprise Applications Services (EAS) team is currently investigating, and we will be making updates at 1-hour intervals. Thank you for your patience during the resolution of this issue!

2. 29. Mai 2026 um 17:01 UTCmonitoring

   Ellucian, the vendor for Banner, has identified the issue and implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect another update at the end of the business day (5:00PM) or if new information becomes available.

3. 30. Mai 2026 um 01:01 UTCresolved

   The fix applied to Banner Admin has remained stable, and we are considering the outage resolved at this time. Please report any continued issues with this service to your campus's IT helpdesk, and thank you again for your patience during its resolution!

4. 1. Juli 2026 um 18:10 UTCpostmortem

   UAOnline and Banner Admin Login Issue Problem Impact Analysis Event Occurrence: May 28, 2026 4am to 11:15am, May 29, 2026 4am to 9am # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. These systems are hosted in Ellucian cloud and require period maintenance including security certificate updates for trust between UA and Ellucian systems. The Banner software periodically has system defects that are addressed by daily application restarts. # Break Down of the Problem ‌ On May 28th at 6:56am, a notice was sent to the Banner team through slack that a person was receiving an error when attempting to access the Employee Dashboard. The vendor Ellucian was notified of the event and identified the issue and implemented a work around. On May 29th at 8:11am, the same issue was reported through the Banner team slack channel for Banner Admin. The same ticket opened the prior day was used to report the issue and they used the same work around from the day before to restore service prior to 9:00am. # Target State / Goal Banner self service \(Employee Dashboard\) and Banner Admin services should be available to customers 24/7 except during pre-defined maintenance windows. # Root Cause Analysis ‌ Ellucian in preparation for an upcoming security certificate renewal staged changes in the production environment for the following weekend’s activity. There were mitigations in place due to Banner product defects that would restart Banner service instances daily at 4am. The restart process triggered the inclusion of these new certificates, causing a mismatch of certificates that prevented Single Sign On services from connecting for both Banner admin and the employee self service module. # Develop Countermeasures ‌ * Complete the implementation of the new certificates. * Provide feedback to the vendor to ensure their staff are properly equipped to avoid this in the future. # Implementation of Countermeasures May 30, 7:00 PM: Complete implementation of certificate change over for the whole system. June 2, 11:00AM: Convey feedback to vendor on how they need to change. # Follow Up / Review May 30-31: Validate certificate replacement is working for all systems. June 2: Vendor notified and RCA was provided by vendor, confirming what occurred.

1. 28. Mai 2026 um 16:02 UTCinvestigating

   We have received reports that forms in Banner admin are not loading, and UAOnline's Employee login is experiencing authentication issues. The OIT EAS team is currently reaching out to the vendor, and we will be making updates at 30-minute intervals. Thank you for your patience during the resolution of this issue!

2. 28. Mai 2026 um 16:36 UTCinvestigating

   OIT EAS has contacted the vendor for Banner and are monitoring their communication channels for updates. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!

3. 28. Mai 2026 um 17:06 UTCinvestigating

   OIT EAS reports the vendor's technicians are engaged and working on both Banner/UAOnline issues experienced. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!

4. 28. Mai 2026 um 19:03 UTCinvestigating

   The issue is continuing to be worked, and there is no new information available at this time. We will continue to make updates as new information becomes available and at 30-minute intervals. Thank you again for your time and patience while we work towards a resolution!

5. 28. Mai 2026 um 19:16 UTCmonitoring

   Ellucian, the vendor for Banner, has identified the issue and implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.

6. 29. Mai 2026 um 01:49 UTCresolved

   The fix applied to Banner Admin and the UAOnline Employee Dashboard has remained stable, and we are considering the outage resolved at this time. 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!

7. 1. Juli 2026 um 18:03 UTCpostmortem

   UAOnline and Banner Admin Login Issue Problem Impact Analysis Event Occurrence: May 28, 2026 4am to 11:15am, May 29, 2026 4am to 9am # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. These systems are hosted in Ellucian cloud and require period maintenance including security certificate updates for trust between UA and Ellucian systems. The Banner software periodically has system defects that are addressed by daily application restarts.  # Break Down of the Problem ‌ On May 28th at 6:56am, a notice was sent to the Banner team through slack that a person was receiving an error when attempting to access the Employee Dashboard. The vendor Ellucian was notified of the event and identified the issue and implemented a work around. On May 29th at 8:11am, the same issue was reported through the Banner team slack channel for Banner Admin. The same ticket opened the prior day was used to report the issue and they used the same work around from the day before to restore service prior to 9:00am. # Target State / Goal  Banner self service \(Employee Dashboard\) and Banner Admin services should be available to customers 24/7 except during pre-defined maintenance windows. # Root Cause Analysis  ‌ Ellucian in preparation for an upcoming security certificate renewal staged changes in the production environment for the following weekend’s activity. There were mitigations in place due to Banner product defects that would restart Banner service instances daily at 4am. The restart process triggered the inclusion of these new certificates, causing a mismatch of certificates that prevented Single Sign On services from connecting for both Banner admin and the employee self service module. # Develop Countermeasures  ‌ * Complete the implementation of the new certificates. * Provide feedback to the vendor to ensure their staff are properly equipped to avoid this in the future. # Implementation of Countermeasures May 30, 7:00 PM: Complete implementation of certificate change over for the whole system.  June 2, 11:00AM: Convey feedback to vendor on how they need to change.  # Follow Up / Review May 30-31: Validate certificate replacement is working for all systems.  June 2: Vendor notified and RCA was provided by vendor, confirming what occurred.

1. 16. Mai 2026 um 16:20 UTCinvestigating

   There is an Active Directory issue that is preventing users from logging into certain systems. The PAWS/Networking/Security teams are actively troubleshooting and investigating the issue.

2. 16. Mai 2026 um 17:49 UTCinvestigating

   An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.

3. 16. Mai 2026 um 18:24 UTCinvestigating

   An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.

4. 16. Mai 2026 um 19:23 UTCinvestigating

   There are no new updates as of 11:21AM. Reporting will continue until the end of day at 5PM. An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.

5. 16. Mai 2026 um 20:21 UTCinvestigating

   There are no new updates as of 12:20PM. The issue is continuing to be investigated and reporting will continue until the end of day at 5PM. An Active Directory issue is currently affecting UAF Servers and Services. The PAWS, Networking, and Security teams are actively troubleshooting and investigating the issue. A possible cause is being investigated and an update will be sent out as soon as it's identified. If you are a user logging into a server remotely using VDI, VPN, or other services, such as WiFi, that use your UA AD credentials, they may show as invalid. The cause is still being identified and the scope of the affected systems and services are still being assessed.

6. 16. Mai 2026 um 21:31 UTCinvestigating

   Update (1:30 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.

7. 16. Mai 2026 um 22:55 UTCinvestigating

   Update (2:45 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.

8. 16. Mai 2026 um 23:34 UTCinvestigating

   Update (3:33 PM): The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams are actively troubleshooting a potential cause. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be shared as soon as a cause is identified, with continuous reporting through 5:00 PM.

9. 17. Mai 2026 um 07:00 UTCinvestigating

   The Authentication Issues affecting UAF servers and services is still under investigation. The PAWS, Networking, and Security teams will continue remediation efforts tomorrow morning at 8:00 AM. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here tomorrow morning. Thank you for your patience.

10. 17. Mai 2026 um 15:52 UTCinvestigating

    The Authentication Issues affecting UAF servers and services are still under investigation. The PAWS, Networking, and Security teams will continue remediation efforts this morning at 8:00 AM. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here later today. Thank you for your patience.

11. 17. Mai 2026 um 21:03 UTCinvestigating

    As of 1PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. We will post more information as soon as it's available. User Impact: The UAF Devices Portal, Wi-Fi, Remote logins via VDI, VPN, or other services using UA AD credentials may fail or show as invalid. Further updates will be posted here later today. Thank you for your patience while we find a solution.

12. 18. Mai 2026 um 01:19 UTCidentified

    As of 5PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. We will post more information as soon as it's available. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid. Our next scheduled update is 11PM. Thank you for your patience while we find a solution.

13. 18. Mai 2026 um 07:03 UTCidentified

    As of 11PM on Sunday, May 17th, our teams are still actively troubleshooting the authentication issues. Teams are working with Cisco and Microsoft to investigate the cause. The next update will be tomorrow at 7AM. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid.

14. 18. Mai 2026 um 15:03 UTCidentified

    As of 7AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. The next update will be later this morning at 8AM. At this time, university Wi-Fi, VPN and VDI services have been restored. User Impact: The UAF Devices Portal or other services using UA AD credentials may fail or show as invalid.

15. 18. Mai 2026 um 16:14 UTCidentified

    As of 8AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after the 9AM meeting with diagnostic teams from this weekend. The next update will be later this morning at 9AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.

16. 18. Mai 2026 um 17:14 UTCidentified

    As of 9AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after meeting with diagnostic teams from this weekend. The next update will be later this morning at 10AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.

17. 18. Mai 2026 um 18:18 UTCidentified

    As of 10AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be available after meeting with diagnostic teams from this weekend. The next update will be later this morning at 11AM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.

18. 18. Mai 2026 um 19:02 UTCidentified

    As of 11AM on Monday, May 18th, the current fixes in place are holding steady. Our teams are working with Cisco and Microsoft on troubleshooting the authentication issues. More information will be posted as soon as it's available. The next update will be later today at 12PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.

19. 18. Mai 2026 um 20:17 UTCidentified

    As of 12PM on Monday, May 18th, the current fixes in place are still holding steady. Our teams are continuing to work with Cisco and Microsoft on troubleshooting the authentication issues. More information will be posted as soon as it's available. The next update will be later today at 1PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. *You may have to clear your cache or use an incognito/private browsing window access the UAF Devices Portal. For help with this, call the NTS Service Desk. User Impact: Some services using UA AD credentials may still fail or show as invalid.

20. 18. Mai 2026 um 21:36 UTCmonitoring

    As of 1PM on Monday, May 18th, while we are in monitoring mode, all impacted systems have been restored and continue to be stable. More information will be posted as soon as it's available. The next update will be later today at 2PM. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.

21. 19. Mai 2026 um 00:18 UTCmonitoring

    As of 3PM on Monday, May 18th, all impacted systems have been restored and continue to be stable. The next update will be 8AM tomorrow. If you continue to experience service login errors, please contact the NTS Service Desk. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.

22. 19. Mai 2026 um 16:21 UTCmonitoring

    As of 8AM on Tuesday, May 19th, all impacted systems have been restored and continue to be stable. The next update will be 8AM tomorrow. If you continue to experience service login errors, please contact the NTS Service Desk. At this time, university Wi-Fi, UAF Devices Portal, VPN and VDI services have been restored. User Impact: Some services using UA credentials may still fail or show as invalid.

23. 20. Mai 2026 um 16:00 UTCmonitoring

    As of 8AM on Wednesday, May 20th, the primary impacted services have been restored and are currently stable under monitoring. The next update will be tomorrow at 8AM, unless there are any significant changes. At this time, university Wi-Fi, UAF Devices Portal, VPN, and VDI services have been restored.

24. 21. Mai 2026 um 16:30 UTCmonitoring

    As of 8AM on Thursday, May 21st, the primary impacted services have been restored and are currently stable under monitoring. The next update will be tomorrow at 8AM, unless there are any significant changes. At this time, university Wi-Fi, UAF Devices Portal, VPN, and VDI services have been restored.

25. 1. Juni 2026 um 17:05 UTCresolved

    Our teams have resolved the issue with the Authentication service, and confirmed the fix to be stable. 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!

1. 15. Mai 2026 um 22:52 UTCinvestigating

   We have received reports that ELMO is currently experiencing issues. The UAS ELMO team is currently investigating, and we will be making updates at 30 minute intervals. Thank you for your patience during the resolution of this issue!

2. 15. Mai 2026 um 23:13 UTCmonitoring

   The UAS ELMO team has identified the issue with ELMO service and has implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.

3. 16. Mai 2026 um 00:57 UTCmonitoring

   The affected components of ELMO appear to be stable. We will continue monitoring the stability of the fix over the weekend, and you can expect a final update at the start of business (8:00AM) Monday if there is no new information until then. Thank you again for your patience during the resolution of this issue!

4. 18. Mai 2026 um 16:25 UTCresolved

   The UAS ELMO team has resolved the issue with the ELMO, and confirmed the fix to be stable. 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!

1. 11. Mai 2026 um 17:23 UTCmonitoring

   We have received reports that UAOnline Employee Login is currently experiencing issues. The OIT Enterprise Applications (EAS) team is aware and has identified the cause. This issue appears to be related to an update to Banner over the weekend that is causing issues for some users. EAS is currently working with the vendor, Ellucian towards a permeant fix. For users experiencing issues, there is a workaround. If getting an error, simply change the "UAA" in the url to either "UAF" or "UAS". Once logged into UAOnline, you should be able to log out and use the Employee Login option without issue. We will make updates on this situation at the end of the business day 5:00pm and as new information becomes available. Thank you for your patience during the resolution of this issue!

2. 12. Mai 2026 um 00:58 UTCmonitoring

   There are still some users currently experiencing issues with the UAOnline Employee Login. The EAS team is continuing to work with the vendor, Ellucian, towards a permeant fix. For users experiencing issues, there is a workaround. If getting an error stating that the "MEP code is invalid", simply change the "UAA" in the url of the page displaying the error to either "UAF" or "UAS". Once logged into UAOnline, you should be able to log out and use the Employee Login option without issue. If the issue persists, please contact the NTS Service Desk. We will make updates on this situation at the start of the business day 8:00am and as new information becomes available. Thank you for your patience during the resolution of this issue!

3. 12. Mai 2026 um 16:23 UTCmonitoring

   The OIT EAS team has identified the issue with the UAOnline Employee Login and has implemented a fix, which is being monitored for effectiveness and stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.

4. 12. Mai 2026 um 16:35 UTCresolved

   The OIT EAS team has resolved the issue with the UAOnline Employee Login, and confirmed the fix to be stable. 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!

1. 28. April 2026 um 01:06 UTCinvestigating

   We have received reports that our ticketing system, TeamDynamix (TDX), is currently experiencing issues processing replies to generated emails. The UAA Enterprise Service Management team is currently investigating, and we will be making updates when we open at 8:00am Alaska Time. Thank you for your patience during the resolution of this issue!

2. 28. April 2026 um 15:56 UTCmonitoring

   UAA ESM has applied a workaround and the affected components of TDX appear to be stable. We will continue monitoring the stability of the fix until the end of the business day (5:00PM) today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!

3. 29. April 2026 um 00:57 UTCresolved

   The UAA ESM team has resolved the issue with the affected components of TDX, and confirmed the fix to be stable. 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!

4. 27. Mai 2026 um 18:26 UTCpostmortem

   This outage was caused by an issue on our vendor’s side. They released the following information: “The issue was caused by a misconfiguration during a maintenance deployment and has now been fully resolved.“

1. 9. April 2026 um 18:59 UTCidentified

   We have received reports that the Banner Production instance (including UAOnline) is currently experiencing issues. The OIT Enterprise Applications Services team is aware and has contacted the vendor. We will be making updates at 1-hour intervals as they work towards a fix. Thank you for your patience during the resolution of this issue!

2. 9. April 2026 um 20:17 UTCidentified

   OIT EAS reports that Ellucian is going to perform a rolling restart of the affected components, so we expect to see services regain functionality one-at-a-time. We'll report on the status of each as new information becomes available, and at our 1-hour intervals! Thank you again for your time and understanding.

3. 9. April 2026 um 20:52 UTCmonitoring

   A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.

4. 10. April 2026 um 00:52 UTCmonitoring

   A fix has been implemented and users are reporting access. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM.

5. 10. April 2026 um 16:11 UTCinvestigating

   The affected components of Banner and UAOnline appear to be stable. We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 12:52PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!

6. 10. April 2026 um 22:03 UTCresolved

   The affected components of Banner are still operational, and we are considering the fix to be stable and this outage resolved. 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!

1. 8. April 2026 um 19:23 UTCinvestigating

   We have received reports that multiple Banner Self-Service services (including UAOnline) are currently unavailable. The OIT Enterprise Applications Services team has reached out to the vendor and is currently investigating, and we will be making updates at 1-hour intervals. Please contact your campus IT helpdesk if you notice other Banner components are affected. Thank you for your patience during the resolution of this issue!

2. 8. April 2026 um 19:48 UTCinvestigating

   Some users are reporting that functionality has returned, but are still experiencing slowness. We're waiting for further updates from the vendor, Ellucian, and will continue to make updates as new information becomes available and at 1-hour intervals. Thank you for your time.

3. 8. April 2026 um 20:24 UTCidentified

   Ellucian reports that they have marked our incident as high-priority, located the cause, and are currently working on a fix. Further updates will continue at 1-hour intervals and as new information becomes available. Thank you for your time!

4. 8. April 2026 um 21:33 UTCmonitoring

   A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.

5. 9. April 2026 um 01:04 UTCmonitoring

   A fix has been implemented and users are reporting access. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM.

6. 9. April 2026 um 16:00 UTCmonitoring

   The affected components of UAOnline appear to remain operational! We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 1:30PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!

7. 9. April 2026 um 19:05 UTCidentified

   UAOnline is experiencing slowness and timeouts as a result of a different incident, and details can be found here as we continue to follow that resolution: https://status.alaska.edu/incidents/2141hpy4lvlm

8. 9. April 2026 um 20:46 UTCresolved

   This issue with UAOnline was identified and the fix is stable.

9. 6. Mai 2026 um 18:33 UTCpostmortem

   UAOnline Partial Outages Problem Impact Analysis Event Occurrence: March \[15, 17, 20 , 23\] 2026 Employee Self Service; April 2, 2026 Employee Self Service; April 7, 2026 Finance Self Service; April 8, 2026 General Self Service  # Background UAOnline is the self service portal for Ellucian Banner used as the university’s Enterprise Resource Planning \(ERP\) system. Banner and UAOnline are hosted by the vendor Ellucian, also the maker of the product. From time to time during initial validation of new upgrades, not all defects are experienced. The self service components of Banner include General, Employee, Finance, and Student self service. All of these are separate applications that are made available under the heading UAOnline and navigable between each area after initial login.  # Break Down of the Problem Initially Employee Self Service \(ESS\) was impacted with unavailability on March 15, 17, and 20. Upon report of an issue with the instance the vendor was notified and the corrective action was to restart the service. Noted during these times that some end users were able to access the platform while others could not. On March 20th the service owner escalated further related to this issue. Ellucian shared 2 product defects related to ESS that they expected to cause the issue scheduled of the UA production environment in May.  Ellucian recommends instituting daily restarts of the Employee Self Service instances to occur in the UA daily maintenance window of 4am to 5am. The earliest Ellucian could schedule was March 25, resulting in another outage on March 23rd and an escalation response to Ellucian to restore service. On April 2nd, after mitigation was in place, ESS failed again and Ellucian further escalated to prepare a fix to address the product defect specifically for ESS. A patched version of ESS was deployed on April 3rd in TEST and validation was reported back to Ellucian on April 6th to go into production. Further issues with ESS were not identified. On April 7th, Finance Self Service\(FSS\) went down and was reported to Ellucian and Ellucian configured daily restarts. April 8th, General Self Service \(GSS\) was reported down and escalations were entered with Ellucian. On April 10, all self service apps were scheduled to be updated similarly to ESS with daily restarts. All but GSS were successful with this update. ‌ # Target State / Goal  The Banner and UAOnline services should be available 24 hours a day 7 days a week with the exception of scheduled and planned down time including the daily maintenance window. The system should always be responsive. # Root Cause Analysis  Ellucian’s review of the application hosts that were failing showed the available disk filling up related to a large amount of logs being created in a very short period of time. Ellucian attempted to mitigate this with a daily restart, but demonstrated during this time that the issue could manifest in just a few hours. Ellucian traced to specific product defects that they believed were causing the excessive logging issue. They attempted to mitigate this issue by establishing daily restarts and by creating a non-standard custom WAR file for deployment and management of each Self Service Application. Ellucian later discovered that there was a bug in the text manager product component that when using a MEP environment like UA has, could cause the excessive generation of error log messages which is likely what was filling the disk. Ellucian has released an update for each of the Self Service applications out of band to address the product defect.  # Develop Countermeasures  * Deploy updated version of self service software that addresses the product defect. # Implementation of Countermeasures ‌ * May 10, 2026 - All self service application with the expectation of Employee Self Service \(ESS\) will be updated to the version where the underlying product defect is corrected. ESS has a new defect that will prevent immediate updating.  * Future - Apply ESS tier 2 update which corrects the product defect, when the other dependent product defect is resolved.  ‌ # Follow Up / Review ‌ May 11, 2026: Verify all self service applications are working as expected.  July 5, 2026: Verify status of ESS to be upgraded.

1. 7. April 2026 um 18:58 UTCinvestigating

   We have received reports that Finance Self-Service Banner (the UAOnline 'Finance' tab) is currently experiencing issues. The OIT Enterprise Applications Services team has sent a high-priority ticket to the vendor, and we will be making updates at 3-hour intervals. Thank you for your patience during the resolution of this issue!

2. 7. April 2026 um 19:57 UTCmonitoring

   Ellucian has restarted the affected services; Finance SSB and its associated UAOnline tab appear to be functional again! We will monitor the stability of this fix and make another update at the end of the business day (5:00PM) today. Thank you again for your time while we followed the resolution of this issue!

3. 8. April 2026 um 00:59 UTCmonitoring

   Ellucian has restarted the affected services; Finance SSB and its associated UAOnline tab appear to be functional again. There have been no new developments, monitoring will continue until tomorrow morning at 8:00AM. Thank you again for your time while we followed the resolution of this issue.

4. 8. April 2026 um 16:09 UTCresolved

   The issue with Finance SSB, and its associated UAOnline tab, was identified. A fix was implemented and the solution is still working after being monitored all night. Marking this as resolved.

1. 2. April 2026 um 16:24 UTCinvestigating

   We have received reports that the Employee login for UAOnline (Employee SSB) is currently experiencing issues including slowness and intermittent login availability. The OIT Enterprise Applications Services team is currently investigating, and we will be making updates at 3-hour intervals. Thank you for your patience during the resolution of this issue!

2. 2. April 2026 um 18:03 UTCinvestigating

   Further reports indicate Faculty Self-Service (this includes the 'Faculty & Advisor Services' link in UAOnline) may also be impacted. OIT EAS has opened a ticket with the vendor for Banner, and are monitoring their channels of communication for updates. We will continue to make updates as new information becomes available, and at 3-hour intervals. Thanks so much for your time!

3. 2. April 2026 um 19:30 UTCinvestigating

   The vendor for Banner is currently investigating the cause of this issue. OIT EAS is monitoring their channels of communication for updates. Thank you for your continued patience as we work towards a full resolution. We will continue to make updates as new information becomes available, and at 3-hour intervals.

4. 2. April 2026 um 19:53 UTCinvestigating

   OIT EAS reports that the vendor has been instructed to restart the affected services, and are awaiting confirmation that the instructed actions have been taken. Once complete, the effectiveness of the solution will be determined. Thank you again for your patience! We will continue to make updates at 3-hour intervals and as new information becomes available.

5. 2. April 2026 um 20:39 UTCmonitoring

   The affected services have been reset, and Employee SSB and Faculty SSB through UAOnline both appear to be operational again. We will monitor the stability of this fix, and another update can be expected at the end of the business day (5:00pm) today! Please report any continued issues with Banner and UAOnline to your campus IT helpdesk. Thanks so much again for your time and patience as we followed the resolution of this incident.

6. 3. April 2026 um 01:02 UTCmonitoring

   The Employee SSB and Faculty SSB through UAOnline both are operational. We will continue to monitor the stability of this fix, and another update can be expected at the start of the business day (8:00am) tomorrow! Please report any continued issues with Banner and UAOnline to your campus IT helpdesk. Thanks so much again for your time and patience as we followed the resolution of this incident.

7. 3. April 2026 um 16:09 UTCmonitoring

   The affected components of UAOnline and Banner appear to remain operational! We will continue monitoring the stability of the fix until the 24-hour mark, at approximately 12:39PM today, and you can expect a final update at that time if there is no new information until then. Thank you again for your patience during the resolution of this issue!

8. 3. April 2026 um 22:15 UTCresolved

   We've received no further reports of UAOnline or Banner service degradation, and are marking this incident as resolved. Please report any issues with these services (and others!) to your campus IT helpdesk as usual. Thank you again, and happy Friday!

1. 1. April 2026 um 19:15 UTCidentified

   We have received reports that Banner and Banner-related services such as UAOnline are currently experiencing slow load times. The OIT Enterprise Applications Services (EAS) team is aware and is communicating with their vendor. We will be making updates at 3-hour intervals as they work towards a fix. Thank you for your patience during the resolution of this issue!

2. 1. April 2026 um 19:52 UTCidentified

   OIT EAS reports that the vendor is actively looking to resolve the issue, and at this time most services seem to be available again, including Banner and Employee Self-Service. Faculty Self-Service still appears to be down. We will continue to make updates at 3-hour intervals and as new information becomes available. Thank you for your time!

3. 1. April 2026 um 22:26 UTCidentified

   Ellucian is continuing to work towards a fix for this issue, and no new information has been relayed at this time. Faculty Self-Service appears to be the only service still affected; this includes the 'Faculty & Advisor Services' link in UAOnline. We will make further updates and as new information becomes available, and at the end of the business day (5:00pm) today. Thank you for your time!

4. 1. April 2026 um 22:48 UTCmonitoring

   Ellucian reports that the issue has been resolved, and are reviewing to ensure that the fix is permanent. We will monitor the stability of the fix until the beginning of the business day tomorrow (8:00am) and you can expect another update at that time. Please report any continued issues with Banner speed and functionality to your campus IT helpdesk. Thank you again for your time and patience as we followed the resolution of this issue!

5. 1. April 2026 um 23:46 UTCresolved

   OIT EAS reports that Banner and affected services are now fully operational, and expect the fix to be stable. The vendor has identified a root cause for recent Banner performance issues, and a longer-term fix is expected to be applied in May. Please report any continued issues with Banner and UAOnline, if they arise, to your campus IT helpdesk. Thanks so much for your time and patience as we followed the resolution of this incident.

1. 25. März 2026 um 19:13 UTCidentified

   UAF Facility Services has a planned power outage in Hess Village that is impacting network equipment in Hess Village. That power outage is planned to be complete by 1PM.

2. 26. März 2026 um 00:38 UTCresolved

   UAF Facilities Services has completed work in Hess Village and the impacted network equipment is operating without issue.

3. 8. April 2026 um 18:20 UTCpostmortem

   A scheduled power outage in Hess Village affected the wireless network in that area.

1. 23. März 2026 um 15:47 UTCinvestigating

   We have received reports that UAOnline is currently experiencing issues and the Employee Dashboard is intermittently accessible. The OIT Enterprise Application Services team is currently investigating, and we will be making updates at 1-hour intervals. Thank you for your patience during the resolution of this issue!

2. 23. März 2026 um 15:53 UTCinvestigating

   OIT EAS has re-escalated their existing ticket with the vendor (Ellucian). We will continue to make updates at 1-hour intervals and as new information becomes available. Thank you again for your time!

3. 23. März 2026 um 17:06 UTCinvestigating

   There has been no new information provided at this time. A ticket with the vendor for UAOnline (Ellucian) is ongoing. We will continue to make updates at 1-hour intervals and as new information becomes available. Thank you again for your time!

4. 23. März 2026 um 17:41 UTCmonitoring

   OIT EAS reports that the vendor has restarted the Employee Self-Service application, resolving the intermittent login issues, and the service is now being monitored for stability. Thank you again for your patience during the resolution of this issue! You can expect further updates at the end of the business day (5:00PM) or as new information becomes available.

5. 23. März 2026 um 17:51 UTCresolved

   OIT EAS has confirmed the fix to be stable. 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!

1. 20. März 2026 um 17:06 UTCidentified

   We have received reports that the UAOnline Self-Service/Employee Dashboard is currently experiencing issues. The OIT EAS team is aware and has identified the cause to be related to resource issues on the vendor's side; they have started a ticket with the vendor. We will be making updates at 1-hour intervals as they work towards a fix. Thank you for your patience during the resolution of this issue!

2. 20. März 2026 um 18:09 UTCmonitoring

   Vendor identified the issue, restarted the affected service, and function was restored. We are currently monitoring for any further issues.

3. 20. März 2026 um 18:12 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20. März 2026 um 18:14 UTCresolved

   Service is restored.

1. 17. März 2026 um 17:10 UTCinvestigating

   We have received reports that UAOnline is currently experiencing issues and the Employee Dashboard is intermittently accessible. The OIT Enterprise Application Services team is currently investigating, and we will be making updates at 3-hour intervals. Thank you for your patience during the resolution of this issue!

2. 17. März 2026 um 18:11 UTCresolved

   The OIT EAS team requested their vendor to perform a restart of affected services, and the Employee Dashboard in UAOnline appears to be fully operational again. 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!