Historique des pannes de University Of Alaska

1. 19 août 2026 à 23:57 UTCmonitoring

   Certains clients d'AT&T mobiles sont actuellement incapables d'effectuer des appels vers des numéros de téléphone de campus. Ce problème a été identifié comme provenant du réseau d'AT&T, et non de nos systèmes ou services téléphoniques. Nous surveillons la situation et fournirons une mise à jour une fois que les appels seront confirmés pour fonctionner normalement à nouveau.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 août 2026 à 20:54 UTCidentified

   Nous avons reçu des rapports selon lesquels les lecteurs de cartes du campus de l'UAF connaissent actuellement des problèmes. L'équipe OIT PAWS est consciente et travaille activement à récupérer le serveur qui contrôle ce système. Nous ferons des mises à jour à intervalles d'une heure lorsqu'elles travailleront vers un correctif. Les coordonnateurs du bâtiment sont peut-être au courant des autres méthodes et itinéraires d'accès pour certaines pièces, mais il n'y a pas de solution de rechange à l'heure actuelle. Merci de votre patience lors de la résolution de ce problème!

2. 16 août 2026 à 22:59 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

3. 16 août 2026 à 23:56 UTCresolved

   OIT PAWS signale que le serveur des systèmes de balayage de cartes Lenel a été redémarré avec succès et est opérationnel.

