54 University Of Alaska incidents · июнь 2025 г. — official updates, affected components, duration and resolution details.
Некоторые мобильные клиенты AT&T в настоящее время не могут выполнять звонки на номера телефонов кампуса. Эта проблема возникла в сети AT&T, а не в наших телефонных системах или службах. Мы следим за ситуацией и предоставим обновленную информацию, как только звонки будут подтверждены.
Автоматический перевод официального обновления инцидента.
Мы получили сообщения о том, что читатели карт в кампусе UAF в настоящее время испытывают проблемы. Команда OIT PAWS знает и активно работает над восстановлением сервера, который управляет этой системой. Мы будем делать обновления с интервалом в один час, поскольку они работают в направлении исправления. Координаторы зданий могут быть осведомлены об альтернативных методах доступа и маршрутах для конкретных помещений, но в настоящее время не существует широко распространенных обходных путей. Спасибо за терпение при решении этого вопроса!
Мы продолжаем работать над решением этой проблемы.
OIT PAWS сообщает, что сервер для систем свайпа карт Lenel успешно перезапущен и работает.
# **Root Cause Analysis – Argus Server Incident** ## **Executive Summary** The Argus server experienced a rapid loss of available space on the Windows C: drive. During investigation, PAWS identified significant disk activity occurring within the Lenel application log directory. Available disk space continued to decrease and eventually reached approximately 37 MB. PAWS cleanly shut down the server to prevent the operating system from reaching 0 available disk space and potentially causing additional system issues. PAWS expanded the C: drive and successfully returned the server to service. Following recovery, disk utilization stabilized and approximately 20 GB of free space remained available. PAWS is responsible for the underlying Windows server infrastructure but does not administer or support the Lenel application. The cause of the increased application-generated disk activity has not been determined and requires investigation by the application owner/vendor. ## **Incident Impact** The Argus server became unavailable during the incident and infrastructure recovery activities, resulting in an interruption to services dependent on the server. Reported impacts included on-campus door card reader functionality. ## **Timeline** **All times are Alaska Time.** **Approximately 11:04 AM** – PAWS was notified of an issue involving the Argus server and reported impacts to on-campus door card readers. The associated incident was TDX 991008. **Approximately 11:23 AM** – PAWS identified rapidly decreasing available space on the Windows C: drive. Resource Monitor showed significant write activity occurring within: `C:\ProgramData\Ln\logs` PAWS attempted to recover available disk capacity; however, C: utilization continued to increase. The C: drive eventually reached approximately **37 MB of available space**. PAWS cleanly shut down the VM to prevent the Windows system drive from reaching 0 available space and potentially causing additional operating system issues. PAWS performed the infrastructure work necessary to increase the capacity of the system drive. **Approximately 3:34 PM** – Infrastructure work was completed and the C: drive was expanded. The server was brought back online and PAWS verified normal server and disk operation. **Approximately 3:49 PM** – The server was reported operational. The following day, C: remained stable at approximately **19.9 GB free**, with no recurrence of the rapid disk consumption. ## **Root Cause** The immediate cause of the server outage was exhaustion of available capacity on the Windows C: drive. During the incident, PAWS observed significant disk write activity within the Lenel application log directory: `C:\ProgramData\Ln\logs` This activity rapidly consumed the remaining available capacity on the system drive. The underlying reason for the increased application-generated disk activity has **not been determined**. PAWS is responsible for administration of the underlying server infrastructure but does not administer, configure, or support the Lenel application. Determining why the application generated the increased disk activity requires investigation by the application owner/vendor and is outside the scope of this infrastructure RCA. ## **Contributing Factor** ### **Limited Available System Disk Capacity** The server did not have sufficient remaining C: drive capacity to absorb the unexpected increase in application-generated disk utilization. Available capacity eventually decreased to approximately **37 MB**, requiring PAWS to shut down the server to prevent Windows from reaching 0 available disk space. ## **Resolution** PAWS completed the following infrastructure recovery actions: * Investigated the rapidly decreasing C: drive capacity. * Identified the source directory associated with the increased disk activity. * Cleanly shut down the server before the system drive reached 0 available space. * Increased the capacity available to the Windows C: drive. * Returned the server to service. * Verified normal server and disk operation. * Continued monitoring disk utilization following recovery. Following recovery, the C: drive remained stable at approximately **19.9 GB free**. ## **Corrective and Preventative Actions** ### **Disk Capacity Monitoring** PAWS will review disk capacity monitoring and alert thresholds for the Argus server to provide sufficient notification when system drive capacity approaches critical levels. ### **Server Capacity** PAWS will continue monitoring C: drive utilization to verify that the additional capacity provides sufficient operating headroom under normal server conditions. ### **Application Investigation** The application owner/vendor will need to determine the cause of the unexpected increase in Lenel-generated disk activity and identify any application-level corrective actions that may be required. Application configuration, logging, retention, and application-level remediation are outside the scope of PAWS server administration. ## **Current Status** The Argus server is online and operational. The C: drive remained stable at approximately **19.9 GB free** during follow-up monitoring, with no recurrence of the rapid disk consumption observed during the incident. PAWS considers the **server infrastructure portion of the incident resolved**. The underlying cause of the Lenel application behavior remains undetermined and requires follow-up by the application owner/vendor.
Автоматический перевод официального обновления инцидента.
Мы получили сообщения о том, что Баннер в настоящее время испытывает проблемы. В настоящее время команда OIT EAS проводит расследование, и мы будем делать обновления с интервалом в 1 час. Выявлен функционирующий обходной путь: откройте частное окно браузера или инкогнито для доступа к Баннеру. Если сайт по-прежнему медленно/не загружается, закройте и откройте еще одно частное окно или окно инкогнито; это может занять несколько попыток, но как только надежное соединение будет сделано, вы можете продолжать использовать этот сеанс, пока проблема не будет решена! Спасибо за терпение при решении этого вопроса!
Команда OIT EAS определила проблему с баннером и внедрила исправление, которое контролируется на предмет эффективности и стабильности. Еще раз спасибо за терпение при решении этого вопроса! Вы можете ожидать дальнейших обновлений в конце рабочего дня 5:00 вечера или по мере поступления новой информации.
Команда OIT EAS решила проблему с Баннером и подтвердила, что исправление будет стабильным. Вопрос был решен 10 августа. Пожалуйста, сообщите о любых продолжающихся проблемах с этой услугой в службу поддержки ИТ вашего кампуса, и еще раз спасибо за ваше терпение во время решения этой проблемы!
Автоматический перевод официального обновления инцидента.
Мы получили сообщения о том, что опция входа в Интернет Iru в настоящее время испытывает проблемы. В настоящее время команда NTS Technology Support Services проводит расследование, и мы будем делать обновления с интервалом в 3 часа. Переключение на локальный логин должно позволить вам войти в свой Mac. Спасибо за терпение при решении этого вопроса!
Команда NTS Technology Support Services (TSS) в настоящее время изучает причину этой проблемы. Если вы не можете войти в свой UA Mac, они пытаются переключиться на локальный логин. Чтобы переключиться на локальный логин: 1. Нажмите на значок профиля (человек внутри круга) в правом верхнем углу экрана. 2.Выберите переключение на локальный логин. 3. Введите свои учетные данные входа в университет в полях имени пользователя и пароля, которые появляются в нижней части экрана. 4.Щелкните по знаку Чтобы войти. Если вы все еще не можете войти в систему, пожалуйста, свяжитесь с вашим местным отделом ИТ-помощи для дальнейшей помощи. Спасибо за ваше терпение, поскольку мы работаем над полным разрешением; мы будем делать дальнейшие обновления с интервалом в 3 часа и по мере поступления новой информации.
Команда NTS TSS в настоящее время расследует причину этих проблем. Подсказка Iru для синхронизации ваших паролей безопасна для игнорирования, насколько это возможно, пока мы изучаем, почему она предлагается. Если вы не можете войти в свой UA Mac, они пытаются переключиться на локальный логин. Чтобы переключиться на локальный логин: 1. Нажмите на значок профиля (человек внутри круга) в правом верхнем углу экрана. 2.Выберите переключение на локальный логин. 3. Введите свои учетные данные входа в университет в полях имени пользователя и пароля, которые появляются в нижней части экрана. 4.Щелкните по знаку Чтобы войти. Если вы все еще не можете войти в систему, пожалуйста, свяжитесь с вашим местным отделом ИТ-помощи для дальнейшей помощи. Спасибо за ваше терпение, поскольку мы работаем над полным разрешением; мы будем вносить дальнейшие обновления с интервалом в 1 час.
Команда NTS TSS продолжает расследование причин этих проблем. В настоящее время никаких дальнейших обновлений нет. Подсказка Iru для синхронизации ваших паролей безопасна для игнорирования, насколько это возможно, пока мы изучаем, почему она предлагается. Если вы не можете войти в свой UA Mac, они пытаются переключиться на локальный логин. Чтобы переключиться на локальный логин: 1. Нажмите на значок профиля (человек внутри круга) в правом верхнем углу экрана. 2.Выберите переключение на локальный логин. 3. Введите свои учетные данные входа в университет в полях имени пользователя и пароля, которые появляются в нижней части экрана. 4.Щелкните по знаку Чтобы войти. Если вы все еще не можете войти в систему, пожалуйста, свяжитесь с вашим местным отделом ИТ-помощи для дальнейшей помощи. Спасибо за ваше терпение, поскольку мы работаем над полным разрешением; мы будем вносить дальнейшие обновления с интервалом в 1 час.
Мы решили недавнюю проблему, вызванную неожиданным изменением аутентификации Duo, которое повлияло на логины управляемых компьютеров macOS в кампусе. Если вы используете Mac, управляемый университетом, ваш опыт входа в систему теперь восстановлен до обычных операций. Однако при первом входе на компьютер после этого исправления вы можете увидеть одну или две дополнительные подсказки аутентификации Duo. При входе в ваш управляемый Mac впервые: 1.Введите свои обычные учетные данные на главном экране входа в MacOS. 2. Заполните запрос(ы): Вам может быть предложено пройти аутентификацию через Duo дополнительное время, поскольку системные разрешения обновляются и повторно синхронизируются с вашей учетной записью. 3. Утвердить запрос в мобильном приложении Duo, аппаратном токене или с помощью предпочтительного метода MFA. 4.Выберите «Давайте держать вашу учетную запись в безопасности». 5.Выберите Next at the Set up a sign-in method prompt. Если вы продолжаете сталкиваться с ошибками входа в систему, повторяющимися подсказками для синхронизации паролей при входе в систему или любыми другими проблемами при входе в Mac, пожалуйста, свяжитесь с IT Helpdesk вашего кампуса.
Автоматический перевод официального обновления инцидента.
Доступ к vdi.alaska.edu недоступен, но причина сбоя выявлена. Любой доступ к рабочему столу через vdi.alaska.edu и, возможно, толстый клиент не смогут получить доступ или использовать виртуальные машины с этого адреса, пока проблема не будет решена.
UA определила проблему с доступом к vdi.alaska.edu и работает над ее решением. Любой доступ к рабочему столу через vdi.alaska.edu и, возможно, толстый клиент не смогут использовать виртуальные машины с этого адреса. Спасибо за ваше терпение во время решения этого вопроса. Пожалуйста, ожидайте обновления в 11:50 утра и ежечасные обновления после.
UA определила проблему с доступом к vdi.alaska.edu и работает над ее решением. Любой доступ к рабочему столу через vdi.alaska.edu и, возможно, толстый клиент не смогут использовать виртуальные машины с этого адреса. Спасибо за ваше терпение во время решения этого вопроса. Пожалуйста, ожидайте обновления в 12:50 утра и ежечасные обновления после.
UA определила проблему с доступом к vdi.alaska.edu и работает над ее решением. Любой доступ к рабочему столу через vdi.alaska.edu и, возможно, толстый клиент не смогут использовать виртуальные машины с этого адреса. Спасибо за ваше терпение во время решения этого вопроса. Пожалуйста, ожидайте обновления в 1:50 вечера и ежечасные обновления после.
UA определила проблему с доступом к vdi.alaska.edu и работает над ее решением. Любой доступ к рабочему столу через vdi.alaska.edu и, возможно, толстый клиент не смогут использовать виртуальные машины с этого адреса. Спасибо за ваше терпение во время решения этого вопроса. Пожалуйста, ожидайте обновления в 5:00.
UA решила проблему с vdi.alaska.edu и подтвердила, что исправление будет стабильным. Это будет помещено в мониторинг до конца бизнеса в 5:00 вечера. Пожалуйста, сообщите о любых продолжающихся проблемах с этой услугой в службу поддержки ИТ вашего кампуса, и еще раз спасибо за ваше терпение во время решения этой проблемы!
UA решила проблему с vdi.alaska.edu и подтвердила, что исправление будет стабильным. Пожалуйста, сообщите о любых продолжающихся проблемах с этой услугой в службу поддержки ИТ вашего кампуса и еще раз спасибо за ваше терпение во время решения этой проблемы!
[vdi.alaska.edu] (http://vdi.alaska.edu) нарушение доступа. Сертификаты Unified Access Gateway. Дата Время: 07/23/2026 4:00 PM. # Предыстория [vdi.alaska.edu] (http://vdi.alaska.edu) предоставляет пользователю доступ к среде VMware/Omnissa Horizon VDI. Оба устройства Unified Access Gateway (существуют на платформе VXrail) обеспечивают внешний уровень доступа для пользователей, которые хотят получить доступ к VDI как в кампусе, так и удаленно. # Разорвать проблему Оба сертификата на каждую УАГ истекли 23 июля 3:59 вечера 2026 года. Проблема была замечена в пятницу утром 24 июля около 8:30 утра, когда пользователи сообщили, что не могут получить доступ к своим средам VDI «Мой рабочий стол» при решении [vdi.alaska.edu] (http: / /vdi.alaska.edu). Когда пользователь попытался разрешить [vdi.alaska.edu] (http://vdi.alaska.edu) через свой браузер, он получил уведомление «Ваше соединение не является приватным», а затем был заблокирован от достижения [vdi.alaska.edu] (http://vdi.alaska.edu). Страница Горизонт вообще. Меры, принятые для восстановления службы: Запрашиваемый сертификат о продлении от PAWS. Этот сертификат содержал основное доменное имя [vdi.alaska.edu] (http://vdi.alaska.edu), но также включал альтернативные имена \(оба названия 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) Продолжительность сбоя и время восстановления сервиса: Четверг 23 июля 4:00 вечера - пятница 24th 2:00 вечера. #Цель/Цель Оба UAG должны постоянно предоставлять действительные, надежные сертификаты и внешний и внутренний доступ к VDI. # Анализ первопричин Оба устройства UAG представили просроченные сертификаты TLS. TSS получила список серверных устройств VXrail, которые оценивали время истечения срока действия сертификатов. Оба устройства UAG не были в этом списке, поэтому мы не смогли диктовать, когда их сертификаты истекут. #Разработать контрмеры Я создал таблицу мастер-сертификатов, которая теперь содержит информацию о сертификатах UAG, включая даты истечения срока действия. Я делюсь этим с нашей командой TSS, чтобы мы могли продолжать отслеживать ожидаемые истечения срока действия сертификата в будущем. Запрошенный доступ к сервису Certinext для дальнейшего продления сертификата. Расписание осуществления: Вышеизложенное должно позволить нам запрашивать и выполнять сертификаты до истечения срока их действия на обоих сертификатах UAG до истечения срока их действия. # Follow Up / Обзор Проверьте даты истечения срока действия сертификата на обоих UAG, отслеживая таблицу мастер-сертификата. Подать запрос в PAWS на продление сертификата, спланировать краткое отключение CAB, применить сертификат как к UAG, а затем подтвердить, что продление было успешным, и доступ происходит
Автоматический перевод официального обновления инцидента.
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!
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.
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!
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.
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!
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!
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!
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!
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.
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!
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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!
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!
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.
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!
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!
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!
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!
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.
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!
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!
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!
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!
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.“
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!
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.
A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.
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.
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!
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!
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!
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.
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!
A fix has been implemented and users are reporting access. We will continue to monitor the service and update the status page at 5PM.
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.
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!
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
This issue with UAOnline was identified and the fix is stable.
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.
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!
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!
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.
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.
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!
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!
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.
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.
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.
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.
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!
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!
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!
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!
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!
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!
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.
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.
UAF Facilities Services has completed work in Hess Village and the impacted network equipment is operating without issue.
A scheduled power outage in Hess Village affected the wireless network in that area.
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!
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!
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!
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.
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!
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!
Vendor identified the issue, restarted the affected service, and function was restored. We are currently monitoring for any further issues.
We are continuing to monitor for any further issues.
Service is restored.
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!
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!