Cronologia delle interruzioni di University Of Alaska

1. 19 agosto 2026 alle ore 23:57 UTCmonitoring

   Alcuni clienti mobili AT&T non sono attualmente in grado di completare le chiamate ai numeri di telefono del campus. Questo problema è stato identificato come originario della rete AT&T, non con i nostri sistemi telefonici o servizi. Stiamo monitorando la situazione e fornirà un aggiornamento una volta che le chiamate sono confermate di funzionare di nuovo normalmente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 agosto 2026 alle ore 20:54 UTCidentified

   Abbiamo ricevuto rapporti che i lettori di carte intorno al campus UAF stanno attualmente vivendo problemi. Il team OIT PAWS è consapevole e sta lavorando attivamente per recuperare il server che controlla questo sistema. Faremo aggiornamenti a intervalli di un'ora mentre lavorano verso una correzione. I coordinatori degli edifici possono essere a conoscenza di metodi di accesso alternativi e percorsi per particolari stanze, ma in questo momento non c'è alcun lavoro diffuso. Grazie per la vostra pazienza durante la risoluzione di questo problema!

2. 16 agosto 2026 alle ore 22:59 UTCidentified

   Stiamo continuando a lavorare per risolvere questo problema.

3. 16 agosto 2026 alle ore 23:56 UTCresolved

   OIT PAWS riferisce che il server per i sistemi di swipe della scheda Lenel è stato riavviato con successo ed è operativo.