4. 19 août 2026 à 21:25 UTCpostmortem

   # **Analyse des causes de la root – Incident du serveur Argus** **Résumé** Le serveur Argus a connu une perte rapide d'espace disponible sur le disque Windows C:. Au cours de l'enquête, PAWS a identifié une activité importante sur disque dans le répertoire du journal des applications de Lenel. L'espace disque disponible a continué de diminuer et a finalement atteint environ 37 Mo. PAWS ferme complètement le serveur pour empêcher le système d'exploitation d'atteindre 0 espace disque disponible et potentiellement causer des problèmes de système supplémentaires. PAWS a élargi le lecteur C: et a renvoyé avec succès le serveur au service. Après la récupération, l'utilisation du disque s'est stabilisée et environ 20 Go d'espace libre sont restés disponibles. PAWS est responsable de l'infrastructure sous-jacente du serveur Windows, mais ne gère ni ne supporte l'application Lenel. La cause de l'augmentation de l'activité de disque générée par l'application n'a pas été déterminée et nécessite une enquête de la part du propriétaire ou du vendeur de l'application. (en milliers de dollars) (en milliers de dollars) ## **Incident Impact** Le serveur Argus est devenu indisponible pendant l'incident et les activités de récupération de l'infrastructure, ce qui a entraîné une interruption des services dépendant du serveur. Les impacts signalés comprenaient la fonctionnalité de lecteur de cartes de porte sur le campus. (en milliers de dollars) (en milliers de dollars) **Échéancier** **Toutes les heures sont Alaska Time.** **Environ 11h04** – PAWS a été informé d'un problème impliquant le serveur Argus et a signalé des impacts sur les lecteurs de cartes de porte sur le campus. L'incident connexe était TDX 991008. **Environ 11h23** – PAWS a identifié une diminution rapide de l'espace disponible sur le disque Windows C. Resource Monitor a montré une activité d'écriture importante dans: `C:\ProgramData\Ln\logs` PAWS a tenté de récupérer la capacité du disque disponible; cependant, C: l'utilisation a continué à augmenter. Le disque C: a finalement atteint environ **37 Mo d'espace disponible**. PAWS ferme complètement le VM pour empêcher le lecteur du système Windows d'atteindre 0 espace disponible et potentiellement causer des problèmes supplémentaires du système d'exploitation. PAWS a effectué les travaux d'infrastructure nécessaires pour augmenter la capacité de l'entraînement du système. **Environ 15h34** – Les travaux d'infrastructure ont été terminés et le lecteur C: a été élargi. Le serveur a été ramené en ligne et PAWS a vérifié le fonctionnement normal du serveur et du disque. ** Environ 15 h 49** – Le serveur a été déclaré opérationnel. Le jour suivant, C: est resté stable à environ **19,9 Go libre**, sans récurrence de la consommation rapide de disque. (en milliers de dollars) (en milliers de dollars) ## **La cause de la mort** La cause immédiate de la panne du serveur était l'épuisement de la capacité disponible sur le disque Windows C:. Pendant l'incident, PAWS a observé une activité importante d'écriture de disque dans le répertoire du journal des applications Lenel : `C:\ProgramData\Ln\logs` Cette activité a rapidement consommé la capacité disponible restante sur le lecteur système. La raison sous-jacente de l'augmentation de l'activité du disque générée par l'application n'a pas été déterminée**. PAWS est responsable de l'administration de l'infrastructure sous-jacente du serveur, mais ne gère pas, ne configure pas ou ne supporte pas l'application Lenel. Déterminer pourquoi l'application a généré l'activité accrue du disque nécessite une enquête par le propriétaire/vendeur de l'application et est hors de la portée de cette infrastructure RCA. (en milliers de dollars) (en milliers de dollars) ** Facteur de conversion** Nombre de disques disponibles Le serveur ne disposait pas d'une capacité d'entraînement suffisante pour absorber l'augmentation inattendue de l'utilisation du disque générée par l'application. La capacité disponible a finalement diminué à environ **37 MB**, exigeant que PAWS ferme le serveur pour empêcher Windows d'atteindre 0 espace disque disponible. (en milliers de dollars) (en milliers de dollars) Résolution Le PAWS a mené à bien les mesures de rétablissement de l'infrastructure suivantes : * Étude de la capacité d'entraînement du C en baisse rapide. * Identifié le répertoire source associé à l'activité accrue du disque. * Éteignez complètement le serveur avant que le lecteur du système atteigne 0 espace disponible. * Augmentation de la capacité disponible pour le lecteur Windows C:. * Renvoyé le serveur au service. * Vérifié fonctionnement normal du serveur et du disque. * Surveillance continue de l'utilisation du disque après la récupération. Après récupération, l'entraînement C: est resté stable à environ **19,9 Go libre**. (en milliers de dollars) (en milliers de dollars) ** Mesures correctives et préventives** **Surveillance de la capacité de disque** Le PAWS examinera les seuils de surveillance de la capacité du disque et d'alerte pour le serveur Argus afin de fournir une notification suffisante lorsque la capacité du système approche des niveaux critiques. Capacité du serveur** PAWS continuera de surveiller C: l'utilisation du lecteur pour vérifier que la capacité supplémentaire fournit une salle de tête d'opération suffisante dans des conditions normales de serveur. ### ** Enquête sur la demande** Le propriétaire/vendor de l'application devra déterminer la cause de l'augmentation inattendue de l'activité du disque généré par Lenel et identifier toute mesure corrective nécessaire au niveau de l'application. La configuration de l'application, l'enregistrement, la conservation et l'assainissement du niveau de l'application ne relèvent pas de l'administration du serveur PAWS. (en milliers de dollars) (en milliers de dollars) Statut actuel** Le serveur Argus est en ligne et opérationnel. L'entraînement C: est resté stable à environ **19,9 Go libre** pendant la surveillance de suivi, sans que la consommation rapide de disque observée au cours de l'incident ne se reproduise. PAWS considère que la partie de l'incident relative à l'infrastructure des serveurs ** a été résolue**. La cause sous-jacente du comportement de l'application Lenel reste indéterminée et nécessite un suivi par le propriétaire/vendor de l'application.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 10 août 2026 à 19:02 UTCinvestigating

   Nous avons reçu des rapports selon lesquels Banner connaît actuellement des problèmes. L'équipe du SAE de l'OIT enquête actuellement, et nous ferons des mises à jour à intervalles d'une heure. Une solution de rechange a été identifiée : ouvrez une fenêtre de navigateur privée ou incognito pour accéder à Banner. Si le site est encore lent/pas chargé, fermez et ouvrez une nouvelle fenêtre privée ou incognito ; il peut prendre quelques tentatives, mais une fois une connexion fiable est faite, vous pouvez continuer à utiliser cette session jusqu'à ce que le problème soit résolu ! Merci de votre patience lors de la résolution de ce problème!

