Historial de interrupciones de University Of Alaska

1. August 19, 2026 at 11:57 PM UTCmonitoring

   Algunos clientes móviles de AT comprimidoT actualmente no pueden completar llamadas a números de teléfono del campus. Este número se ha identificado como originario de la red de AT plagaT, no con nuestros sistemas telefónicos o servicios. Estamos monitoreando la situación y proporcionaremos una actualización una vez que se confirme que las llamadas funcionan normalmente de nuevo.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 16, 2026 at 8:54 PM UTCidentified

   Hemos recibido informes de que lectores de tarjetas alrededor del campus de la UAF están experimentando problemas. El equipo de la OIT PAWS es consciente y está trabajando activamente para recuperar el servidor que controla este sistema. Haremos actualizaciones a intervalos de una hora mientras trabajan hacia una solución. Los coordinadores de la construcción pueden estar conscientes de los métodos y rutas de acceso alternativo para determinadas habitaciones, pero no hay una solución general en este momento. ¡Gracias por su paciencia durante la resolución de este tema!

2. August 16, 2026 at 10:59 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

3. August 16, 2026 at 11:56 PM UTCresolved

   La OIT PAWS informa que el servidor para sistemas de cableado de tarjetas Lenel ha sido reiniciado con éxito y está operativo.

