Istoricul incidentelor University Of Alaska

1. 19 august 2026 la 23:57 UTCmonitoring

   În prezent, unii clienți de telefonie mobilă AT&T nu pot finaliza apelurile către numerele de telefon ale campusului. Acest aspect a fost identificat ca fiind originar din rețeaua AT&T, nu din sistemele sau serviciile noastre telefonice. Monitorizăm situația și vom oferi o actualizare odată ce apelurile sunt confirmate că funcționează normal din nou.

Traducere automată din actualizarea oficială a incidentului.

1. 16 august 2026 la 20:54 UTCidentified

   Am primit rapoarte că cititorii de cărţi din campusul UAF se confruntă în prezent cu probleme. Echipa OIT PAWS este conștientă și lucrează activ pentru a recupera serverul care controlează acest sistem. Vom face actualizări la intervale de o oră, în timp ce acestea lucrează spre un fix. Coordonatorii clădirilor pot fi conștienți de metodele de acces alternative și de rutele pentru anumite săli, însă nu există un proces general în acest moment. Vă mulțumim pentru răbdare în timpul soluționării acestei probleme!

2. 16 august 2026 la 22:59 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

3. 16 august 2026 la 23:56 UTCresolved

   OIT PAWS raportează că serverul pentru sistemele Lenel card swipe a fost repornit cu succes și este operațional.