2. 10 août 2026 à 20:03 UTCmonitoring

   L'équipe du SAE de l'OIT a identifié le problème avec la bannière et a mis en place un correctif, qui est surveillé pour assurer son efficacité et sa stabilité. Merci encore pour votre patience pendant la résolution de cette question! Vous pouvez vous attendre à d'autres mises à jour à la fin du jour ouvrable 17:00PM ou à mesure que de nouvelles informations deviennent disponibles.

3. 17 août 2026 à 16:53 UTCresolved

   L'équipe de l'OIT EAS a résolu le problème avec la bannière et a confirmé que la correction était stable. Le problème a été résolu le 10 août. Veuillez signaler tout problème continu avec ce service au service d'assistance informatique de votre campus, et merci encore pour votre patience pendant la résolution de ce problème!

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 3 août 2026 à 16:55 UTCinvestigating

   Nous avons reçu des rapports que l'option de connexion web Iru connaît actuellement des problèmes. L'équipe NTS Technology Support Services enquête actuellement, et nous ferons des mises à jour à intervalles de 3 heures. Le passage à une connexion locale devrait vous permettre de vous connecter à votre Mac. Merci de votre patience lors de la résolution de ce problème!

2. 3 août 2026 à 17:25 UTCinvestigating

   L'équipe des Services de soutien technologique du NTS (TSS) étudie actuellement la cause de ce problème. Si vous ne pouvez pas vous connecter à votre Mac UA, ils essaient de passer à la connexion locale. Pour passer à la connexion locale : 1. Cliquez sur l'icône de profil (la personne dans un cercle) dans le coin supérieur droit de l'écran. 2. Sélectionnez Switch to Local Login. 3. Entrez vos identifiants universitaires dans les champs nom d'utilisateur et mot de passe qui apparaissent près du centre inférieur de l'écran. 4. Cliquez sur Signe Pour ouvrir une session. Si vous n'êtes toujours pas en mesure de vous connecter, veuillez contacter votre bureau d'assistance informatique local pour obtenir de l'aide. Merci pour votre patience continue alors que nous travaillons vers une résolution complète; nous ferons d'autres mises à jour à intervalles de 3 heures et à mesure que de nouvelles informations seront disponibles.

3. 3 août 2026 à 18:02 UTCinvestigating

   L'équipe du SST du SNT enquête actuellement sur la cause de ces problèmes. L'invite Iru à synchroniser vos mots de passe est sûre d'ignorer au mieux que vous êtes en mesure pendant que nous étudions pourquoi elle est sollicitée. Si vous ne pouvez pas vous connecter à votre Mac UA, ils essaient de passer à la connexion locale. Pour passer à la connexion locale : 1. Cliquez sur l'icône de profil (la personne dans un cercle) dans le coin supérieur droit de l'écran. 2. Sélectionnez Switch to Local Login. 3. Entrez vos identifiants universitaires dans les champs nom d'utilisateur et mot de passe qui apparaissent près du centre inférieur de l'écran. 4. Cliquez sur Signe Pour ouvrir une session. Si vous n'êtes toujours pas en mesure de vous connecter, veuillez contacter votre bureau d'assistance informatique local pour obtenir de l'aide. Merci pour votre patience continue alors que nous travaillons à une résolution complète; nous ferons d'autres mises à jour à intervalles d'une heure et à mesure que de nouvelles informations seront disponibles.

4. 3 août 2026 à 19:44 UTCinvestigating

   L'équipe du NTS continue d'enquêter sur la cause de ces problèmes. Il n'y a pas d'autres mises à jour pour le moment. L'invite Iru à synchroniser vos mots de passe est sûre d'ignorer au mieux que vous êtes en mesure pendant que nous étudions pourquoi elle est sollicitée. Si vous ne pouvez pas vous connecter à votre Mac UA, ils essaient de passer à la connexion locale. Pour passer à la connexion locale : 1. Cliquez sur l'icône de profil (la personne dans un cercle) dans le coin supérieur droit de l'écran. 2. Sélectionnez Switch to Local Login. 3. Entrez vos identifiants universitaires dans les champs nom d'utilisateur et mot de passe qui apparaissent près du centre inférieur de l'écran. 4. Cliquez sur Signe Pour ouvrir une session. Si vous n'êtes toujours pas en mesure de vous connecter, veuillez contacter votre bureau d'assistance informatique local pour obtenir de l'aide. Merci pour votre patience continue alors que nous travaillons à une résolution complète; nous ferons d'autres mises à jour à intervalles d'une heure et à mesure que de nouvelles informations seront disponibles.