4. 19 agosto 2026 alle ore 21:25 UTCpostmortem

   Traduzione: Traduzione: Il server Argus ha sperimentato una rapida perdita di spazio disponibile sull'unità Windows C. Durante l'indagine, PAWS ha identificato un'attività disco significativa che si verifica nella directory di registro delle applicazioni Lenel. Lo spazio disponibile del disco ha continuato a diminuire e alla fine ha raggiunto circa 37 MB. PAWS spegnere il server in modo pulito per impedire al sistema operativo di raggiungere lo spazio su disco disponibile e potenzialmente causare ulteriori problemi di sistema. PAWS ha ampliato l'unità C: e ha restituito il server al servizio. Dopo il recupero, l'utilizzo del disco stabilizzato e circa 20 GB di spazio libero sono rimasti disponibili. PAWS è responsabile dell'infrastruttura del server Windows sottostante ma non amministra o supporta l'applicazione Lenel. La causa dell'aumento dell'attività del disco generata dall'applicazione non è stata determinata e richiede un'indagine da parte del proprietario/vendor dell'applicazione. # Il server Argus non è stato disponibile durante le attività di recupero di incidenti e infrastrutture, con conseguente interruzione dei servizi dipendenti dal server. Gli impatti segnalati includono la funzionalità del lettore di schede di porta sul campus. # Timeline # Tutte le volte sono Alaska Time. **Approssimativamente 11:04 ** – PAWS è stato notificato di un problema che riguarda il server Argus e ha segnalato gli impatti ai lettori di porta on-campus. L'incidente associato è stato TDX 991008. **Approssimativamente 11:23 ** – PAWS ha identificato rapidamente diminuire lo spazio disponibile sull'unità Windows C:. Monitor delle risorse ha mostrato una significativa attività di scrittura che si verifica all'interno: `C:\ProgramData\Ln\logs` PAWS ha tentato di recuperare la capacità del disco disponibile; tuttavia, C: l'utilizzo ha continuato ad aumentare. L'unità C: alla fine ha raggiunto circa **37 MB di spazio disponibile**. PAWS spegnere la VM in modo pulito per evitare che l'unità di sistema di Windows raggiunga 0 spazio disponibile e potenzialmente causando ulteriori problemi di sistema operativo. PAWS ha eseguito il lavoro infrastrutturale necessario per aumentare la capacità dell'unità di sistema. **Approssimativamente 3:34** – Il lavoro di infrastruttura è stato completato e l'unità C: è stata ampliata. Il server è stato riportato on-line e PAWS ha verificato il normale funzionamento del server e del disco. **Approssimativamente 3:49 PM** – Il server è stato segnalato operativo. Il giorno seguente, C: rimase stabile a circa **19.9 GB libero**, senza ricorrenza del consumo rapido del disco. ♪#Root Cause ♪ La causa immediata dell'interruzione del server era esaurimento della capacità disponibile sull'unità Windows C:. Durante l'incidente, PAWS ha osservato un'attività significativa di scrittura del disco all'interno della directory di registro delle applicazioni Lenel: `C:\ProgramData\Ln\logs` Questa attività ha rapidamente consumato la capacità disponibile rimanente sull'unità di sistema. Il motivo sottostante per l'aumento dell'attività del disco generato dall'applicazione non è stato determinato****. PAWS è responsabile per l'amministrazione dell'infrastruttura server sottostante ma non amministra, configura o supporta l'applicazione Lenel. Determinare il motivo per cui l'applicazione ha generato l'aumento dell'attività del disco richiede l'indagine da parte del proprietario/vendor dell'applicazione ed è al di fuori della portata di questa infrastruttura RCA. # ### **Limited Available System Disk Capacity** Il server non ha avuto sufficiente capacità di azionamento C: assorbire l'inaspettato aumento dell'utilizzo del disco generato dall'applicazione. La capacità disponibile alla fine è diminuita di circa **37 MB**, richiedendo PAWS di spegnere il server per impedire a Windows di raggiungere 0 spazio disponibile su disco. Traduzione: PAWS ha completato le seguenti azioni di recupero delle infrastrutture: * Investigato il C in rapida diminuzione: capacità di azionamento. * Identificata la directory sorgente associata all'attività del disco aumentata. * Pulitamente spegnere il server prima che l'unità di sistema abbia raggiunto 0 spazio disponibile. * Aumentata la capacità disponibile per l'unità Windows C. * Ha restituito il server al servizio. * Verified normale server e funzionamento del disco. * Continua l'utilizzo del disco di monitoraggio dopo il recupero. Dopo il recupero, l'unità C: rimase stabile a circa **19.9 GB libero**. Revisione: #####**Disk Capacity Monitoring**** PAWS esaminerà il monitoraggio della capacità del disco e le soglie di avviso per il server Argus per fornire una notifica sufficiente quando la capacità di unità di sistema si avvicina ai livelli critici. ######**Server Capacity* PAWS continuerà a monitorare C: l'utilizzo dell'unità per verificare che la capacità aggiuntiva fornisca una sufficiente sala operatoria in condizioni normali del server. ###### **Application Investigation * Il proprietario/vendor dell'applicazione dovrà determinare la causa dell'inaspettato aumento dell'attività del disco generato da Lenel e identificare eventuali azioni correttive a livello di applicazione che possono essere richieste. La configurazione delle applicazioni, la registrazione, la ritenzione e la bonifica a livello di applicazione sono al di fuori del campo di applicazione dell'amministrazione del server PAWS. Traduzione: Il server Argus è online e operativo. L'unità C: rimase stabile a circa **19.9 GB gratuiti** durante il monitoraggio del follow-up, senza ricorrenza del consumo rapido del disco osservato durante l'incidente. PAWS considera la parte dell'infrastruttura del server dell'incidente risolto**. La causa sottostante del comportamento dell'applicazione Lenel rimane indeterminata e richiede il follow-up dal proprietario/vendor dell'applicazione.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 10 agosto 2026 alle ore 19:02 UTCinvestigating

   Abbiamo ricevuto segnalazioni che Banner sta attualmente vivendo problemi. Il team OIT EAS sta attualmente indagando, e faremo aggiornamenti a intervalli di 1 ora. È stata identificata una soluzione di funzionamento: aprire una finestra di navigazione privata o incognito per accedere a Banner. Se il sito è ancora lento / non caricamento, chiudere e aprire un'altra nuova finestra privata o incognito; può richiedere alcuni tentativi, ma una volta che una connessione affidabile è fatta, è possibile continuare a utilizzare quella sessione fino a quando il problema non è risolto! Grazie per la vostra pazienza durante la risoluzione di questo problema!