4. 19 august 2026 la 21:25 UTCpostmortem

   # **Root Cause Analysis ## ** Rezumat executiv** Serverul Argus a experimentat o pierdere rapidă de spațiu disponibil pe Windows C: unitate. În timpul anchetei, PAWS a identificat o activitate semnificativă a discului care a avut loc în registrul de aplicații Lenel. Spaţiul disponibil pe disc a continuat să scadă şi în cele din urmă a atins aproximativ 37 MB. PAWS a închis cu ușurință serverul pentru a împiedica sistemul de operare să ajungă la 0 spațiu disponibil pe disc și poate provoca probleme suplimentare de sistem. PAWS a extins C: unitate și a returnat cu succes serverul la serviciu. După recuperare, utilizarea disk stabilizat și aproximativ 20 GB de spațiu liber a rămas disponibil. PAWS este responsabil pentru infrastructura serverelor Windows, dar nu administrează și nu suportă aplicația Lenel. Cauza creșterii activității discului generat de aplicații nu a fost determinată și necesită investigarea de către proprietarul/vendorul aplicației. ## **Incident Impact** Serverul Argus a devenit indisponibil în timpul activităților de recuperare a incidentelor și infrastructurii, ceea ce a dus la întreruperea serviciilor dependente de server. Impacturile raportate au inclus funcţionalitatea cititorului cardului de acces în campus. "Timeline" * Toate timpurile sunt Alaska timp.** **Aproximativ 11:04 AM** Incidentul asociat a fost TDX 991008. **Aproximativ 11:23 AM** Monitor de resurse a arătat o activitate de scriere semnificativă care are loc în cadrul: PAWS a încercat să recupereze capacitatea disponibilă de disc; totuși, C: utilizarea a continuat să crească. C: unitatea a ajuns în cele din urmă la aproximativ ** 37 MB din spațiul disponibil**. PAWS a închis VM pentru a împiedica motorul sistemului Windows să ajungă la 0 spațiu disponibil și poate provoca probleme suplimentare ale sistemului de operare. PAWS a realizat lucrările de infrastructură necesare pentru a crește capacitatea de acționare a sistemului. **Aproximativ 3:34 PM** Serverul a fost readus online și PAWS a verificat funcționarea normală a serverului și a discului. **Aproximativ 3:49 PM** Serverul a fost raportat operaţional. În ziua următoare, C: a rămas stabil la aproximativ ** 19,9 GB gratuit**, fără recurență a consumului rapid de disc. ## **Root Cause** Cauza imediată a întreruperii serverului a fost epuizarea capacității disponibile pe Windows C: unitate. În timpul incidentului, PAWS a observat o activitate semnificativă de scriere pe disc în registrul de aplicații Lenel: Această activitate a consumat rapid restul de capacitate disponibilă pe unitatea sistemului. Motivul care stă la baza creșterii activității discului generat de aplicații nu a fost determinat**. PAWS este responsabil pentru administrarea infrastructurii serverelor subiacente, dar nu administrează, configura sau susține aplicația Lenel. Stabilirea motivului pentru care cererea a generat o activitate pe disc sporită necesită o anchetă din partea proprietarului/vânzătorului aplicației și este în afara domeniului de aplicare al acestei infrastructuri RCA. ## ** Factor de contribuţie** ### **Limited Available System Disk Capacity** Serverul nu a avut suficient C rămas: capacitatea de unitate pentru a absorbi creșterea neașteptată a utilizării discului generat de aplicații. Capacitatea disponibilă a scăzut în cele din urmă la aproximativ ** 37 MB**, solicitând PAWS să închidă serverul pentru a împiedica Windows să ajungă la 0 spațiu disponibil pe disc. "Rezoluţia" PAWS a finalizat următoarele acțiuni de recuperare a infrastructurii: * Investigat scăderea rapidă C: capacitatea de conducere. * Identificat directorul sursă asociat cu activitatea de disc crescut. * Închideți cu ușurință serverul înainte ca unitatea de sistem să ajungă la 0 spațiu disponibil. * Creșterea capacității disponibile pentru Windows C: unitate. * Returnat serverul la serviciu. * Verified normal server and disk operation. * Continuarea monitorizării utilizării discului după recuperare. După recuperare, unitatea C: a rămas stabilă la aproximativ ** 19,9 GB gratuit**. ## **acţiuni corective şi preventive** ### **Disk Capacity Monitoring** PAWS va revizui monitorizarea capacității discului și pragurile de alertă pentru serverul Argus pentru a furniza o notificare suficientă atunci când capacitatea de acționare a sistemului se apropie de niveluri critice. ### **Server Capacity** PAWS va continua monitorizarea C: utilizarea motorului pentru a verifica dacă capacitatea suplimentară oferă o cameră de operare suficientă în condiții normale de server. Investigaţii de Aplicare Proprietarul/vendorul aplicației va trebui să determine cauza creșterii neașteptate a activității pe disc generate de Lenel și să identifice orice acțiuni corective la nivel de aplicație care pot fi necesare. Configurația aplicațiilor, logarea, păstrarea și remedierea nivelului de aplicare sunt în afara domeniului de aplicare al administrării serverului PAWS. ## **Current Status** Serverul Argus este online și operațional. C: unitatea a rămas stabilă la aproximativ **19,9 GB free** în timpul monitorizării follow-up, fără recidiva consumului rapid de disc observat în timpul incidentului. PAWS consideră partea de infrastructură **server a incidentului rezolvată**. Cauza principala a comportamentului aplicatiei Lenel ramane nedeterminata si necesita urmarire de catre proprietarul/vendorul aplicatiei.

Traducere automată din actualizarea oficială a incidentului.

1. 10 august 2026 la 19:02 UTCinvestigating

   Am primit rapoarte că Banner se confruntă în prezent cu probleme. Echipa OIT EAS investighează în prezent şi vom face actualizări la intervale de 1 oră. A fost identificat un cadru funcţional: deschideţi o fereastră privată sau incognito pentru a accesa Banner. Dacă site-ul este încă lent / nu se încarcă, închide și deschide o altă fereastră nouă privată sau incognito; poate dura câteva încercări, dar odată ce o conexiune de încredere este făcută, puteți continua să utilizați acea sesiune până când problema este rezolvată! Vă mulțumim pentru răbdare în timpul soluționării acestei probleme!

2. 10 august 2026 la 20:03 UTCmonitoring

   Echipa OIT EAS a identificat problema cu Banner și a implementat un fix, care este monitorizat pentru eficacitate și stabilitate. Vă mulţumesc din nou pentru răbdare în timpul soluţionării acestei probleme! Vă puteți aștepta la actualizări suplimentare la sfârșitul zilei de lucru 5:00 PM sau ca noi informații devin disponibile.