5. 3 août 2026 à 22:35 UTCmonitoring

   Nous avons résolu un problème récent causé par un changement inattendu avec l'authentification Duo qui a affecté les connexions d'ordinateur macOS gérés à travers le campus. Si vous utilisez un Mac géré par une université, votre expérience de connexion est maintenant rétablie dans des opérations normales. Cependant, la première fois que vous vous connectez à votre ordinateur après cette correction, vous pouvez voir une ou deux autres invites d'authentification Duo. Lors de la première connexion à votre Mac géré aujourd'hui: 1. Entrez vos identifiants de compte habituels à l'écran de connexion macOS primaire. 2. Remplissez la ou les instructions Duo : Vous pouvez être invité à authentifier à travers Duo un temps supplémentaire comme permissions système rafraîchir et de re-synchroniser avec votre compte. 3. Approuvez la demande sur votre application mobile Duo, jeton matériel ou via votre méthode MFA préférée comme normale. 4. Sélectionnez Suivant dans les Let. 5. Sélectionnez Suivant à l'invite Définir une méthode d'inscription. Si vous continuez à rencontrer des erreurs de connexion, des invitations répétées à synchroniser les mots de passe sur login, ou tout autre problème de connexion à votre Mac, veuillez contacter votre Helpdesk informatique de campus.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 17:46 UTCidentified

   L'accès à vdi.alaska.edu n'est pas disponible, mais la cause de la panne a été identifiée. Tout accès de bureau via vdi.alaska.edu, et peut-être le client épais, ne sera pas en mesure d'accéder ou d'utiliser les machines virtuelles de cette adresse jusqu'à ce que le problème ait été résolu.

2. 24 juillet 2026 à 18:55 UTCidentified

   UA a identifié le problème d'accès à vdi.alaska.edu et travaille à le résoudre. Tout accès de bureau via vdi.alaska.edu, et peut-être le client épais, ne sera pas en mesure d'utiliser les machines virtuelles de cette adresse. Merci de votre patience pendant la résolution de cette question. S'il vous plaît attendre une mise à jour à 11:50 AM et des mises à jour horaires après.

3. 24 juillet 2026 à 20:12 UTCidentified

   UA a identifié le problème d'accès à vdi.alaska.edu et travaille à le résoudre. Tout accès de bureau via vdi.alaska.edu, et peut-être le client épais, ne sera pas en mesure d'utiliser les machines virtuelles de cette adresse. Merci de votre patience pendant la résolution de cette question. S'il vous plaît attendre une mise à jour à 12:50 AM et des mises à jour horaires après.

4. 24 juillet 2026 à 20:55 UTCidentified

   UA a identifié le problème d'accès à vdi.alaska.edu et travaille à le résoudre. Tout accès de bureau via vdi.alaska.edu, et peut-être le client épais, ne sera pas en mesure d'utiliser les machines virtuelles de cette adresse. Merci de votre patience pendant la résolution de cette question. S'il vous plaît attendre une mise à jour à 1:50 PM et des mises à jour horaires après.

5. 24 juillet 2026 à 22:35 UTCidentified

   UA a identifié le problème d'accès à vdi.alaska.edu et travaille à le résoudre. Tout accès de bureau via vdi.alaska.edu, et peut-être le client épais, ne sera pas en mesure d'utiliser les machines virtuelles de cette adresse. Merci de votre patience pendant la résolution de cette question. Veuillez vous attendre à une mise à jour à 17h00.

6. 25 juillet 2026 à 00:03 UTCmonitoring

   UA a résolu le problème avec le vdi.alaska.edu et a confirmé que la correction était stable. Cela sera mis en surveillance jusqu'à la fin des travaux à 17 h. Veuillez signaler tout problème continu avec ce service au service d'assistance informatique de votre campus, et merci encore pour votre patience pendant la résolution de ce problème!