4. August 19, 2026 at 9:25 PM UTCpostmortem

   # **Análisis de la causa real - Incidente del servidor de Argus** ## ** Resumen ejecutivo** El servidor Argus experimentó una rápida pérdida de espacio disponible en la unidad Windows C:. Durante la investigación, PAWS identificó una actividad significativa en el directorio de registro de aplicaciones Lenel. El espacio de disco disponible siguió disminuyendo y finalmente alcanzó aproximadamente 37 MB. PAWS cerró limpiamente el servidor para evitar que el sistema operativo alcance 0 espacio de disco disponible y potencialmente causando problemas adicionales del sistema. PAWS expandió la unidad C: y devolvió el servidor al servicio. Tras la recuperación, se estabilizó la utilización de discos y se mantuvieron disponibles aproximadamente 20 GB de espacio libre. PAWS es responsable de la infraestructura de servidor de Windows subyacente pero no administra ni apoya la aplicación Lenel. La causa del aumento de la actividad de disco generada por la aplicación no se ha determinado y requiere investigación por el propietario/vendor de la aplicación. ## **Incident Impact** El servidor Argus no estaba disponible durante el incidente y las actividades de recuperación de infraestructura, lo que dio lugar a una interrupción de los servicios dependientes del servidor. Los impactos reportados incluyen funcionalidad de lector de tarjetas de puerta en el campus. ## **Timeline** Todas las veces son Alaska Time. **Aproximadamente 11:04 AM** – PAWS fue notificado de un problema que involucra al servidor Argus y reportó impactos a lectores de tarjetas de puerta en el campus. El incidente asociado fue TDX 991008. **Aproximadamente 11:23 AM** – PAWS identificó rápidamente la disminución del espacio disponible en la unidad Windows C:. Resource Monitor mostró una importante actividad de escritura que se realizaba dentro de: `C:\ProgramaData\Ln\logs` PAWS intentó recuperar la capacidad de disco disponible; sin embargo, C: la utilización continuó aumentando. The C: drive eventually reached approximately **37 MB of available space**. PAWS cerró limpiamente el VM para evitar que la unidad del sistema de Windows alcance 0 espacio disponible y potencialmente causando problemas adicionales del sistema operativo. PAWS realizó el trabajo de infraestructura necesario para aumentar la capacidad de la unidad del sistema. **Aproximadamente 3:34 PM** – Se completó el trabajo de infraestructura y se amplió la unidad C. El servidor fue devuelto en línea y PAWS verificó el servidor normal y el funcionamiento del disco. **Aproximadamente las 3:49 PM** – El servidor fue informado operativo. Al día siguiente, C: se mantuvo estable en aproximadamente **19.9 GB gratis**, sin recidiva del rápido consumo de disco. ## ## Root Cause ## La causa inmediata de la salida del servidor fue el agotamiento de la capacidad disponible en la unidad Windows C:. Durante el incidente, PAWS observó una importante actividad de escritura de disco dentro del directorio de registro de aplicaciones Lenel: `C:\ProgramaData\Ln\logs` Esta actividad consumió rápidamente la capacidad disponible restante en la unidad del sistema. La razón subyacente para aumentar la actividad de disco generada por la aplicación **no se ha determinado**. PAWS es responsable de la administración de la infraestructura de servidor subyacente pero no administra, configura o apoya la aplicación Lenel. Determinando por qué la aplicación generada el aumento de la actividad de disco requiere investigación por el propietario de la aplicación y está fuera del alcance de esta infraestructura RCA. ## ** Factor de contribución** #### **Limited Available System Disk Capacity** El servidor no tenía suficiente C restante: capacidad de unidad para absorber el aumento inesperado de la utilización del disco generado por la aplicación. La capacidad disponible eventualmente disminuyó a aproximadamente **37 MB**, lo que requiere que PAWS cierre el servidor para evitar que Windows alcance 0 espacio de disco disponible. ## **Resolución** PAWS completó las siguientes acciones de recuperación de infraestructura: * Investigado el rápido descenso C: capacidad de conducción. * Identifica el directorio fuente asociado con el aumento de la actividad de disco. * Cerrar el servidor de forma limpia antes de que la unidad del sistema alcanzara 0 espacio disponible. * Aumento de la capacidad disponible para Windows C: unidad. * Devolvió el servidor al servicio. * Servidor normal y operación de disco verificada. * Continuación de la utilización del disco de monitoreo después de la recuperación. Después de la recuperación, la unidad C: se mantuvo estable en aproximadamente **19.9 GB gratis**. ## ** Acciones Correctivas e Preventivas** #### ** Monitoreo de Capacidades de Disco** PAWS revisará los umbrales de monitoreo de la capacidad de disco y alerta para el servidor Argus para proporcionar suficiente notificación cuando la capacidad de unidad del sistema se acerque a niveles críticos. #### **Server Capacity** PAWS continuará monitoreando C: uso de la unidad para verificar que la capacidad adicional proporciona suficiente espacio de funcionamiento en condiciones normales del servidor. #### **Application Investigation** El propietario/vendor de la aplicación tendrá que determinar la causa del aumento inesperado de la actividad de disco generada por Lenel e identificar cualquier acción correctiva de nivel de aplicación que pueda ser necesaria. La configuración, registro, retención y remediación a nivel de aplicación están fuera del alcance de la administración del servidor PAWS. ## **Estatus actual** El servidor Argus está en línea y operativo. The C: drive remained stable at approximately **19.9 GB free** during follow-up monitoring, with no recurrence of the rapid disco consumption observed during the incident. PAWS considera la parte de infraestructura **servidora del incidente**. La causa subyacente del comportamiento de aplicación Lenel sigue siendo indeterminada y requiere seguimiento por el propietario/vendor de la aplicación.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 10, 2026 at 7:02 PM UTCinvestigating

   Hemos recibido informes de que Banner está experimentando problemas. El equipo de la OIT EAS está investigando, y haremos actualizaciones a intervalos de 1 hora. Se ha identificado una solución funcional: abrir una ventana del navegador privado o incognito para acceder a Banner. Si el sitio todavía es lento/no carga, cerrar y abrir otra nueva ventana privada o de incógnito; puede tomar algunos intentos, pero una vez que se hace una conexión confiable, puede seguir utilizando esa sesión hasta que se resuelva el problema! ¡Gracias por su paciencia durante la resolución de este tema!

2. August 10, 2026 at 8:03 PM UTCmonitoring

   El equipo de la OIT EAS ha identificado la cuestión con la Banner y ha aplicado una solución, que está siendo supervisada para la eficacia y estabilidad. ¡Gracias de nuevo por su paciencia durante la resolución de este tema! Usted puede esperar nuevas actualizaciones al final del día de negocios 5:00PM o como nueva información se pone disponible.

