Histórico de interrupções do University Of Alaska

1. 19 Eost 2026 da 23:57 UTCmonitoring

   Alguns clientes móveis AT&T são atualmente incapazes de completar chamadas para os números de telefone do campus. Esta questão tem sido identificada como originada pela rede AT&T, não pelos nossos sistemas ou serviços telefónicos. Estamos acompanhando a situação e vamos fornecer uma atualização uma vez que as chamadas são confirmadas para estar funcionando normalmente novamente.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Eost 2026 da 20:54 UTCidentified

   Recebemos relatos de que os leitores de cartões em todo o campus da UAF estão passando por problemas. A equipe do OIT PAWS está ciente e está trabalhando ativamente para recuperar o servidor que controla este sistema. Vamos fazer actualizações em intervalos de uma hora enquanto eles trabalham para uma correção. Os coordenadores de edifícios podem estar cientes de métodos e rotas de acesso alternativos para determinadas salas, mas não existe uma solução de trabalho generalizada neste momento. Obrigado pela vossa paciência durante a resolução desta questão!

2. 16 Eost 2026 da 22:59 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 16 Eost 2026 da 23:56 UTCresolved

   OIT PAWS relata que o servidor para os sistemas de passe de cartão Lenel foi reiniciado com sucesso e está operacional.

