54 University Of Alaska incidents · czerwiec 2025 — official updates, affected components, duration and resolution details.
Niektórzy mobilni klienci AT & T nie są obecnie w stanie wykonać połączeń do kampusu numerów telefonów. Problem ten został zidentyfikowany jako pochodzący z sieci AT & T, a nie z naszych systemów telefonicznych lub usług. Monitorujemy sytuację i dostarczymy aktualizację po potwierdzeniu, że połączenia działają normalnie.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Otrzymaliśmy raporty, że czytelnicy kart w kampusie UAF doświadczają obecnie problemów. Zespół OIT PAWS jest świadomy i aktywnie pracuje nad odzyskaniem serwera sterującego tym systemem. Będziemy robić aktualizacje w odstępach jednogodzinnych, gdy będą pracować nad naprawą. Koordynatorzy budynkowi mogą być świadomi alternatywnych metod i tras dostępu do poszczególnych pomieszczeń, ale obecnie nie ma szeroko zakrojonych działań. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii!
Kontynuujemy prace nad rozwiązaniem tego problemu.
OIT PAWS informuje, że serwer dla systemów Swipe kart Lenel został ponownie uruchomiony i działa.
* * * Root Cause Analysis - Argus Server Incident * * * * * Executive Summary * * Serwer Argus doświadczył szybkiej utraty dostępnej przestrzeni na dysku Windows C. Podczas dochodzenia PAWS zidentyfikował znaczącą aktywność dysku występującą w katalogu dzienników aplikacji Lenela. Dostępne miejsce na dysku nadal spadało i ostatecznie osiągnęło około 37 MB. PAWS wyraźnie wyłączył serwer, aby system operacyjny nie osiągnął 0 dostępnej przestrzeni dyskowej i potencjalnie spowodował dodatkowe problemy systemowe. PAWS rozszerzył napęd C: i z powodzeniem zwrócił serwer do serwisu. Po odzyskaniu, wykorzystanie dysku ustabilizowane i około 20 GB wolnego miejsca pozostało dostępne. PAWS jest odpowiedzialny za podstawową infrastrukturę serwera Windows, ale nie zarządza ani nie wspiera aplikacji Lenel. Przyczyna zwiększonej aktywności dyskowej generowanej przez aplikację nie została określona i wymaga zbadania przez właściciela / sprzedawcę aplikacji. Uzasadnienie Uzasadnienie / Incydent Impact Serwer Argus stał się niedostępny podczas działań związanych z odzyskiwaniem infrastruktury i incydentu, co doprowadziło do przerwania świadczenia usług zależnych od serwera. Zgłoszone skutki obejmowały funkcje czytnika kart drzwi w kampusie. Uzasadnienie Uzasadnienie * * * Timeline * * * * All time are Alaska Time. * * * * Około 11: 04 AM * * - PAWS został powiadomiony o problemie związanym z serwerem Argus i zgłoszone skutki do czytników kart drzwi na kampusie. Incydent związany był z TDX 991008. * * Około 11: 23 AM * * - PAWS zidentyfikował szybko zmniejszającą się przestrzeń dostępną na dysku Windows C. Monitoring zasobów wykazał znaczącą aktywność pisarską w obrębie: 'C:\ ProgramData\ Ln\ logs' PAWS próbował odzyskać dostępną pojemność dysku, jednak C: wykorzystanie nadal rośnie. Napęd C: ostatecznie osiągnął w przybliżeniu * * 37 MB dostępnej przestrzeni * *. PAWS czysto wyłączyć VM, aby zapobiec napędowi systemu Windows z osiągnięcia 0 dostępnej przestrzeni i potencjalnie powodując dodatkowe problemy systemu operacyjnego. PAWS wykonał prace infrastrukturalne niezbędne do zwiększenia przepustowości napędu systemowego. * * Około 3: 34 PM * * - Prace infrastrukturalne zostały zakończone i napęd C: został rozszerzony. Serwer został przywrócony online i PAWS zweryfikowało normalne działanie serwera i dysku. * * Około 3: 49 PM * * - Serwer został zgłoszony jako operacyjny. Następnego dnia, C: pozostawał stabilny w przybliżeniu * * 19,9 GB wolny * *, bez ponownego szybkiego zużycia dysku. Uzasadnienie Uzasadnienie * * * Root Cause * * Bezpośrednią przyczyną awarii serwera było wyczerpanie dostępnej pojemności na dysku Windows C. Podczas incydentu PAWS zaobserwował znaczącą aktywność zapisu dysku w katalogu dziennika aplikacji Lenel: 'C:\ ProgramData\ Ln\ logs' Aktywność ta szybko zużyła pozostałe dostępne moce na napędzie systemowym. Podstawowa przyczyna zwiększonej aktywności dysku generowanej przez aplikację nie została określona * *. PAWS jest odpowiedzialny za zarządzanie bazową infrastrukturą serwera, ale nie zarządza, nie konfiguruje ani nie obsługuje aplikacji Lenel. Określenie, dlaczego aplikacja wygenerowała zwiększoną aktywność dysków, wymaga zbadania przez właściciela / sprzedawcę aplikacji i wykracza poza zakres tej infrastruktury RCA. Uzasadnienie Uzasadnienie * * * Contributing Factor * * # # # * * Ograniczona dostępna pojemność dysków systemu * * Serwer nie miał wystarczającej pojemności napędowej C, aby wchłonąć nieoczekiwany wzrost wykorzystania dysków generowanych przez aplikacje. Dostępna pojemność zmniejszyła się do około * * 37 MB * *, wymagając od PAWS wyłączenia serwera, aby system Windows nie osiągnął 0 dostępnej przestrzeni dyskowej. Uzasadnienie Uzasadnienie Rezolucja PAWS zrealizował następujące działania w zakresie odzyskiwania infrastruktury: * Zbadano szybko malejące C: pojemność napędu. * Zidentyfikowano katalog źródłowy związany ze zwiększoną aktywnością dysku. * Czyste wyłączenie serwera zanim napęd systemowy osiągnął 0 dostępnej przestrzeni. * Zwiększona pojemność dostępna dla Windows C: drive. * Zwrócił serwer do serwisu. * Zweryfikowane normalne działanie serwera i dysku. * Kontynuowane monitorowanie wykorzystania dysku po odzyskaniu. Po odzyskaniu C: napęd pozostał stabilny na poziomie około * * 19,9 GB wolnego * *. Uzasadnienie Uzasadnienie * * * Działania naprawcze i zapobiegawcze * * * * * Monitoring pojemności dysków * * PAWS dokona przeglądu monitorowania pojemności dysków i progów alarmowych dla serwera Argus, aby zapewnić wystarczającą notyfikację, gdy napęd systemu zbliża się do poziomów krytycznych. * * * Server Capacity * * PAWS będzie nadal monitorował C: wykorzystanie napędu w celu sprawdzenia, czy dodatkowa pojemność zapewnia wystarczającą liczbę zagłówków operacyjnych w normalnych warunkach serwerowych. * * * Application Investigation * * Właściciel / sprzedawca aplikacji będzie musiał określić przyczynę nieoczekiwanego wzrostu aktywności dysków generowanych przez Lenel- i określić wszelkie działania naprawcze na poziomie aplikacji, które mogą być wymagane. Konfiguracja aplikacji, logowanie, retencja i rekultywacja poziomu aplikacji nie wchodzą w zakres administracji serwera PAWS. Uzasadnienie Uzasadnienie * * * Current Status * * Serwer Argus działa online. Napęd C: utrzymywał się na stabilnym poziomie w przybliżeniu * * 19,9 GB wolnego * * podczas obserwacji, bez nawrotu szybkiego zużycia dysku obserwowanego podczas incydentu. PAWS uważa, że część infrastruktury serwera * * rozwiązanego incydentu * *. Podstawowa przyczyna zachowania aplikacji Lenel pozostaje nieokreślona i wymaga kontynuacji przez właściciela aplikacji / sprzedawcy.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Otrzymaliśmy doniesienia, że Banner ma obecnie problemy. Zespół EAS OIT prowadzi śledztwo i będziemy robić aktualizacje w odstępach 1-godzinnych. Zidentyfikowano funkcjonującą pracę: otworzyć prywatne lub incognito okno przeglądarki, aby uzyskać dostęp do Banner. Jeśli strona jest nadal powolny / nie ładowanie, zamknąć i otworzyć inne nowe okno prywatne lub incognito; może to wymagać kilku prób, ale po wykonaniu niezawodnego połączenia, można nadal korzystać z tej sesji do czasu rozwiązania problemu! Dziękuję za cierpliwość podczas rozwiązywania tej kwestii!
Zespół OIT EAS zidentyfikował problem z Bannerem i wprowadził rozwiązanie, które jest monitorowane pod kątem skuteczności i stabilności. Jeszcze raz dziękuję za cierpliwość podczas rozwiązywania tej kwestii! Możesz spodziewać się dalszych aktualizacji na koniec dnia roboczego 5: 00PM lub jak nowe informacje stają się dostępne.
Zespół EAS OIT rozwiązał problem z Bannerem i potwierdził stabilność. Sprawa została rozwiązana 10 sierpnia. Proszę zgłosić wszelkie nierozwiązane problemy związane z tą usługą do działu informatycznego Państwa kampusu i ponownie podziękować za cierpliwość w trakcie rozwiązywania tej kwestii!
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Otrzymaliśmy raporty, że opcja logowania Iru jest obecnie doświadczająca problemów. Zespół NTS Technology Support Services prowadzi obecnie dochodzenie i będziemy dokonywać aktualizacji w odstępach 3 godzin. Przełączenie do lokalnego logowania powinno umożliwić zalogowanie się do komputera Mac. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii!
Zespół NTS Technology Support Services (TSS) bada obecnie przyczynę tego problemu. Jeśli nie możesz zalogować się do komputera UA Mac, spróbuj przełączyć się na logowanie lokalne. Aby przejść do lokalnego logowania: 1. Kliknij ikonę profilu (osoba wewnątrz okręgu) w prawym górnym rogu ekranu. 2. Wybierz Przełącz na lokalny logowanie. 3. Wpisz dane logowania na uniwersytecie w polu nazwy użytkownika i hasła, które pojawiają się w pobliżu dolnego centrum ekranu. 4. Kliknij znak Zaloguj się. Jeśli nadal nie możesz się zalogować, skontaktuj się z lokalnym biurem pomocy IT, aby uzyskać dalszą pomoc. Dziękujemy za ciągłą cierpliwość, ponieważ pracujemy nad pełną rezolucją; będziemy dokonywać dalszych aktualizacji w odstępach 3 godzin i gdy nowe informacje staną się dostępne.
Zespół NTS TSS bada obecnie przyczynę tych problemów. Prośba Iru o synchronizację haseł jest bezpieczna do zignorowania tak dobrze, jak jest w stanie, podczas gdy my badamy, dlaczego jest to proszone. Jeśli nie możesz zalogować się do komputera UA Mac, spróbuj przełączyć się na logowanie lokalne. Aby przejść do lokalnego logowania: 1. Kliknij ikonę profilu (osoba wewnątrz okręgu) w prawym górnym rogu ekranu. 2. Wybierz Przełącz na lokalny logowanie. 3. Wpisz dane logowania na uniwersytecie w polu nazwy użytkownika i hasła, które pojawiają się w pobliżu dolnego centrum ekranu. 4. Kliknij znak Zaloguj się. Jeśli nadal nie możesz się zalogować, skontaktuj się z lokalnym biurem pomocy IT, aby uzyskać dalszą pomoc. Dziękujemy za ciągłą cierpliwość, ponieważ pracujemy na rzecz pełnej rezolucji; będziemy dokonywać dalszych aktualizacji w odstępach 1 godziny i jak nowe informacje stają się dostępne.
Zespół NTS TSS nadal bada przyczyny tych problemów. W tej chwili nie ma dalszych aktualizacji. Prośba Iru o synchronizację haseł jest bezpieczna do zignorowania tak dobrze, jak jest w stanie, podczas gdy my badamy, dlaczego jest to proszone. Jeśli nie możesz zalogować się do komputera UA Mac, spróbuj przełączyć się na logowanie lokalne. Aby przejść do lokalnego logowania: 1. Kliknij ikonę profilu (osoba wewnątrz okręgu) w prawym górnym rogu ekranu. 2. Wybierz Przełącz na lokalny logowanie. 3. Wpisz dane logowania na uniwersytecie w polu nazwy użytkownika i hasła, które pojawiają się w pobliżu dolnego centrum ekranu. 4. Kliknij znak Zaloguj się. Jeśli nadal nie możesz się zalogować, skontaktuj się z lokalnym biurem pomocy IT, aby uzyskać dalszą pomoc. Dziękujemy za ciągłą cierpliwość, ponieważ pracujemy na rzecz pełnej rezolucji; będziemy dokonywać dalszych aktualizacji w odstępach 1 godziny i jak nowe informacje stają się dostępne.
Rozwiązaliśmy niedawny problem spowodowany nieoczekiwaną zmianą uwierzytelniania Duo, który wpłynął na zarządzane logi komputerów w całym kampusie. Jeśli używasz zarządzanego university- Mac, Twoje doświadczenie logowania jest teraz przywrócone do normalnych operacji. Jednak po pierwszym zalogowaniu się do komputera po tej poprawce, możesz zobaczyć jeden lub dwa dodatkowe polecenia uwierzytelniania Duo. Podczas podpisywania się w swoim zarządzanym Mac po raz pierwszy dzisiaj: 1. Wpisz swoje zwykłe dane konta na głównym ekranie logowania w systemie Mac. 2. Ukończ tryb duo: Możesz zostać poproszony o uwierzytelnienie przez Duo dodatkowego czasu jako uprawnienia systemowe odświeżyć i ponownie zsynchronizować z kontem. 3. Zatwierdzenie wniosku na aplikacji mobilnej Duo, tokenie sprzętowym lub za pomocą preferowanej metody MFA jako normalne. 4. Zaznacz Dalej na liście Let 's keep your account security shown. 5. Zaznacz Dalej przy ustawieniu sygna-in. Jeśli w dalszym ciągu napotkasz błędy logowania, powtarzające się sygnały do synchronizacji haseł podczas logowania lub jakiekolwiek inne problemy logowania się do komputera Mac, skontaktuj się z kampusem IT Helpdesk.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Dostęp do vdi.alaska.edu jest niedostępny, ale przyczyna awarii została zidentyfikowana. Każdy dostęp na pulpicie przez vdi.alaska.edu, a być może przez grubego klienta, nie będzie w stanie uzyskać dostępu lub używać maszyn wirtualnych z tego adresu do czasu rozwiązania problemu.
UA zidentyfikowała problem dostępu do vdi.alaska.edu i pracuje nad jego rozwiązaniem. Każdy dostęp na pulpicie przez vdi.alaska.edu, a być może przez grubego klienta, nie będzie w stanie korzystać z maszyn wirtualnych z tego adresu. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii. Proszę oczekiwać aktualizacji o 11: 50 rano i co godzinę aktualizacji po.
UA zidentyfikowała problem dostępu do vdi.alaska.edu i pracuje nad jego rozwiązaniem. Każdy dostęp na pulpicie przez vdi.alaska.edu, a być może przez grubego klienta, nie będzie w stanie korzystać z maszyn wirtualnych z tego adresu. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii. Proszę oczekiwać aktualizacji o 12: 50 rano i co godzinę aktualizacji po.
UA zidentyfikowała problem dostępu do vdi.alaska.edu i pracuje nad jego rozwiązaniem. Każdy dostęp na pulpicie przez vdi.alaska.edu, a być może przez grubego klienta, nie będzie w stanie korzystać z maszyn wirtualnych z tego adresu. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii. Oczekuj aktualizacji o 13: 50, a następnie co godzinę.
UA zidentyfikowała problem dostępu do vdi.alaska.edu i pracuje nad jego rozwiązaniem. Każdy dostęp na pulpicie przez vdi.alaska.edu, a być może przez grubego klienta, nie będzie w stanie korzystać z maszyn wirtualnych z tego adresu. Dziękuję za cierpliwość podczas rozwiązywania tej kwestii. Oczekuj aktualizacji o 17: 00.
UA rozwiązała problem z vdi.alaska.edu i potwierdziła stabilizację. Będzie to monitorowane do końca działalności o 17: 00. Proszę zgłosić wszelkie nierozwiązane problemy związane z tą usługą do działu informatycznego Państwa kampusu i ponownie podziękować za cierpliwość w trakcie rozwiązywania tej kwestii!
UA rozwiązała problem z vdi.alaska.edu i potwierdziła stabilizację. Proszę zgłosić wszelkie nierozwiązane problemy związane z tą usługą do działu informatycznego Państwa kampusu i ponownie podziękować za cierpliwość podczas rozwiązywania tej kwestii!
[vdi.alaska.edu] (http: / / vdi.alaska.edu) Uzasadnienie Wygasłe ujednolicone certyfikaty bramy dostępu. Data: 07 / 23 / 2026 4: 00 PM. # Tło [vdi.alaska.edu] (http: / / vdi.alaska.edu) zapewnia użytkownikom dostęp do środowiska VMware / Omnissa Horizon VDI. Uzasadnienie Zarówno Unified Access Gateway urządzeń\ (istniejących na platformie VXrail\) zapewniają zewnętrzną warstwę dostępu dla użytkowników, którzy chcą uzyskać dostęp do swoich VDI zarówno w kampusie lub zdalnie. Uzasadnienie # Break Down of the Problem Oba certyfikaty dotyczące każdego UAG wygasły 23 lipca 2026 r., godz. 15.59. Uzasadnienie Problem został zauważony w piątek rano 24 lipca około 8: 30 rano, gdy użytkownicy zgłosili, że nie mogli uzyskać dostępu do swoich środowisk VDI "Mój pulpit" podczas rozwiązywania [vdi.alaska.edu] (http: / / vdi.alaska.edu) Uzasadnienie Uzasadnienie Kiedy użytkownik próbował rozwiązać [vdi.alaska.edu] (http: / / vdi.alaska.edu) poprzez swoją przeglądarkę, otrzymał zawiadomienie "Twoje połączenie nie jest prywatne", a następnie zostałby zablokowany przed dotarciem do [vdi.alaska.edu] (http: / / vdi.alaska.edu) Strona Horizon w ogóle. Uzasadnienie Działania podjęte w celu przywrócenia usługi: wymagane świadectwo odnowienia z PAWS. Ten cert zawierał podstawową nazwę domeny, [vdi.alaska.edu] (http: / / vdi.alaska.edu), ale zawierał również alternatywne nazwy\ (oba nazwy 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) Uzasadnienie Uzasadnienie Czas trwania przestoju i czas przywrócenia służby: Czwartek 23 lipca 16: 00 - piątek 24: 14. Uzasadnienie Uzasadnienie Uzasadnienie # Cel / Cel Uzasadnienie Oba UAG powinny stale prezentować ważne, zaufane certyfikaty oraz zewnętrzny i wewnętrzny dostęp VDI Uzasadnienie # Root Cause Analysis # Oba urządzenia UAG prezentowały przestarzałe certyfikaty TLS. TSS otrzymało listę urządzeń serwerowych VXrail, które oszacowały czas wygaśnięcia ich certyfikatów. Oba urządzenia UAG nie były na tej liście, więc nie byliśmy w stanie dyktować, kiedy ich certyfikaty wygasną. # Opracowanie środków zaradczych Stworzyłem arkusz głównego certyfikatu, który teraz zawiera zarówno informacje UAG certyfikatu, aby zawierać daty ważności. Dzielę się nim z naszym zespołem TSS, żebyśmy mogli w przyszłości monitorować spodziewane wypłaty certyfikatów. Wymagany dostęp do usługi Certinext dla przyszłych wznowienia certyfikatu. Uzasadnienie Harmonogram realizacji: Powyższe powinno umożliwić nam zwrócenie się o wydanie i wdrożenie certyfikatów przed ich wygaśnięciem w obu UAG przed ich wygaśnięciem. # Follow Up / Review Sprawdzić daty ważności certyfikatu na obu UAG poprzez monitorowanie arkusza głównego certyfikatu. Złóż wniosek do PAWS o odnowienie certyfikatu, zaplanowanie krótkiego wyłączenia CAB, zastosowanie certyfikatu zarówno do UAG, a następnie potwierdzić odnowienie został pomyślny i dostęp występuje
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
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!