3. August 17, 2026 at 4:53 PM UTCresolved

   El equipo de la OIT EAS ha resuelto el problema con la Banner, y ha confirmado que la solución es estable. La cuestión se resolvió el 10 de agosto. Por favor reporte cualquier problema continuo con este servicio al ayudante de TI de su campus, y gracias de nuevo por su paciencia durante la resolución de este problema!

Traducido automáticamente desde la actualización oficial del incidente.

1. August 3, 2026 at 4:55 PM UTCinvestigating

   Hemos recibido informes de que la opción de inicio de sesión web de Iru está experimentando problemas. El equipo de Servicios de Apoyo Tecnológico de NTS está investigando y haremos actualizaciones a intervalos de 3 horas. Cambiar a un login local debe permitirle iniciar sesión en su Mac. ¡Gracias por su paciencia durante la resolución de este tema!

2. August 3, 2026 at 5:25 PM UTCinvestigating

   El equipo de servicios de apoyo tecnológico de NTS está investigando la causa de esta cuestión. Si no pueden conectarse a su UA Mac, intentan cambiar a la conexión local. Para cambiar a la entrada local: 1. Haga clic en el icono de perfil (la persona dentro de un círculo) en la esquina superior derecha de la pantalla. 2. Seleccione Cambiar a sesión local. 3. Introduzca sus credenciales de inicio de sesión en los campos de usuario y contraseña que aparecen cerca del centro inferior de la pantalla. 4. Haga clic en Para entrar. Si todavía no puede iniciar sesión, póngase en contacto con su mostrador de ayuda de TI local para obtener más asistencia. Gracias por su paciencia continua mientras trabajamos hacia una resolución completa; haremos nuevas actualizaciones a intervalos de 3 horas y a medida que se disponga de nueva información.

3. August 3, 2026 at 6:02 PM UTCinvestigating

   El equipo de NTS TSS está investigando la causa de estas cuestiones. El impulso de Iru para sincronizar sus contraseñas es seguro ignorar como mejor que usted es capaz mientras investigamos por qué se está solicitando. Si no pueden conectarse a su UA Mac, intentan cambiar a la conexión local. Para cambiar a la entrada local: 1. Haga clic en el icono de perfil (la persona dentro de un círculo) en la esquina superior derecha de la pantalla. 2. Seleccione Cambiar a sesión local. 3. Introduzca sus credenciales de inicio de sesión en los campos de usuario y contraseña que aparecen cerca del centro inferior de la pantalla. 4. Haga clic en Para entrar. Si todavía no puede iniciar sesión, póngase en contacto con su mostrador de ayuda de TI local para obtener más asistencia. Gracias por su paciencia continua mientras trabajamos hacia una resolución completa; haremos nuevas actualizaciones a intervalos de 1 hora y a medida que se disponga de nueva información.

4. August 3, 2026 at 7:44 PM UTCinvestigating

   El equipo de NTS TSS continúa investigando la causa de estas cuestiones. No hay actualizaciones adicionales en este momento. El impulso de Iru para sincronizar sus contraseñas es seguro ignorar como mejor que usted es capaz mientras investigamos por qué se está solicitando. Si no pueden conectarse a su UA Mac, intentan cambiar a la conexión local. Para cambiar a la entrada local: 1. Haga clic en el icono de perfil (la persona dentro de un círculo) en la esquina superior derecha de la pantalla. 2. Seleccione Cambiar a sesión local. 3. Introduzca sus credenciales de inicio de sesión en los campos de usuario y contraseña que aparecen cerca del centro inferior de la pantalla. 4. Haga clic en Para entrar. Si todavía no puede iniciar sesión, póngase en contacto con su mostrador de ayuda de TI local para obtener más asistencia. Gracias por su paciencia continua mientras trabajamos hacia una resolución completa; haremos nuevas actualizaciones a intervalos de 1 hora y a medida que se disponga de nueva información.