4. 19 Eost 2026 da 21:25 UTCpostmortem

   # ** Análise de Causas Root – Incidente com Servidor Argus** ** Resumo executivo ** O servidor Argus experimentou uma perda rápida de espaço disponível na unidade Windows C:. Durante a investigação, a PAWS identificou atividade de disco significativa ocorrendo no diretório de log da aplicação Lenel. O espaço em disco disponível continuou a diminuir e, eventualmente, atingiu aproximadamente 37 MB. O PAWS desligou o servidor de forma limpa para evitar que o sistema operacional atingisse 0 espaço disponível em disco e potencialmente causando problemas adicionais no sistema. O PAWS expandiu a unidade C: e retornou com sucesso o servidor ao serviço. Após a recuperação, a utilização do disco estabilizou e aproximadamente 20 GB de espaço livre permaneceram disponíveis. PAWS é responsável pela infraestrutura do servidor Windows subjacente, mas não administra ou suporta o aplicativo Lenel. A causa do aumento da atividade do disco gerado pela aplicação não foi determinada e requer investigação pelo proprietário/vendor da aplicação. □ □ * * Impacto Incidente * O servidor Argus ficou indisponível durante as atividades de recuperação de incidentes e infraestrutura, resultando em uma interrupção para serviços dependentes do servidor. Os impactos relatados incluíram a funcionalidade do leitor de cartões no campus. □ □ ** Timeline ** Todos os tempos são Alaska Time.** ** Aproximadamente 11:04 - PAWS foi notificado de um problema envolvendo o servidor Argus e relatou impactos para os leitores de cartões de porta no campus. O incidente associado foi TDX 99108. ** Aproximadamente 11:23 AM** – PAWS identificado diminuindo rapidamente o espaço disponível na unidade Windows C:. O Monitor de Recursos mostrou atividade de escrita significativa ocorrendo dentro: `C:\ProgramData\Ln\logs` O PAWS tentou recuperar a capacidade de disco disponível; no entanto, C: a utilização continuou a aumentar. A unidade C: eventualmente atingiu aproximadamente **37 MB de espaço disponível**. O PAWS desliga de forma limpa a VM para evitar que a unidade do sistema Windows atinja 0 espaço disponível e potencialmente cause problemas adicionais no sistema operacional. A PAWS realizou o trabalho de infraestrutura necessário para aumentar a capacidade de acionamento do sistema. ** Aproximadamente 3:34 PM** – O trabalho de infraestrutura foi concluído e o drive C: foi expandido. O servidor foi trazido de volta on-line e o PAWS verificou a operação normal do servidor e do disco. ** Aproximadamente 3:49 PM** O servidor foi reportado como operacional. No dia seguinte, C: permaneceu estável em aproximadamente **19,9 GB livre**, sem recorrência do consumo rápido de disco. □ □ # # ** Causa da raiz # A causa imediata da interrupção do servidor foi o esgotamento da capacidade disponível na unidade Windows C:. Durante o incidente, a PAWS observou atividade significativa de gravação de disco dentro do diretório de log da aplicação Lenel: `C:\ProgramData\Ln\logs` Esta atividade consumiu rapidamente a capacidade restante disponível na unidade do sistema. A razão subjacente para o aumento da atividade do disco gerado pela aplicação ** não foi determinada**. PAWS é responsável pela administração da infraestrutura do servidor subjacente, mas não administra, configura ou suporta a aplicação Lenel. Determinando por que a aplicação gerou o aumento da atividade do disco requer investigação pelo proprietário/vendor do aplicativo e está fora do escopo desta infraestrutura RCA. □ □ # # **Factor Contribuinte # ## # ** Capacidade de Disco do Sistema Disponível Limitada O servidor não tinha suficiente C restante: capacidade de acionamento para absorver o aumento inesperado na utilização de disco gerado pela aplicação. A capacidade disponível eventualmente diminuiu para aproximadamente **37 MB**, exigindo PAWS para desligar o servidor para evitar que o Windows alcance 0 espaço disponível em disco. □ □ **Resolução** A PAWS concluiu as seguintes ações de recuperação de infraestrutura: * Investigado o C rapidamente decrescente: capacidade de acionamento. * Identificou o diretório fonte associado com o aumento da atividade do disco. * Desligue o servidor de forma limpa antes que a unidade do sistema atinja 0 espaço disponível. * Aumento da capacidade disponível para o Windows C: unidade. * Devolveu o servidor ao serviço. * Verificado normal servidor e operação de disco. * Continuou monitorando a utilização do disco após a recuperação. Após a recuperação, a unidade C: permaneceu estável em aproximadamente **19,9 GB livre**. □ □ ** Ações Corretivas e Preventivas # # ** Monitorização da capacidade do disco # O PAWS analisará o monitoramento da capacidade do disco e os limiares de alerta para o servidor Argus para fornecer notificação suficiente quando a capacidade de movimentação do sistema se aproximar de níveis críticos. # # ** Capacidade do servidor # PAWS continuará monitorando C: utilização de drive para verificar se a capacidade adicional fornece suficiente sala de operação em condições normais de servidor. Tradução: O proprietário/vendor da aplicação terá de determinar a causa do aumento inesperado da actividade do disco gerado pela Lenel e identificar quaisquer medidas correctivas a nível da aplicação que possam ser necessárias. A configuração da aplicação, registro, retenção e remediação de nível de aplicação estão fora do escopo da administração do servidor PAWS. □ □ ## ** Status atual O servidor Argus está online e operacional. A unidade C: permaneceu estável em aproximadamente **19,9 GB livre** durante o acompanhamento, sem recorrência do consumo rápido de disco observado durante o incidente. PAWS considera a ** parte da infraestrutura do servidor do incidente resolvido**. A causa subjacente do comportamento da aplicação Lenel permanece indeterminada e requer acompanhamento pelo proprietário/vendor da aplicação.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Eost 2026 da 19:02 UTCinvestigating

   Recebemos relatórios de que a Banner está actualmente a enfrentar problemas. A equipa da OIT EAS está actualmente a investigar, e vamos fazer actualizações a intervalos de 1 hora. Foi identificada uma solução funcional: abrir uma janela privada ou incógnita para aceder ao Banner. Se o site ainda estiver lento/não carregando, feche e abra outra nova janela privada ou incógnita; pode levar algumas tentativas, mas uma vez feita uma conexão confiável, você pode continuar a usar essa sessão até que o problema seja resolvido! Obrigado pela vossa paciência durante a resolução desta questão!