3. 17 august 2026 la 16:53 UTCresolved

   Echipa OIT EAS a rezolvat problema cu Banner, și a confirmat fix pentru a fi stabil. Problema a fost rezolvată pe 10 august. Vă rugăm să raportați orice probleme continue cu acest serviciu către biroul IT al campusului dvs. și vă mulțumesc din nou pentru răbdare în timpul rezoluției acestei probleme!

Traducere automată din actualizarea oficială a incidentului.

1. 3 august 2026 la 16:55 UTCinvestigating

   Am primit rapoarte că opțiunea Iru de conectare web se confruntă în prezent cu probleme. Echipa NTS Technology Support Services investighează în prezent şi vom face actualizări la intervale de 3 ore. Trecerea la autentificare locală ar trebui să vă permită să vă conectați în Mac dumneavoastră. Vă mulțumim pentru răbdare în timpul soluționării acestei probleme!

2. 3 august 2026 la 17:25 UTCinvestigating

   Echipa NTS Technology Support Services (TSS) investighează în prezent cauza acestei probleme. Dacă nu se pot conecta la UA Mac, încearcă să treacă la conectare locală. Pentru a trece la autentificare locală: 1. Faceți clic pe pictograma de profil (persoana din interiorul unui cerc) în colțul din dreapta sus al ecranului. 2. Selectați Comutarea la autentificare locală. 3. Introduceți acreditările de autentificare ale Universității în câmpurile de utilizator și parole care apar în apropierea centrului de jos al ecranului. 4. Faceți clic pe semn Să mă loghez. Dacă încă nu vă puteți conecta, vă rugăm să contactați biroul de asistență IT local pentru asistență suplimentară. Vă mulțumim pentru răbdarea dumneavoastră în timp ce lucrăm către o rezoluție completă; vom face actualizări suplimentare la intervale de 3 ore și pe măsură ce vor fi disponibile noi informații.

3. 3 august 2026 la 18:02 UTCinvestigating

   Echipa NTS TSS investighează în prezent cauza acestor probleme. Iru prompt pentru a sincroniza parolele dvs. este sigur de a ignora cel mai bine că sunteți capabil în timp ce noi investigăm de ce este determinat. Dacă nu se pot conecta la UA Mac, încearcă să treacă la conectare locală. Pentru a trece la autentificare locală: 1. Faceți clic pe pictograma de profil (persoana din interiorul unui cerc) în colțul din dreapta sus al ecranului. 2. Selectați Comutarea la autentificare locală. 3. Introduceți acreditările de autentificare ale Universității în câmpurile de utilizator și parole care apar în apropierea centrului de jos al ecranului. 4. Faceți clic pe semn Să mă loghez. Dacă încă nu vă puteți conecta, vă rugăm să contactați biroul de asistență IT local pentru asistență suplimentară. Vă mulțumim pentru răbdarea dvs. continuă în timp ce lucrăm către o rezoluție completă; vom face actualizări suplimentare la intervale de 1 oră și pe măsură ce noi informații devin disponibile.

4. 3 august 2026 la 19:44 UTCinvestigating

   Echipa NTS TSS continuă să investigheze cauza acestor probleme. Nu există alte actualizări în acest moment. Iru prompt pentru a sincroniza parolele dvs. este sigur de a ignora cel mai bine că sunteți capabil în timp ce noi investigăm de ce este determinat. Dacă nu se pot conecta la UA Mac, încearcă să treacă la conectare locală. Pentru a trece la autentificare locală: 1. Faceți clic pe pictograma de profil (persoana din interiorul unui cerc) în colțul din dreapta sus al ecranului. 2. Selectați Comutarea la autentificare locală. 3. Introduceți acreditările de autentificare ale Universității în câmpurile de utilizator și parole care apar în apropierea centrului de jos al ecranului. 4. Faceți clic pe semn Să mă loghez. Dacă încă nu vă puteți conecta, vă rugăm să contactați biroul de asistență IT local pentru asistență suplimentară. Vă mulțumim pentru răbdarea dvs. continuă în timp ce lucrăm către o rezoluție completă; vom face actualizări suplimentare la intervale de 1 oră și pe măsură ce noi informații devin disponibile.