5. August 3, 2026 at 10:35 PM UTCmonitoring

   Hemos resuelto un problema reciente causado por un cambio inesperado con la autenticación de Duo que impactó a los ordenadores MacOS gestionados en todo el campus. Si utilizas un Mac gestionado por la universidad, tu experiencia de inicio de sesión ahora se restaura a operaciones normales. Sin embargo, la primera vez que vuelva a conectarse a su computadora después de esta solución, puede ver uno o dos avisos adicionales de autenticación Duo. Al iniciar sesión en su Mac gestionado por primera vez hoy: 1. Introduzca sus credenciales de cuenta habituales en la pantalla de inicio de sesión macOS. 2. Completar el impulso de Duo: Se le puede pedir que autentique a través de Duo un tiempo extra a medida que los permisos del sistema refresquen y vuelvan a sincronizarse con su cuenta. 3. Aprobar la solicitud en su aplicación móvil Duo, token de hardware o a través de su método MFA preferido como normal. 4. Seleccione Siguiente en el aviso Mantenga su cuenta segura. 5. Seleccione Siguiente en el Configurar un método de inicio de sesión. Si continúas encontrando errores de inicio de sesión, repetidos avisos para sincronizar contraseñas en el inicio de sesión, o cualquier otro problema conectado a tu Mac, por favor contacta a tu campus IT Helpdesk.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 5:46 PM UTCidentified

   El acceso a vdi.alaska.edu no está disponible, pero se ha identificado la causa de la salida. Cualquier acceso de escritorio a través de vdi.alaska.edu, y posiblemente el cliente grueso, no será capaz de acceder o utilizar máquinas virtuales desde esa dirección hasta que se haya resuelto el problema.

2. July 24, 2026 at 6:55 PM UTCidentified

   La UA ha identificado el problema con el acceso a vdi.alaska.edu y está trabajando para resolverlo. Cualquier acceso de escritorio a través de vdi.alaska.edu, y posiblemente el cliente grueso, no será capaz de utilizar máquinas virtuales de esa dirección. Gracias por su paciencia durante la resolución de este problema. Por favor, espere una actualización a las 11:50 AM y actualizaciones por hora después.

3. July 24, 2026 at 8:12 PM UTCidentified

   La UA ha identificado el problema con el acceso a vdi.alaska.edu y está trabajando para resolverlo. Cualquier acceso de escritorio a través de vdi.alaska.edu, y posiblemente el cliente grueso, no será capaz de utilizar máquinas virtuales de esa dirección. Gracias por su paciencia durante la resolución de este problema. Por favor, espere una actualización a las 12:50 AM y actualizaciones por hora después.

4. July 24, 2026 at 8:55 PM UTCidentified

   La UA ha identificado el problema con el acceso a vdi.alaska.edu y está trabajando para resolverlo. Cualquier acceso de escritorio a través de vdi.alaska.edu, y posiblemente el cliente grueso, no será capaz de utilizar máquinas virtuales de esa dirección. Gracias por su paciencia durante la resolución de este problema. Por favor, espere una actualización a las 1:50 PM y actualizaciones por hora después.

5. July 24, 2026 at 10:35 PM UTCidentified

   La UA ha identificado el problema con el acceso a vdi.alaska.edu y está trabajando para resolverlo. Cualquier acceso de escritorio a través de vdi.alaska.edu, y posiblemente el cliente grueso, no será capaz de utilizar máquinas virtuales de esa dirección. Gracias por su paciencia durante la resolución de este problema. Por favor, espere una actualización a las 5:00 PM.

6. July 25, 2026 at 12:03 AM UTCmonitoring

   UA ha resuelto el problema con el vdi.alaska.edu y confirmado la solución para ser estable. Esto se colocará en monitoreo hasta el final del negocio a las 5:00 PM. Por favor reporte cualquier problema continuo con este servicio al ayudante de TI de su campus, y gracias de nuevo por su paciencia durante la resolución de este problema!