2. 10 agosto 2026 alle ore 20:03 UTCmonitoring

   Il team OIT EAS ha identificato il problema con la Banner e ha implementato una correzione, che viene monitorata per efficacia e stabilità. Grazie ancora per la vostra pazienza durante la risoluzione di questo problema! Potete aspettarvi ulteriori aggiornamenti alla fine del giorno di affari 5:00PM o come nuove informazioni diventano disponibili.

3. 17 agosto 2026 alle ore 16:53 UTCresolved

   Il team OIT EAS ha risolto il problema con il Banner, e ha confermato la fissazione per essere stabile. Il problema è stato risolto il 10 agosto. Si prega di segnalare eventuali problemi continui con questo servizio al helpdesk IT del vostro campus, e grazie ancora per la vostra pazienza durante la risoluzione di questo problema!

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 3 agosto 2026 alle ore 16:55 UTCinvestigating

   Abbiamo ricevuto rapporti che l'opzione di login web Iru sta attualmente vivendo problemi. Il team NTS Technology Support Services sta attualmente indagando, e faremo aggiornamenti a intervalli di 3 ore. Passare al login locale dovrebbe consentire di accedere al Mac. Grazie per la vostra pazienza durante la risoluzione di questo problema!

2. 3 agosto 2026 alle ore 17:25 UTCinvestigating

   Il team NTS Technology Support Services (TSS) sta attualmente indagando sulla causa di questo problema. Se non è possibile accedere al Mac UA, provano a passare al login locale. Per passare al login locale: 1. Fare clic sull'icona del profilo (la persona all'interno di un cerchio) nell'angolo in alto a destra dello schermo. 2. Selezionare Passare al Login locale. 3. Inserisci le credenziali di accesso dell'Università nei campi username e password che appaiono vicino al centro inferiore dello schermo. 4. Clic Sign Per accedere. Se non sei ancora in grado di accedere, contatta il tuo assistente IT locale per ulteriori assistenza. Grazie per la vostra continua pazienza mentre lavoriamo verso una risoluzione completa; faremo ulteriori aggiornamenti a intervalli di 3 ore e come nuove informazioni diventano disponibili.

3. 3 agosto 2026 alle ore 18:02 UTCinvestigating

   NTS TSS team sta attualmente indagando la causa di questo problema. Il prompt Iru per sincronizzare le tue password è sicuro di ignorare come meglio si è in grado mentre si indaga sul perché viene richiesto. Se non è possibile accedere al Mac UA, provano a passare al login locale. Per passare al login locale: 1. Fare clic sull'icona del profilo (la persona all'interno di un cerchio) nell'angolo in alto a destra dello schermo. 2. Selezionare Passare al Login locale. 3. Inserisci le credenziali di accesso dell'Università nei campi username e password che appaiono vicino al centro inferiore dello schermo. 4. Clic Sign Per accedere. Se non sei ancora in grado di accedere, contatta il tuo assistente IT locale per ulteriori assistenza. Grazie per la vostra continua pazienza mentre lavoriamo verso una risoluzione completa; faremo ulteriori aggiornamenti a intervalli di 1 ora e come nuove informazioni diventano disponibili.

4. 3 agosto 2026 alle ore 19:44 UTCinvestigating

   NTS TSS team continua a indagare sulla causa di questo problema. Non ci sono ulteriori aggiornamenti in questo momento. Il prompt Iru per sincronizzare le tue password è sicuro di ignorare come meglio si è in grado mentre si indaga sul perché viene richiesto. Se non è possibile accedere al Mac UA, provano a passare al login locale. Per passare al login locale: 1. Fare clic sull'icona del profilo (la persona all'interno di un cerchio) nell'angolo in alto a destra dello schermo. 2. Selezionare Passare al Login locale. 3. Inserisci le credenziali di accesso dell'Università nei campi username e password che appaiono vicino al centro inferiore dello schermo. 4. Clic Sign Per accedere. Se non sei ancora in grado di accedere, contatta il tuo assistente IT locale per ulteriori assistenza. Grazie per la vostra continua pazienza mentre lavoriamo verso una risoluzione completa; faremo ulteriori aggiornamenti a intervalli di 1 ora e come nuove informazioni diventano disponibili.