5. 3 august 2026 la 22:35 UTCmonitoring

   Am rezolvat o problemă recentă cauzată de o schimbare neașteptată cu autentificarea Duo care a afectat login-uri de calculator MacOS gestionate în tot campusul. Dacă utilizați un Mac administrat de universitate, experiența ta de conectare este acum restaurat la operații normale. Cu toate acestea, prima dată când vă conectați înapoi în computerul dumneavoastră în urma acestei fix, puteți vedea unul sau două solicitări suplimentare de autentificare Duo. Când te-ai înscris la Mac pentru prima dată azi: 1. Introduceți acreditările obişnuite ale contului la ecranul de autentificare MacOS primar. 2. Completați Duo prompt (s): Puteți fi îndemnat să autentificați prin Duo un timp suplimentar ca permisiuni de sistem reîmprospătare și re-sincronizare cu contul. 3. Aprobati cererea pe aplicatia dvs. mobila Duo, token hardware, sau prin metoda preferata MAE ca de obicei. 4. Selectaţi Next la Lets păstra contul dvs. în siguranţă prompt. 5. Selectaţi Următorul la Setare o metodă de sign-in prompt. Dacă continuați să întâlniți erori de autentificare, solicitări repetate pentru a sincroniza parolele pe login, sau orice alte probleme logare în Mac, vă rugăm să ajungeți la campusul dvs. IT Helpdesk.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 17:46 UTCidentified

   Accesul la Vdi.alaska.edu nu este disponibil, dar cauza întreruperii a fost identificată. Orice acces desktop prin vdi.alaska.edu, și, eventual, clientul gros, nu va putea accesa sau utiliza mașini virtuale de la acea adresă până când problema a fost rezolvată.

2. 24 iulie 2026 la 18:55 UTCidentified

   UA a identificat problema accesării vdi.alaska.edu și lucrează la rezolvarea acesteia. Orice acces desktop prin vdi.alaska.edu, și, eventual, clientul gros, nu va putea utiliza masini virtuale de la acea adresă. Vă mulţumesc pentru răbdare în timpul soluţionării acestei probleme. Vă rugăm să așteptați o actualizare la 11:50 AM și actualizări pe oră după.

3. 24 iulie 2026 la 20:12 UTCidentified

   UA a identificat problema accesării vdi.alaska.edu și lucrează la rezolvarea acesteia. Orice acces desktop prin vdi.alaska.edu, și, eventual, clientul gros, nu va putea utiliza masini virtuale de la acea adresă. Vă mulţumesc pentru răbdare în timpul soluţionării acestei probleme. Vă rugăm să așteptați o actualizare la 12:50 AM și actualizări pe oră după.

4. 24 iulie 2026 la 20:55 UTCidentified

   UA a identificat problema accesării vdi.alaska.edu și lucrează la rezolvarea acesteia. Orice acces desktop prin vdi.alaska.edu, și, eventual, clientul gros, nu va putea utiliza masini virtuale de la acea adresă. Vă mulţumesc pentru răbdare în timpul soluţionării acestei probleme. Vă rugăm să așteptați o actualizare la 1:50 PM și actualizări pe oră după.

5. 24 iulie 2026 la 22:35 UTCidentified

   UA a identificat problema accesării vdi.alaska.edu și lucrează la rezolvarea acesteia. Orice acces desktop prin vdi.alaska.edu, și, eventual, clientul gros, nu va putea utiliza masini virtuale de la acea adresă. Vă mulţumesc pentru răbdare în timpul soluţionării acestei probleme. Vă rugăm să așteptați o actualizare la 05:00.