2. 10 Eost 2026 da 20:03 UTCmonitoring

   A equipe da OIT EAS identificou o problema com a Banner e implementou uma correção, que está sendo monitorada quanto à eficácia e estabilidade. Obrigado mais uma vez pela vossa paciência durante a resolução desta questão! Você pode esperar novas atualizações no final do dia útil 5:00 PM ou como novas informações se tornam disponíveis.

3. 17 Eost 2026 da 16:53 UTCresolved

   A equipe da OIT EAS resolveu o problema com o Banner, e confirmou a fixação para ser estável. O assunto foi resolvido em 10 de agosto. Por favor, relate quaisquer problemas contínuos com este serviço para o helpdesk de TI do seu campus, e obrigado novamente por sua paciência durante a resolução deste problema!

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Eost 2026 da 16:55 UTCinvestigating

   Recebemos relatórios de que a opção de login do Iru está atualmente com problemas. A equipe de Serviços de Suporte de Tecnologia da NTS está atualmente investigando, e faremos atualizações em intervalos de 3 horas. Mudar para o login local deve permitir que você faça login no seu Mac. Obrigado pela vossa paciência durante a resolução desta questão!

2. 3 Eost 2026 da 17:25 UTCinvestigating

   A equipe de Serviços de Suporte à Tecnologia (TSS) da NTS está atualmente investigando a causa desta questão. Se não conseguir entrar no seu Mac UA, eles tentam mudar para o login local. Para mudar para o login local: 1. Clique no ícone do perfil (a pessoa dentro de um círculo) no canto superior direito da tela. 2. Selecione Mudar para Login Local. 3. Digite suas credenciais de login da Universidade nos campos de nome de usuário e senha que aparecem perto do centro inferior da tela. 4. Clique em assinar Entrar para entrar. Se você ainda não conseguir fazer login, entre em contato com o seu Departamento de Ajuda de TI local para obter mais assistência. Obrigado por sua paciência contínua enquanto trabalhamos para uma resolução completa; vamos fazer novas atualizações em intervalos de 3 horas e como novas informações se tornam disponíveis.

3. 3 Eost 2026 da 18:02 UTCinvestigating

   A equipe NTS TSS está atualmente investigando a causa desses problemas. O prompt Iru para sincronizar suas senhas é seguro para ignorar o melhor que você é capaz enquanto investigamos por que está sendo solicitado. Se não conseguir entrar no seu Mac UA, eles tentam mudar para o login local. Para mudar para o login local: 1. Clique no ícone do perfil (a pessoa dentro de um círculo) no canto superior direito da tela. 2. Selecione Mudar para Login Local. 3. Digite suas credenciais de login da Universidade nos campos de nome de usuário e senha que aparecem perto do centro inferior da tela. 4. Clique em assinar Entrar para entrar. Se você ainda não conseguir fazer login, entre em contato com o seu Departamento de Ajuda de TI local para obter mais assistência. Obrigado por sua paciência contínua enquanto trabalhamos para uma resolução completa; vamos fazer novas atualizações em intervalos de 1 hora e como novas informações se tornam disponíveis.

4. 3 Eost 2026 da 19:44 UTCinvestigating

   A equipe do NTS TSS continua investigando a causa desses problemas. Não há mais atualizações neste momento. O prompt Iru para sincronizar suas senhas é seguro para ignorar o melhor que você é capaz enquanto investigamos por que está sendo solicitado. Se não conseguir entrar no seu Mac UA, eles tentam mudar para o login local. Para mudar para o login local: 1. Clique no ícone do perfil (a pessoa dentro de um círculo) no canto superior direito da tela. 2. Selecione Mudar para Login Local. 3. Digite suas credenciais de login da Universidade nos campos de nome de usuário e senha que aparecem perto do centro inferior da tela. 4. Clique em assinar Entrar para entrar. Se você ainda não conseguir fazer login, entre em contato com o seu Departamento de Ajuda de TI local para obter mais assistência. Obrigado por sua paciência contínua enquanto trabalhamos para uma resolução completa; vamos fazer novas atualizações em intervalos de 1 hora e como novas informações se tornam disponíveis.