7. July 25, 2026 at 1:06 AM UTCresolved

   UA ha resuelto el problema con el vdi.alaska.edu y confirmado la solución para ser estable. Por favor reporte cualquier problema continuo con este servicio al ayudante de TI de su campus y gracias de nuevo por su paciencia durante la resolución de este problema!

8. August 19, 2026 at 9:26 PM UTCpostmortem

   [vdi.alaska.edu](http://vdi.alaska.edu) access disruption. Certificados de puerta de acceso unificado caros. Hora de la fecha:07/23/2026 4:00 PM. Antecedentes [vdi.alaska.edu](http://vdi.alaska.edu) proporciona acceso de los usuarios al entorno VMware/Omnissa Horizon VDI. Ambos electrodomésticos Unified Access Gateway \(existen en la plataforma VXrail\) proporcionan la capa de acceso externo para usuarios que quieren acceder a su VDI tanto en el campus como remotamente. # Break Down of the Problem Ambos certificados en cada UAG expiraron el 23 de julio de 3:59 PM, 2026. El problema se notó el viernes 24 de julio alrededor de las 8:30 am, cuando los usuarios informaron de que no podían acceder a sus entornos VDI “My Desktop” cuando se resolvían a [vdi.alaska.edu](http://vdi.alaska.edu) When a user tried to resolve to [vdi.alaska.edu](http://vdi.alaska.edu) through their browser, they received a “Your connection is not private” notice and then would be blocked from reaching the [vdi.alaska.edu](http://vdi.alaska.edu) Página horizontal en absoluto. Medidas adoptadas para restaurar el servicio: Certificado de renovación solicitado de PAWS. Este certificado contenía el nombre de dominio primario, [vdi.alaska.edu](http://vdi.alaska.edu) pero también incluía los nombres alternativos \(ambos nombres 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) Duración del tiempo y el tiempo que el servicio fue restaurado: Jueves 23 de julio a las 4:00 pm - Viernes 24 a las 2:00 pm. # Target State / Goal Ambos UAG deben presentar continuamente certificados válidos, de confianza y acceso VDI externo e interno. # Root Cause Analysis # Ambos aparatos UAG presentaron certificados TLS caducados. TSS recibió una lista de electrodomésticos del servidor VXrail que habían estimado tiempos de cuando sus certificados estaban caducando. Ambos aparatos UAG no estaban en esta lista así que no pudimos dictar cuando sus certificados iban a expirar. # Desarrollar contramedidas He creado una hoja de cálculo de certificado maestro que ahora contiene la información de certificados de UAG para incluir fechas de caducidad. Lo comparto con nuestro equipo de TSS lidera para que podamos seguir monitoreando las expiraciones de certificado previstas en el futuro. Solicitud de acceso al servicio Certinext para futuras renovaciones de certificados. Calendario para la aplicación: Lo anterior debería permitirnos solicitar e implementar los certificados antes de que caducen en ambos UAG antes de que caducen. # Follow Up / Review Verificar las fechas de caducidad de certificados en ambos UAG monitoreando la hoja de cálculo del certificado maestro. Poner en una solicitud a PAWS para renovar el certificado, planificar un breve outage CAB, aplicar el certificado a ambos UAG y luego confirmar la renovación fue exitoso y el acceso se produce

Traducido automáticamente desde la actualización oficial del incidente.

1. May 29, 2026 at 4:26 PM 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. May 29, 2026 at 5:01 PM 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. May 30, 2026 at 1:01 AM 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. July 1, 2026 at 6:10 PM 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. May 28, 2026 at 4:02 PM 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. May 28, 2026 at 4:36 PM 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. May 28, 2026 at 5:06 PM 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. May 28, 2026 at 7:03 PM 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. May 28, 2026 at 7:16 PM 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. May 29, 2026 at 1:49 AM 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. July 1, 2026 at 6:03 PM 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. May 16, 2026 at 4:20 PM 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. May 16, 2026 at 5:49 PM 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. May 16, 2026 at 6:24 PM 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. May 16, 2026 at 7:23 PM 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. May 16, 2026 at 8:21 PM 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. May 16, 2026 at 9:31 PM 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. May 16, 2026 at 10:55 PM 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. May 16, 2026 at 11:34 PM 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. May 17, 2026 at 7:00 AM 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. May 17, 2026 at 3:52 PM 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. May 17, 2026 at 9:03 PM 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. May 18, 2026 at 1:19 AM 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. May 18, 2026 at 7:03 AM 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. May 18, 2026 at 3:03 PM 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. May 18, 2026 at 4:14 PM 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. May 18, 2026 at 5:14 PM 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. May 18, 2026 at 6:18 PM 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. May 18, 2026 at 7:02 PM 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. May 18, 2026 at 8:17 PM 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. May 18, 2026 at 9:36 PM 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. May 19, 2026 at 12:18 AM 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. May 19, 2026 at 4:21 PM 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. May 20, 2026 at 4:00 PM 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. May 21, 2026 at 4:30 PM 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. June 1, 2026 at 5:05 PM 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. May 15, 2026 at 10:52 PM 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. May 15, 2026 at 11:13 PM 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. May 16, 2026 at 12:57 AM 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. May 18, 2026 at 4:25 PM 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. May 11, 2026 at 5:23 PM 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. May 12, 2026 at 12:58 AM 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. May 12, 2026 at 4:23 PM 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. May 12, 2026 at 4:35 PM 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. April 28, 2026 at 1:06 AM 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. April 28, 2026 at 3:56 PM 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. April 29, 2026 at 12:57 AM 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. May 27, 2026 at 6:26 PM 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. April 9, 2026 at 6:59 PM 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. April 9, 2026 at 8:17 PM 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. April 9, 2026 at 8:52 PM 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. April 10, 2026 at 12:52 AM 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. April 10, 2026 at 4:11 PM 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. April 10, 2026 at 10:03 PM 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. April 8, 2026 at 7:23 PM 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. April 8, 2026 at 7:48 PM 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. April 8, 2026 at 8:24 PM 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. April 8, 2026 at 9:33 PM 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. April 9, 2026 at 1:04 AM 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. April 9, 2026 at 4:00 PM 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. April 9, 2026 at 7:05 PM 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. April 9, 2026 at 8:46 PM UTCresolved

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

9. May 6, 2026 at 6:33 PM 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. April 7, 2026 at 6:58 PM 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. April 7, 2026 at 7:57 PM 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. April 8, 2026 at 12:59 AM 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. April 8, 2026 at 4:09 PM 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. April 2, 2026 at 4:24 PM 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. April 2, 2026 at 6:03 PM 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. April 2, 2026 at 7:30 PM 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. April 2, 2026 at 7:53 PM 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. April 2, 2026 at 8:39 PM 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. April 3, 2026 at 1:02 AM 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. April 3, 2026 at 4:09 PM 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. April 3, 2026 at 10:15 PM 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. April 1, 2026 at 7:15 PM 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. April 1, 2026 at 7:52 PM 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. April 1, 2026 at 10:26 PM 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. April 1, 2026 at 10:48 PM 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. April 1, 2026 at 11:46 PM 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. March 25, 2026 at 7:13 PM 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. March 26, 2026 at 12:38 AM UTCresolved

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

3. April 8, 2026 at 6:20 PM UTCpostmortem

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

1. March 23, 2026 at 3:47 PM 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. March 23, 2026 at 3:53 PM 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. March 23, 2026 at 5:06 PM 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. March 23, 2026 at 5:41 PM 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. March 23, 2026 at 5:51 PM 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. March 20, 2026 at 5:06 PM 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. March 20, 2026 at 6:09 PM UTCmonitoring

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

3. March 20, 2026 at 6:12 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. March 20, 2026 at 6:14 PM UTCresolved

   Service is restored.

1. March 17, 2026 at 5:10 PM 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. March 17, 2026 at 6:11 PM 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!