7. 25 juillet 2026 à 01:06 UTCresolved

   UA a résolu le problème avec le vdi.alaska.edu et a confirmé que la correction était stable. Veuillez signaler tout problème continu avec ce service au service d'assistance informatique de votre campus et merci encore pour votre patience pendant la résolution de ce problème!

8. 19 août 2026 à 21:26 UTCpostmortem

   [vdi.alaska.edu](http://vdi.alaska.edu) interruption de l'accès. (en milliers de dollars) Certificats de passerelle d'accès unifié expirés. Heure: 07/23/2026 16:00. # Historique [vdi.alaska.edu](http://vdi.alaska.edu) donne accès à l'environnement VMware/Omnissa Horizon VDI. (en milliers de dollars) Les deux appareils Unified Access Gateway \(existant sur la plate-forme VXrail\) fournissent la couche d'accès externe pour les utilisateurs qui veulent accéder à leur VDI sur le campus ou à distance. (en milliers de dollars) # Briser le problème Les deux certificats de chaque UAG ont expiré le 23 juillet, 15 h 59, 2026. (en milliers de dollars) Le problème a été remarqué vendredi matin le 24 juillet vers 8h30, quand les utilisateurs ont déclaré qu'ils ne pouvaient pas accéder à leurs environnements VDI de mon bureau lors de la résolution à [vdi.alaska.edu](http://vdi.alaska.edu) (en milliers de dollars) (en milliers de dollars) Lorsqu'un utilisateur a essayé de résoudre à [vdi.alaska.edu](http://vdi.alaska.edu) par l'intermédiaire de son navigateur, il a reçu un avis de connexion non privé et serait alors bloqué d'atteindre le [vdi.alaska.edu](http://vdi.alaska.edu) Page Horizon du tout. (en milliers de dollars) Mesures prises pour rétablir le service : Certificat de renouvellement demandé à PAWS. Ce certificat contenait le nom de domaine principal, [vdi.alaska.edu](http://vdi.alaska.edu), mais comprenait également les noms de substitution \(deux noms 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) (en milliers de dollars) (en milliers de dollars) Durée de la panne et temps de rétablissement du service: Jeudi 23 juillet 16h - Vendredi 24 14h. (en milliers de dollars) (en milliers de dollars) (en milliers de dollars) # Objectif / État cible (en milliers de dollars) Tous les deux devraient présenter en permanence des certificats de confiance valides et un accès VDI externe et interne (en milliers de dollars) # Analyse des causes profondes # Les deux appareils UAG présentaient des certificats TLS expirés. TSS a reçu une liste des appareils de serveurs VXrail qui avaient estimé les heures de l'expiration de leurs certificats. Les deux appareils UAG n'étaient pas sur cette liste, donc nous n'avons pas pu dicter quand leurs certificats allaient expirer. # Développer des contre-mesures J'ai créé un tableur de certificat principal qui contient maintenant les deux informations de certificat UAG. Je le partage avec notre équipe TSS pour que nous puissions continuer à surveiller les expirations de certificats prévues à l'avenir. Accès demandé au service Certinext pour les futurs renouvellements de certificats. (en milliers de dollars) Calendrier de mise en œuvre: Ce qui précède devrait nous permettre de demander et de mettre en œuvre les certificats avant qu'ils expirent sur les deux UAG. # Suivi / examen Vérifier les dates d'expiration du certificat sur les deux UAG en surveillant la feuille de calcul du certificat principal. Demander à PAWS de renouveler le certificat, planifier une brève panne de l'ACR, appliquer le certificat aux deux UAG, puis confirmer que le renouvellement a été réussi et que l'accès se fait

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 29 mai 2026 à 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 à 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 à 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 juillet 2026 à 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 à 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 à 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 à 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 à 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 à 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 à 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 juillet 2026 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 juin 2026 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 20:46 UTCresolved

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

9. 6 mai 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 mars 2026 à 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 mars 2026 à 00:38 UTCresolved

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

3. 8 avril 2026 à 18:20 UTCpostmortem

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

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

   We are continuing to monitor for any further issues.

4. 20 mars 2026 à 18:14 UTCresolved

   Service is restored.

1. 17 mars 2026 à 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 mars 2026 à 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!