5. 3 Eost 2026 da 22:35 UTCmonitoring

   Resolvemos um problema recente causado por uma mudança inesperada com a autenticação Duo que afetou logins de computador macOS gerenciados em todo o campus. Se você usar um Mac gerenciado pela universidade, sua experiência de login agora é restaurada para operações normais. No entanto, a primeira vez que você entrar em seu computador após esta correção, você pode ver um ou dois avisos de autenticação Duo adicionais. Ao iniciar sessão no Mac gerenciado pela primeira vez hoje: 1. Digite suas credenciais de conta habituais na tela de login do macOS primário. 2. Complete o prompt(s) Duo: Você pode ser solicitado a autenticar através de Duo um tempo extra como permissões do sistema atualizar e re-sincronizar com sua conta. 3. Aprovar o pedido em seu aplicativo móvel Duo, token de hardware, ou através de seu método preferido MFA como normal. 4. Selecione Próximo no Vamos manter sua conta segura prompt. 5. Selecione Próximo na configuração de um prompt de método de login. Se você continuar a encontrar erros de login, avisos repetidos para sincronizar senhas no login ou quaisquer outros problemas de login no Mac, por favor, entre em contato com o seu campus IT Helpdesk.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 17:46 UTCidentified

   O acesso ao vdi.alaska.edu não está disponível, mas a causa da avaria foi identificada. Qualquer acesso à área de trabalho através do vdi.alaska.edu, e possivelmente o cliente espesso, não será capaz de acessar ou usar máquinas virtuais desse endereço até que o problema seja resolvido.

2. 24 Gouere 2026 da 18:55 UTCidentified

   A UA identificou o problema com o acesso ao vdi.alaska.edu e está trabalhando para resolvê-lo. Qualquer acesso de desktop através de vdi.alaska.edu, e possivelmente o cliente grosso, não será capaz de usar máquinas virtuais a partir desse endereço. Obrigado pela vossa paciência durante a resolução desta questão. Por favor, aguarde uma atualização às 11:50 e atualizações horárias depois.

3. 24 Gouere 2026 da 20:12 UTCidentified

   A UA identificou o problema com o acesso ao vdi.alaska.edu e está trabalhando para resolvê-lo. Qualquer acesso de desktop através de vdi.alaska.edu, e possivelmente o cliente grosso, não será capaz de usar máquinas virtuais a partir desse endereço. Obrigado pela vossa paciência durante a resolução desta questão. Por favor, aguarde uma atualização às 12:50 e atualizações horárias depois.

4. 24 Gouere 2026 da 20:55 UTCidentified

   A UA identificou o problema com o acesso ao vdi.alaska.edu e está trabalhando para resolvê-lo. Qualquer acesso de desktop através de vdi.alaska.edu, e possivelmente o cliente grosso, não será capaz de usar máquinas virtuais a partir desse endereço. Obrigado pela vossa paciência durante a resolução desta questão. Por favor, aguarde uma atualização às 1:50 e atualizações horárias depois.

5. 24 Gouere 2026 da 22:35 UTCidentified

   A UA identificou o problema com o acesso ao vdi.alaska.edu e está trabalhando para resolvê-lo. Qualquer acesso de desktop através de vdi.alaska.edu, e possivelmente o cliente grosso, não será capaz de usar máquinas virtuais a partir desse endereço. Obrigado pela vossa paciência durante a resolução desta questão. Por favor, aguarde uma atualização às 17h.

6. 25 Gouere 2026 da 00:03 UTCmonitoring

   A UA resolveu o problema com o vdi.alaska.edu e confirmou que a solução era estável. Isto será colocado em monitoramento até o fim dos negócios às 17:00. Por favor, relate quaisquer problemas contínuos com este serviço para o helpdesk de TI do seu campus, e obrigado novamente por sua paciência durante a resolução deste problema!