5. 3 agosto 2026 alle ore 22:35 UTCmonitoring

   Abbiamo risolto un problema recente causato da un cambiamento inaspettato con l'autenticazione Duo che ha influenzato i login di computer macOS gestiti in tutto il campus. Se si utilizza un Mac gestito dall'università, la vostra esperienza di login è ora ripristinata alle normali operazioni. Tuttavia, la prima volta che si accede al computer in seguito a questa correzione, è possibile visualizzare uno o due ulteriori prompt di autenticazione Duo. Quando accedi al tuo Mac gestito per la prima volta oggi: 1. Inserisci le credenziali del tuo account abituali nella schermata di accesso macOS primario. 2. Completa il prompt di Duo(s): Si può essere chiesto di autenticare attraverso Duo un tempo supplementare come permessi di sistema rinfrescare e ri-sincrona con il tuo account. 3. Approva la richiesta sulla tua app mobile Duo, token hardware, o tramite il tuo metodo MFA preferito come normale. 4. Selezionare Next al Let’s mantenere il vostro account sicuro prompt. 5. Selezionare Avanti al Impostare un prompt dei metodi di registrazione. Se si continua a incontrare errori di login, ripetuti suggerimenti per sincronizzare le password sul login, o qualsiasi altro problema di registrazione nel vostro Mac, si prega di raggiungere il vostro campus IT Helpdesk.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 17:46 UTCidentified

   L'accesso a vdi.alaska.edu non è disponibile, ma la causa dell'estrazione è stata identificata. Qualsiasi accesso desktop attraverso vdi.alaska.edu, e possibilmente il cliente spesso, non sarà in grado di accedere o utilizzare macchine virtuali da quell'indirizzo fino a quando il problema non è stato risolto.

2. 24 luglio 2026 alle ore 18:55 UTCidentified

   UA ha identificato il problema con l'accesso vdi.alaska.edu e sta lavorando per risolverlo. Qualsiasi accesso desktop attraverso vdi.alaska.edu, e possibilmente il cliente spesso, non sarà in grado di utilizzare macchine virtuali da quell'indirizzo. Grazie per la vostra pazienza durante la risoluzione di questo problema. Si prega di aspettarsi un aggiornamento alle 11:50 AM e aggiornamenti orali dopo.

3. 24 luglio 2026 alle ore 20:12 UTCidentified

   UA ha identificato il problema con l'accesso vdi.alaska.edu e sta lavorando per risolverlo. Qualsiasi accesso desktop attraverso vdi.alaska.edu, e possibilmente il cliente spesso, non sarà in grado di utilizzare macchine virtuali da quell'indirizzo. Grazie per la vostra pazienza durante la risoluzione di questo problema. Si prega di aspettarsi un aggiornamento alle 12:50 AM e aggiornamenti orali dopo.

4. 24 luglio 2026 alle ore 20:55 UTCidentified

   UA ha identificato il problema con l'accesso vdi.alaska.edu e sta lavorando per risolverlo. Qualsiasi accesso desktop attraverso vdi.alaska.edu, e possibilmente il cliente spesso, non sarà in grado di utilizzare macchine virtuali da quell'indirizzo. Grazie per la vostra pazienza durante la risoluzione di questo problema. Si prega di aspettarsi un aggiornamento a 1:50 PM e aggiornamenti orali dopo.

5. 24 luglio 2026 alle ore 22:35 UTCidentified

   UA ha identificato il problema con l'accesso vdi.alaska.edu e sta lavorando per risolverlo. Qualsiasi accesso desktop attraverso vdi.alaska.edu, e possibilmente il cliente spesso, non sarà in grado di utilizzare macchine virtuali da quell'indirizzo. Grazie per la vostra pazienza durante la risoluzione di questo problema. Si prega di aspettarsi un aggiornamento alle 17:00 PM.

6. 25 luglio 2026 alle ore 00:03 UTCmonitoring

   UA ha risolto il problema con il vdi.alaska.edu e ha confermato la correzione di essere stabile. Questo sarà messo in monitoraggio fino alla fine del business alle 17:00 PM. Si prega di segnalare eventuali problemi continui con questo servizio al helpdesk IT del vostro campus, e grazie ancora per la vostra pazienza durante la risoluzione di questo problema!