6. 25 iulie 2026 la 00:03 UTCmonitoring

   UA a rezolvat problema cu vdi.alaska.edu și a confirmat fixarea pentru a fi stabilă. Acest lucru va fi plasat în monitorizare până la sfârșitul afacerii la ora 5:00 PM. Vă rugăm să raportați orice probleme continue cu acest serviciu către biroul IT al campusului dvs. și vă mulțumesc din nou pentru răbdare în timpul rezoluției acestei probleme!

7. 25 iulie 2026 la 01:06 UTCresolved

   UA a rezolvat problema cu vdi.alaska.edu și a confirmat fixarea pentru a fi stabilă. Vă rugăm să raportați orice probleme continue cu acest serviciu la biroul IT al campusului dvs. și vă mulțumesc din nou pentru răbdarea dvs. în timpul rezoluției acestei probleme!

8. 19 august 2026 la 21:26 UTCpostmortem

   [vdi.alaska.edu](http://vdi.alaska.edu) întreruperea accesului. Certificate Unified Access Gateway expirate. Data: 07/23/2026 04:00 # Fundal [vdi.alaska.edu](http://vdi.alaska.edu) oferă acces utilizatorilor la mediul VMware/Omnissa Horizon VDI. Ambele aparate Unified Access Gateway \ (există pe platforma VXrail\) oferă stratul de acces extern pentru utilizatorii care doresc să-și acceseze VDI atât în campus, cât și de la distanță. # Break Down of the Problem Ambele certificate pentru fiecare UAG au expirat la 23 iulie 3:59 PM, 2026. Problema a fost observată vineri dimineaţa, 24 iulie, în jurul orei 8:30, când utilizatorii au raportat că nu au putut accesa mediile lor de pe Desktop-ul meu, VDI, atunci când se rezolvă la [vdi.alaska.edu][http://vdi.alaska.edu] Atunci când un utilizator a încercat să rezolve la [vdi.alaska.edu][http://vdi.alaska.edu] prin intermediul browser-ului lor, ei au primit o conexiune Pagina Horizon, la toate. Acțiuni întreprinse pentru restabilirea serviciului: Certificat de reînnoire solicitat de PAWS. Acest certificat conținea numele de domeniu primar, [vdi.alaska.edu](http://vdi.alaska.edu) dar includea și denumirile alternative \(ambele nume UAG\) [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) Durata întreruperii și timpul de restabilire a serviciului: Joi, 23 iulie, ora 16:00 - vineri, ora 24:00. # Target State / Goal Ambele UAG ar trebui să prezinte în permanență certificate valabile, de încredere și acces intern VDI Analiza cauza rădăcină # Ambele aparate UAG prezentau certificate TLS expirate. TSS a primit o listă de aparate de server VXrail care au estimat timpul de expirare a certificatelor lor. Ambele aparate UAG nu erau pe această listă, aşa că nu am putut dicta când vor expira certificatele lor. Dezvoltă contramăsuri Am creat o foaie de calcul a certificatului de master care conţine acum ambele informaţii din certificatul UAG pentru a include datele de expirare. Împărtășesc cu echipa noastră TSS conduce astfel încât să putem continua să monitorizeze expirarea certificatului așteptat în viitor. A solicitat accesul la serviciul Certinext pentru viitoarele reînnoiri ale certificatului. Calendarul punerii în aplicare: Cele de mai sus ar trebui să ne permită să solicite și să pună în aplicare certificările înainte de a expira pe ambele UAG # Follow up / Review Verificați data de expirare a certificatului pe ambele UAG Pune într-o cerere către PAWS de reînnoire a certificatului, de planificare a unei întreruperi scurte a CAB, de a aplica certificatul atât pentru UAG

Traducere automată din actualizarea oficială a incidentului.

1. 29 mai 2026 la 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 la 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 la 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 iulie 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 iulie 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 iunie 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 20:46 UTCresolved

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

9. 6 mai 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 00:38 UTCresolved

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

3. 8 aprilie 2026 la 18:20 UTCpostmortem

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

1. 23 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 18:12 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20 martie 2026 la 18:14 UTCresolved

   Service is restored.

1. 17 martie 2026 la 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 martie 2026 la 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!