7. 25 Gouere 2026 da 01:06 UTCresolved

   A UA resolveu o problema com o vdi.alaska.edu e confirmou que a solução era estável. Por favor, informe quaisquer problemas contínuos com este serviço para o helpdesk de TI do seu campus e obrigado novamente pela sua paciência durante a resolução deste problema!

8. 19 Eost 2026 da 21:26 UTCpostmortem

   [vdi.alaska.edu] (http://vdi.alaska.edu) □ Certificados Unified Access Gateway Expirados. Data: 23/07/2026 16:00. Fundo [vdi.alaska.edu](http://vdi.alaska.edu) fornece acesso ao ambiente VMware/Omnissa Horizon VDI. □ Ambos os aparelhos Unified Access Gateway \(existem na plataforma VXrail\) fornecem a camada externa de acesso para usuários que querem acessar seu VDI tanto no campus quanto remotamente. □ Quebre o problema Ambos os certificados em cada UAG expirou em 23 de julho 3:59 PM, 2026. □ O problema foi notado sexta-feira de manhã 24 de julho por volta das 8:30 da manhã, quando os usuários relataram que não podiam acessar seus ambientes de VDI “Meu Desktop” ao resolverem para [vdi.alaska.edu](http://vdi.alaska.edu) □ □ Quando um utilizador tentou resolver [vdi.alaska.edu](http://vdi.alaska.edu) através do seu navegador, recebeu um aviso “A sua ligação não é privada” e, em seguida, seria impedido de chegar ao [vdi.alaska.edu](http://vdi.alaska.edu) Página Horizon. □ Ações tomadas para restaurar o serviço: Certificado de renovação solicitado da PAWS. Este certificado continha o nome de domínio principal, [vdi.alaska.edu] (http://vdi.alaska.edu), mas também incluía os nomes alternativos \(ambos os nomes 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) □ □ Duração da interrupção e tempo de restauração do serviço: Quinta-feira, 23 de Julho, 16h. Sexta, 24h. □ □ □ # Estado-alvo / Objectivo □ Ambos os UAG devem apresentar continuamente certificados válidos, confiáveis e acesso VDI externo e interno □ # Análise da Causa Raiz # Ambos os aparelhos UAG estavam apresentando certificados TLS expirados. O TSS recebeu uma lista de aparelhos de servidor VXrail que tinham estimado o tempo de expiração dos certificados. Ambos os aparelhos UAG não estavam nesta lista, por isso não fomos capazes de ditar quando os seus certificados iriam expirar. # Desenvolver contramedidas Criei uma planilha de certificado mestre que agora contém ambas as informações de certificado da UAG para incluir datas de validade. Estou a partilhá-lo com os nossos líderes da equipa TSS para podermos continuar a monitorizar as expirações esperadas do certificado no futuro. Acesso solicitado ao serviço Certinext para futuras renovações de certificados. □ Calendário para a execução: O acima deve permitir-nos solicitar e implementar os certificados antes de expirar em ambos UAG antes de expirar. Acompanhamento / Revisão Verifique as datas de expiração do certificado em ambas as UAGs monitorando a planilha do certificado mestre. Apresentar um pedido à PAWS para renovar o certificado, planear uma breve interrupção do CAB, aplicar o certificado a ambos os UAG e, em seguida, confirmar a renovação foi bem sucedido e o acesso ocorre

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Gouere 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Gouere 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 20:46 UTCresolved

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

9. 6 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 00:38 UTCresolved

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

3. 8 Ebrel 2026 da 18:20 UTCpostmortem

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

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

   We are continuing to monitor for any further issues.

4. 20 Meurzh 2026 da 18:14 UTCresolved

   Service is restored.

1. 17 Meurzh 2026 da 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 Meurzh 2026 da 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!