7. 25 luglio 2026 alle ore 01:06 UTCresolved

   UA ha risolto il problema con il vdi.alaska.edu e ha confermato la correzione di essere stabile. Si prega di segnalare eventuali problemi continui con questo servizio al helpdesk IT del vostro campus e grazie ancora per la vostra pazienza durante la risoluzione di questo problema!

8. 19 agosto 2026 alle ore 21:26 UTCpostmortem

   [vdi.alaska.edu](http://vdi.alaska.edu) Certificati di accesso unificato scaduti. Data: 07/23/2026 4:00 PM. # Sfondo [vdi.alaska.edu](http://vdi.alaska.edu) fornisce l'accesso utente all'ambiente VMware/Omnissa Horizon VDI. Entrambi gli elettrodomestici Unified Access Gateway \(esistente sulla piattaforma VXrail\) forniscono lo strato di accesso esterno per gli utenti che vogliono accedere al loro VDI sia nel campus che in remoto. # Break Down of the Problem Entrambi i certificati su ogni UAG sono scaduti il 23 luglio, 3:59 PM, 2026. Il problema è stato notato venerdì mattina 24 luglio intorno alle 8:30, quando gli utenti hanno riferito di non poter accedere ai loro ambienti VDI “My Desktop” quando si risolve [vdi.alaska.edu](http://vdi.alaska.edu) Quando un utente ha cercato di risolvere a [vdi.alaska.edu](http://vdi.alaska.edu) tramite il proprio browser, ha ricevuto un avviso “La tua connessione non è privata” e quindi sarebbe bloccato dal raggiungere [vdi.alaska.edu](http://vdi.alaska.edu) Pagina orizzontale. Azioni adottate per il ripristino del servizio: Certificato di rinnovo richiesto da PAWS. Questo cert conteneva il nome di dominio principale, [vdi.alaska.edu](http://vdi.alaska.edu) ma includeva anche i nomi alternativi \(entrambi i nomi 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 dell'estrazione e del tempo che il servizio è stato ripristinato: Giovedì 23 luglio 16:00 - Venerdì 24:00. # Target State / Goal Sia UAG dovrebbe presentare continuamente validi, certificati di fiducia e accesso VDI esterno e interno # Analisi delle cause della radice # Entrambi gli apparecchi UAG presentavano certificati TLS scaduti. TSS ha ricevuto un elenco di elettrodomestici server VXrail che aveva stimato i tempi di quando i loro certificati stavano espando. Entrambi gli apparecchi UAG non erano in questa lista quindi non siamo stati in grado di dettare quando i loro certificati sarebbero scaduti. # Sviluppare contromisure Ho creato un foglio di calcolo del certificato master che ora contiene entrambe le informazioni del certificato UAG per includere le date di scadenza. Lo sto condividendo con il nostro team TSS conduce in modo da poter continuare a monitorare le espulsioni dei certificati attesi in futuro. Richiesta di accesso al servizio Certinext per i futuri rinnovi certificati. Programma per l'attuazione: Quanto sopra dovrebbe consentire di richiedere e implementare i certs prima che scadono su entrambi gli UAG prima della loro scadenza. # Follow Up / Review Verificare le date di scadenza del certificato su entrambi gli UAG monitorando il foglio di calcolo del certificato master. Inviare una richiesta a PAWS per rinnovare il certificato, pianificare un breve outage CAB, applicare il certificato a entrambi gli UAG e quindi confermare il rinnovo è stato successo e l'accesso si verifica

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 29 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 luglio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 luglio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 20:46 UTCresolved

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

9. 6 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 00:38 UTCresolved

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

3. 8 aprile 2026 alle ore 18:20 UTCpostmortem

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

1. 23 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 18:12 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 20 marzo 2026 alle ore 18:14 UTCresolved

   Service is restored.

1. 17 marzo 2026 alle ore 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 marzo 2026 alle ore 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!