Historia awarii Okta

1. 3 września 2026 10:42 UTCresolved

   Zespół inżynieryjny nadal bada problem błędu 500 w OP1. W tym czasie użytkownicy mogą doświadczać nieregularnych problemów w naszym systemie. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

2. 3 września 2026 11:02 UTCresolved

   Zespół inżynieryjny nadal bada problem błędu 500 w OP1. W tym czasie użytkownicy mogą doświadczać nieregularnych problemów w naszym systemie. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

3. 3 września 2026 11:34 UTCresolved

   Zespół inżynieryjny nadal bada problem błędu 500 w OP1. W tym czasie użytkownicy mogą doświadczać nieregularnych problemów w naszym systemie. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

4. 3 września 2026 12:00 UTCresolved

   Zespół inżynieryjny nadal bada problem błędu 500 w OP1. W tym czasie użytkownicy mogą doświadczać nieregularnych problemów w naszym systemie. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

5. 3 września 2026 12:30 UTCresolved

   Zespół inżynieryjny nadal bada problem błędu 500 w OP1. W tym czasie użytkownicy mogą doświadczać nieregularnych problemów w naszym systemie. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

6. 3 września 2026 13:03 UTCresolved

   Okta Engineering była w stanie podjąć niezbędne działania w celu złagodzenia tej kwestii i obecnie monitoruje stabilność. Przyczyna problemu i szczegóły podjętych działań zostaną zamieszczone na stronie Trust.

7. 3 września 2026 14:09 UTCresolved

   Po przedłużeniu okresu monitorowania potwierdziliśmy, że problem nie pojawił się ponownie. Analiza przyczyn źródłowych (RCA) zostanie tu zamieszczona w ciągu pięciu dni roboczych. Serdecznie przepraszamy za wpływ, jaki miało to na ciebie i twoich użytkowników.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 14 sierpnia 2026 15:23 UTCresolved

   Okta Engineering is investigating and has determined that the incident is currently impacting email delivery to a subset of customers. During this time, customers may experience email delivery deferrals. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

2. 14 sierpnia 2026 15:39 UTCresolved

   Okta Engineering has determined that certain third-party providers were failing to receive emails from Okta. Our monitoring shows delivery rates are recovering to normal conditions and will continue to monitor until full resolution. Our next update will be in 30 minutes or sooner if additional information becomes available.

3. 14 sierpnia 2026 16:50 UTCresolved

   Our monitoring indicates that email deferrals to the impacted third-party email service have returned to the expected baseline. Additional information will be available within 5 Business days.

4. 21 sierpnia 2026 16:04 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Okta detected an increase in customer support tickets regarding email delivery issues. Customers using custom email domains routed through Proofpoint experienced email delivery deferrals. During this period, affected end users were unable to receive system-generated emails, including One-Time Passwords (OTPs), account activation emails, password reset emails, factor enrollment emails, and other automated notifications. Root Cause Summary: Third-party provider Proofpoint experienced a service disruption, causing issues with email deliverability. When Okta services attempted to send emails to recipient domains whose MX records pointed to Proofpoint's infrastructure, the delivery attempts failed due to connection errors, resulting in deferred delivery. Okta's email sending infrastructure operated normally throughout the event. Remediation Steps: Okta Engineering monitored service telemetry and confirmed that email delivery returned to normal pre-incident baselines once Proofpoint restored stability to its infrastructure. Preventive Actions: Okta is defining automated alerting thresholds for email-bound and deferral rates to decrease detection time and updating runbooks to allow faster diagnosis of downstream provider disruptions. Timing: Incident start: August 14, 2026, at 5:00 AM PDT Incident resolved: August 14, 2026, at 10:04 AM PDT. Duration (# of minutes): 304 minutes Based on details provided by https://www.proofpoint.com/us/support-services

1. 24 lipca 2026 13:55 UTCresolved

   Po okresie stabilności i monitorowania możemy teraz potwierdzić, że kwestia usług została w pełni rozwiązana. Dodatkowe informacje przyczyny będą dostępne w ciągu pięciu dni roboczych.

2. 1 sierpnia 2026 03:28 UTCresolved

   Serdecznie przepraszamy za wpływ, jaki ten incydent spowodował dla ciebie, twojej firmy i twoich klientów. W Okcie naszym priorytetem jest zaufanie i przejrzystość. Poniżej przedstawiono fakty dotyczące tego incydentu. Jesteśmy zaangażowani we wdrażanie ulepszeń w zakresie naszych usług w celu zapobiegania przyszłym zdarzeniom. Detection and Impact On July 24, 2026, at approximately 3: 55 AM PDT, Okta observed service degradation for OK7, OK12, OK14 and OP3. Incydent miał szczególny wpływ na klientów korzystających z uprawnień AD / LDAP w zakresie uwierzytelniania i punktów końcowych OAuth w regionie AWS us- west- 2. Podczas całego wydarzenia użytkownicy napotkali błędy w dostępie do zasobów, błędy uwierzytelniania, timeout połączenia agenta, opóźnienia oraz żądania symbolu OAuth. Streszczenie przyczyny korzeniowej Przyczyna źródłowa powstała z błędów w ramach dostawcy usług w chmurze dla dotkniętego regionu. Etapy naprawy Dostawca usług w chmurze odzyskał łączność, a usługa Okta ustabilizowała się o około 4: 10 AM PDT, a nasze zespoły potwierdziły całkowity powrót do podstawowych operacji o 4: 19 AM PDT. Działania zapobiegawcze Okta aktywnie dokonują przeglądu i realizacji kilku inicjatyw mających na celu zapobieganie przyszłym zdarzeniom. Środki te obejmują: audyt i usprawnienie naszych procesów reagowania na incydenty w przypadku rozszerzonych kwestii w danym regionie oraz udoskonalenie monitorowania i ostrzegania w oparciu o ten incydent. Czas trwania całkowitego czasu trwania (protokół): 15 minut Czas rozpoczęcia: 3: 55 AM PDT Czas zakończenia: 4: 10 AM PDT Czas trwania (# minut): 15

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 22 lipca 2026 15:14 UTCresolved

   Informujemy, że nasza planowa konserwacja jest nadal w toku, a zespoły Okta Engineering są aktywnie zaangażowane. Podczas tego rozszerzonego okna klienci mogą doświadczać błędów podczas logowania do Okta Workflows. Dziękujemy za cierpliwość, ponieważ nasze zespoły pracują nad zakończeniem tej operacji tak szybko i bezpiecznie, jak to możliwe. & nbsp; Aby zrozumieć, w jaki sposób może to wpłynąć na organizację i aby zobaczyć zalecane pracownice, należy zapoznać się z naszym szczegółowym artykułem wsparcia: & nbsp; https: / / support.okta.com / help / s / article / okta- workflows- cell- migration- behaviors- and- workfarounds? language = en _ US. Będziemy dostarczać dalsze aktualizacje w ciągu 30 minut, lub wcześniej, jak więcej informacji staje się dostępna.

2. 22 lipca 2026 15:49 UTCresolved

   Trwają działania konserwacyjne, ponieważ zapewniamy bezpieczne i skuteczne zakończenie migracji. & nbsp; Będziemy nadal udostępniać aktualizacje w ciągu 30 minut lub wcześniej, jak staną się dostępne. W międzyczasie proszę zapoznać się z poniższym artykułem pomocniczym w celu uzyskania najnowszych wskazówek dotyczących działań i oczekiwanych zachowań: https: / / support.okta.com / help / s / article / okta- workflows- cell- migration- expected- behavors- and- workarounds? language = en _ US

3. 22 lipca 2026 16:19 UTCresolved

   Obserwujemy teraz stabilne wyniki systemu po działaniach migracyjnych. Nasze zespoły inżynieryjne są aktywnie zaangażowane w monitorowanie wszystkich usług. Podstawowe przepływy pracy wracają do normy, a klienci powinni być w dalszym ciągu ulepszeni. Dostarczymy naszą następną aktualizację w ciągu 30 minut, lub wcześniej, jeśli nowe informacje staną się dostępne.

4. 22 lipca 2026 16:59 UTCresolved

   Po okresie stabilności i monitorowania możemy teraz potwierdzić, że kwestia usług została w pełni rozwiązana. Dodatkowe informacje przyczyny będą dostępne w ciągu pięciu dni roboczych.

5. 29 lipca 2026 23:34 UTCresolved

   Serdecznie przepraszamy za wpływ, jaki ten incydent spowodował dla ciebie, twojej firmy i twoich klientów. W Okcie naszym priorytetem jest zaufanie i przejrzystość. Poniżej przedstawiono fakty dotyczące tego incydentu. Jesteśmy zaangażowani we wdrażanie ulepszeń w zakresie naszych usług w celu zapobiegania przyszłym zdarzeniom. Zdajemy sobie sprawę, że ta konserwacja wykroczyła poza pierwotnie przekazane okno i że nasze aktualizacje statusu podczas tego rozszerzenia nie informowały klientów w odpowiednim czasie. Przepraszamy za to; poprawa tego jest częścią naszych działań zapobiegawczych poniżej. Detection and Impact On July 22, 2026, at 5: 15 AM PDT, Okta Workflows in our North America region (FL1 cell) began experience issues that affected Workflows users over US Cells 1, 2, 3, 4, 6, 7 and 11. W tym czasie niektóre egzekucje przepływu pracy nie powiodły się lub zakończyły przedwcześnie, a użytkownicy napotkali błędy podczas wczytywania konsoli Workflows. Ponadto niektóre połączenia app przestały działać, wymagając od użytkowników ręcznej weryfikacji w celu przywrócenia funkcjonalności. Streszczenie przyczyny korzeniowej Problem wystąpił podczas planowanej aktualizacji systemu. Wada oprogramowania trzeciego sprzedawcy spowodowała, że aktualizacja przebiegała znacznie dłużej niż oczekiwano. Podczas migracji do nowego systemu danych awaria komunikacji pomiędzy elementami systemu uniemożliwiła powrót usługi do normalnego stanu w oczekiwanym oknie. W tym okresie Konsola Workflows nie ulegała degradacji z wdziękiem, gdy bazowy magazyn danych był niedostępny; zamiast tego ujawniła błędy bezpośrednio użytkownikom. Ponadto połączenia app, których referencje nie mogły być odświeżone podczas zakłóceń, pozostawały w nieudanym stanie i nie były automatycznie odświeżane, dlatego niektóre błędy trwały po zakończeniu aktualizacji, do czasu ponownego autoryzacji połączenia. Etapy naprawy Sprzedawca trzeciej partii potwierdził, że klaster ustabilizował się o 8: 34. Po ustabilizowaniu, Okta Engineering odzyskał dotknięte usługi, aby usunąć obudowy z konfiguracji. Klienci, którzy doświadczyli błędów odświeżania tokena OAuth w tym okresie byli zobowiązani do ręcznego ponownego autoryzacji połączeń aplikacji. Pełna funkcjonalność została przywrócona do 9: 33 AM PDT. Jeśli jesteś nadal dotknięty: ręcznie autoryzować dane dotyczące połączeń w konsoli Workflows (patrz KB: Okta Workflows: Cell Migration Expected Behaviors and Workarounds). Egzekucje Workflow, które nie powiodły się podczas okna, mogą być ponownie uruchomione przy użyciu normalnego procesu; skontaktuj się z Okta Support, jeśli chcesz pomóc zidentyfikować dotknięte egzekucje. Działania zapobiegawcze Aby zapobiec podobnym incydentom, Okta podjęła następujące kroki. Wprowadziliśmy w życie kontrolę nad wszystkimi kolejnymi migracjami silników, aż do momentu, gdy nasz trzeci sprzedawca wdroży naprawę potwierdzonej wady i potwierdzi, że jest bezpieczny. Aktualizujemy również Konsolę Workflows, aby szybko się nie powiodła i automatycznie odzyskiwać, gdy infrastruktura jest tymczasowo niedostępna, zapewniając użytkownikom możliwość ponownego podłączenia się do systemu zamiast błędów systemu surowego. Równolegle dodajemy bezpośredni zautomatyzowany monitoring i ostrzeżenie o niepowodzeniach konwergencji, aby zapewnić szybsze wykrywanie podczas konserwacji okien. Wreszcie, poprawiamy sposób komunikacji podczas konserwacji, która trwa długo, w tym bardziej terminowa strona statusu i postęp / aktualizacje zakończenia. W przypadku pytań dotyczących niezawodności Workflows lub planu działania, Twój zespół Kont Okta może pomóc. Czas trwania całkowitego czasu trwania (protokół): 258 minut (4 godziny i 18 minut) Czas rozpoczęcia: 5: 15 PDT AM Czas zakończenia: 9: 33 PDT Czas trwania (# minut): 258 minut

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 13 lipca 2026 21:23 UTCresolved

   Nasz zespół inżynieryjny zastosował potencjalne rozwiązanie do wpływającego środowiska podglądu i aktywnie monitoruje system odzyskiwania. Dostarczymy kolejną aktualizację w ciągu 30 minut, lub wcześniej, jeśli nowe informacje staną się dostępne. Przepraszamy za wszelkie niedogodności.

2. 13 lipca 2026 21:39 UTCresolved

   Nasz zespół inżynieryjny zastosował rozwiązanie, a my obserwujemy odbudowę naszego podglądu OP2. Dokładnie monitorujemy system i dostarczymy kolejną aktualizację w ciągu 30 minut.

3. 13 lipca 2026 21:53 UTCresolved

   Potwierdziliśmy, że środowisko podglądu OP2 w pełni się ustabilizowało, a wcześniejszy problem jest całkowicie rozwiązany. Dodatkowe informacje przyczyny będą dostępne w ciągu pięciu dni roboczych.

4. 21 lipca 2026 01:57 UTCresolved

   Serdecznie przepraszamy za wpływ, jaki ten incydent spowodował dla ciebie, twojej firmy i twoich klientów. W Okcie naszym priorytetem jest zaufanie i przejrzystość. Poniżej przedstawiono fakty dotyczące tego incydentu. Jesteśmy zaangażowani we wdrażanie ulepszeń w służbie, aby zapobiec przyszłym zdarzeniom tego incydentu. Detection and Impact: 13 lipca 2026 r. o godzinie 1: 01 PM PT, wewnętrzny monitoring Okta zaalarmował nasz zespół o zwiększonych błędach w środowisku Cell Preview EMEA. W tym okresie wpłynęli na to wszyscy klienci z EMEA Preview Cell. Administratorzy i użytkownicy końcowi mogli napotkać komunikaty "Błąd serwera wewnętrznego" i inne błędy podczas próby zalogowania się lub uzyskania dostępu do usług Okta. Podsumowanie przyczyny korzeniowej: Incydent został uruchomiony podczas aktualizacji usługi. Nieprawidłowa konfiguracja spowodowała, że klaster Komórki Podglądu EMEA przypadkowo otrzymał nieprawidłową wersję kluczowego elementu routingu infrastruktury. Aktualizacja ta przerwała wewnętrzną sieć połączeń, co uniemożliwiło komunikację między innymi zdrowymi komponentami infrastruktury. Ponieważ wnioski nie mogły dotrzeć do aplikacji podstawowej, doprowadziło to do szeroko zakrojonych błędów serwisowych i błędów uwierzytelniania. Etapy naprawy: Zespół inżynieryjny Okty zidentyfikował problem i natychmiast rozpoczął wdrażanie poprzedniej, stabilnej wersji konfiguracji routingu. Po wycofaniu, inżynierowie systematycznie wznowili usługi (w tym bramy i proxy), aby przywrócić łączność wewnętrzną. Działania te pomyślnie zajęły się tą kwestią, a wpływ na klientów został w pełni złagodzony o godz. 14.20 PT. Działania zapobiegawcze: udoskonalamy nasze procesy operacyjne w celu zwiększenia stabilności usług. Obejmuje to bieżące prace nad poprawą możliwości automatycznego wykrywania i monitorowania, pomagając nam lepiej zidentyfikować i rozwiązać potencjalne problemy. Całkowity czas trwania (protokół): 79 minut (1 godzina 19 minut) Czas rozpoczęcia: 1: 01 PM PT Czas zakończenia: 2: 20 PM PT

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 lipca 2026 20:50 UTCresolved

   Inżynieria Okta zidentyfikowała problem mający wpływ na przepływy pracy Okta i obecnie podejmuje kroki w celu naprawy. Klienci mogą zobaczyć 500 błędów lub przerw czasowych w konsoli Okta Workflows, punktach końcowych API i przychodzących hakach internetowych. Dostarczymy kolejną aktualizację w ciągu najbliższych 30 minut, lub wcześniej, jeśli dodatkowe informacje staną się dostępne.

2. 7 lipca 2026 21:03 UTCresolved

   Problem z Okta Workflows został rozwiązany. Wszystkie Workflows są teraz przetwarzane normalnie. Analiza przyczyn źródłowych (RCA) zostanie tu zamieszczona w ciągu pięciu dni roboczych. Przepraszamy za wszelkie niedogodności.

3. 15 lipca 2026 15:22 UTCresolved

   Serdecznie przepraszamy za wpływ, jaki ten incydent mógł wywrzeć na pana, pana firmę lub pana klientów. W Okcie naszym priorytetem jest zaufanie i przejrzystość. Poniżej przedstawiono fakty dotyczące tego incydentu. Jesteśmy zaangażowani we wdrażanie ulepszeń w służbie, aby zapobiec przyszłym zdarzeniom tego incydentu. Detection and Impact: 7 lipca 2026 r., o godzinie 1: 01 PM PDT, wewnętrzne monitorowanie i raporty klientów w Okcie ostrzegały nasz zespół o problemach związanych z dostępem użytkowników do Workflow na OK14 komórki Okta w Ameryce Północnej. W tym okresie klienci na FL14 mogli doświadczyć błędów HTTP 500, 503 lub 504 Gateway Timeout podczas nawigacji do Workflows z portalu admin lub próby zalogowania się do Konsoli Workflows za pośrednictwem SSO. Istniejące sesje mogły być przerywane. Zaplanowane i na żądanie przepływy pracy, haki inline i haki webhacks mogą wystąpić błędy i timeout. Dodatkowo, w czasie wykonywania operacji w locie doszło do przerw czasowych. Podsumowanie przyczyn korzeniowych: Zdarzenie to miało miejsce podczas planowanego wprowadzenia do komórki FL14 wersji 2027.07.0. W trakcie procesu rozmieszczania jednostka usługowa odpowiedzialna za wykonywanie aktualizacji schematów została przedwcześnie zakończona. To wcześniejsze zakończenie doprowadziło do niespodziewanych, długotrwałych połączeń z bazą danych, co ostatecznie spowodowało wyczerpanie połączeń w podstawowej bazie danych komórki. Etapy naprawy: Po otrzymaniu ostrzeżeń i raportów klientów zespół rozpoczął diagnostykę o 12: 44 PM PDT. Do 1: 30 PM PDT, wyizolowali i usunęli kapsułę serwisową wykonującą aktualizacje schematów. Pozwoliło to na oczyszczenie połączeń z bazą danych i przywrócenie pełnej obsługi do 1: 45 PM PDT. Działania zapobiegawcze: Aby zapobiec przyszłym zdarzeniom, Okta jest zaangażowana w wzmocnienie naszej stabilności infrastruktury i zwiększenie naszych możliwości monitorowania. Obecnie wdrażamy strategiczne ulepszenia naszych procesów wdrożeniowych i alarmujemy systemy, aby zapewnić szybsze wykrywanie, reagowanie i większą odporność w naszych usługach. Całkowity czas trwania: 67 minut

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 26 czerwca 2026 15:22 UTCresolved

   Our Engineering team has identified the issue, and we will continue monitoring the issue. We will provide another update within the next 15 minutes, or sooner if additional information becomes available.

2. 29 czerwca 2026 23:50 UTCresolved

3. 30 czerwca 2026 15:01 UTCresolved

   The Root Cause Analysis (RCA) details previously posted in this update were published in error and belonged to a separate incident that occurred on June 22nd (I-10858). We sincerely apologize for any confusion this may have caused. Our formal RCA process for this OK11 custom domains incident (I-10874) is still actively underway. We remain committed to transparency and will provide an accurate, dedicated RCA for this disruption within 5 business days (expected late July 6, 2026). Thank you for your patience.

4. 6 lipca 2026 22:01 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On June 26th at 7:43 AM (PT), Okta was alerted to customer reports of connection issues and authentication failures when accessing custom domains. The incident was isolated to OK11 and normal connectivity was restored at 7:53 AM (PT). Root Cause Summary: Okta Engineering identified that the root cause of the issue originated during a custom domain traffic migration in OK11 on June 25th at 10:47 AM (PT), the new routing infrastructure became resource-constrained under increased traffic volume the next day. This resulted in TCP connection resets and errors sent to clients attempting to access custom domains. Remediation Steps: Once the source of the issue was identified, Okta engineering immediately mitigated the issue by reverting custom domain traffic back to the previous infrastructure, restoring normal connectivity within minutes. Preventative Actions: To prevent future incidents, the routing infrastructure was scaled to prevent recurrence. Okta will work to implement enhanced monitoring and alerting, as well as updated auto-scaling policies to ensure routing infrastructure maintains adequate capacity during traffic fluctuations and future infrastructure improvements. Duration (# of minutes): Total Duration (Minutes): 53 minutes Actual Time: 7:00 AM - 7:53 AM PT

1. 22 czerwca 2026 22:02 UTCresolved

   The Okta Engineering team has taken steps to mitigate the issue. We have observed that the errors have been reduced and is continuing to subside. We are monitoring the situation closely and will provide further updates in 15-30 minutes as we move toward full mitigation.

2. 22 czerwca 2026 22:33 UTCresolved

   Internal monitoring confirmed that the EU1 environment has fully recovered and is operating normally. A full Root Cause Analysis (RCA) will be made available within 5 business days. We apologize for any disruption this may have caused.

3. 30 czerwca 2026 14:43 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On June 22nd, 2026, at 2:08 PM PDT, Okta internal monitoring alerted our team to errors in the EU environment. During this period, administrators and end users may have experienced intermittent 500 Internal Server Error and 429 Rate Limit responses when attempting to access Okta services. Root Cause Summary: The incident was triggered by an unexpected scaling down of the application cluster during scheduled maintenance of the environment. This change accidentally overwrote the custom capacity settings for several of our applications. This caused the system to automatically revert to its lowest default capacity, drastically reducing the amount of user traffic it could handle simultaneously. As a result, the remaining servers were immediately overwhelmed by the normal volume of user requests, leading to system slowdowns, errors, and "too many requests" blockages for our customers in the impacted cell. Remediation Steps: Okta's engineering team identified the root cause issue at 2:44 PM PDT. The team mitigated the issue by scaling up resource capacity, completely stabilizing service health back to normal levels by 2:48 PM PDT. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: - Strengthen guardrails by improving our validation tools and multi-environment review processes to automatically detect and flag unexpected server capacity changes before they're applied. - Accelerate system monitoring by implementing enhanced monitoring thresholds to instantly detect and report infrastructure capacity drops before they can impact end users. - Optimize failover protocols by auditing critical alert paths for maximum reliability while establishing a clear, structured communication plan for when automated backup systems are triggered. These learnings work to prevent similar incidents from happening again. Duration (# of minutes):40 minutes

1. 2 czerwca 2026 11:21 UTCresolved

   Engineering is still investigating the issue, recent actions that were taken show errors subsiding.

2. 2 czerwca 2026 11:40 UTCresolved

   The Okta Engineering team has observed that the errors have been reduced. We are monitoring the situation closely and will provide further updates as we move toward full mitigation.

3. 2 czerwca 2026 12:07 UTCresolved

   Okta Engineering has confirmed that the issue has been resolved. An RCA will be provided in five business days. We apologize for any inconvenience this may have caused.

4. 10 czerwca 2026 02:19 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On June 2nd, 2026, at 2:36 AM PT, Okta internal monitoring alerted our team to elevated errors in the OK9 environment. During this period, administrators and end users may have experienced intermittent 500 Internal Server errors when trying to access Okta services. Additionally, Admins may have encountered error messages when fetching certain records. Root Cause Summary: The incident was triggered by a misconfiguration introduced during a scheduled maintenance of the environment. This maintenance introduced an error that caused connectivity issues within specific infrastructure components. Only a small percentage of the infrastructure was affected during this period. Remediation Steps: Okta's engineering team identified and isolated impacted infrastructure at 4:01AM PT. These actions successfully addressed the issue, and normal operations were restored by 4:17 AM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: Incident response processes, procedures, and investigation tools to more rapidly diagnose similar issues in the future. Risk evaluation processes to include expanding error types and adding additional appropriate corresponding alerts and monitoring associated with vulnerability updates. These learnings work to prevent similar incidents from happening again and, in cases like these, allow Okta to respond faster when possible. Duration (# of minutes): 100

1. 1 maja 2026 00:28 UTCresolved

   The Okta Engineering team has successfully resolved the service instability that was causing system timeouts. Okta engineering has confirmed that errors have subsided, and we have transitioned into a monitoring phase to ensure continued stability. We sincerely appreciate your patience while our team worked to identify and resolve the issue.

2. 1 maja 2026 01:01 UTCresolved

   Internal monitoring confirmed that the OP1 environment has fully recovered and is operating normally. A full Root Cause Analysis (RCA) will be made available within 5 days. We apologize for any disruption this may have caused.

3. 8 maja 2026 02:51 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On April 30th, 2026, at 10:57 AM PT, Okta internal monitoring alerted our team of login issues for users accessing Okta Preview Cell 1. During this period, customers may have received 500 errors for query timeouts and were unable to log in. Root Cause Summary: The incident stemmed from a database query change. The updated query intermittently exceeded its timeout limit across several login endpoints. Consequently, users experienced 500 errors and were unable to log in. Remediation Steps: Upon receiving the alerts, Okta Engineering immediately launched an investigation. By 1:02 PM PT, the team took initial mitigation steps to resolve the issue, however these steps did not resolve the issue. The incident response team continued to triage and diagnose the issue and identified the root cause related to the updated database query change at 4:50 PM PT. The team reverted the new query behavior at 5:00 PM PT in Preview Cell 1, and full service functionality was restored by 5:05 PM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta is currently reviewing the following: -Reviewing incident response processes and investigation tools to more rapidly diagnose similar issues in the future -Risk evaluation processes associated with query updates -Alerts and monitors associated with the database proxy These learnings work to prevent similar incidents from happening again and, in cases like these, allow Okta to respond faster when possible. Duration (# of minutes): 375

1. 29 kwietnia 2026 22:42 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Customers using the third-party service Kolide began reporting that attempts to sign in to their orgs redirected to an unrelated tenant and received an HTTP 400 error with the message “Login Failed - 400: Bad Request Error Code: GENERAL_NONSUCCESS” Root Cause Summary: Kolide has confirmed for Okta that an incident occurred with their Device Trust SAML authentication system, resulting in some users being redirected to an incorrect service provider after completing authentication. This resulted in users receiving a 400 error. Kolide reported that users were unable to access their intended application, any unauthorized applications, or any unauthorized environments. Remediation Steps: Okta Support advised customers that they could temporarily disable their Kolide integrations to allow their users to successfully access their services. Timing: Kolide reports: Incident start: April 22, 2026, at 8:24 AM PDT Incident resolved: April 22, 2026, at 8:30 AM PDT Duration (# of minutes): 6 Minutes

1. 13 kwietnia 2026 20:33 UTCresolved

   Okta has identified the issue impacting Access Request job processing and Engineering Teams are working to restore the service. We are rolling out the fix for this issue in 30 minutes and will provide another update once the fix is rolled out.

2. 13 kwietnia 2026 20:59 UTCresolved

   Okta has identified the root cause of the issue affecting Access Request job processing as of 1:00 PM PT. A resolution was implemented at 1:45 PM PT, and the service is now fully operational for new submissions. The engineering team is currently working to restore and process any requests submitted during the disruption period. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

3. 13 kwietnia 2026 21:29 UTCresolved

   While new Access Request job processing has been restored, Okta is also working to resolve the issue affecting in-flight Access Request job requests processed during the disruption period.  The fix for this issue is expected to be implemented around 5:00pm PT.  Okta will provide another update at 5:00pm PT or sooner if one becomes available.

4. 14 kwietnia 2026 00:25 UTCresolved

   The issue with in-flight Access Request job requests processed during the disruption period has also been resolved. All Access Request jobs are now processing normally. A root cause analysis (RCA) will be posted here within five business days. We apologize for any inconvenience this may have caused.

5. 21 kwietnia 2026 23:16 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this kind. Detection and Impact: On April 13, 2026, at 11:51 AM PST, an incident was reported where Okta Identity Governance (OIG) access requests stalled in the "In Progress" state indefinitely across all environments. The system accepted initial submissions and first-level approvals, but failed to trigger subsequent automated tasks like assigning users to apps/groups or running delegated workflows. . Root Cause Summary: During a recent update deployment, new tasks inadvertently moved to a 'LOCKED' status without implementing the necessary logic to transition them back to 'OPEN.' This caused the tasks to become permanently hidden, preventing the automated execution of the action associated with them. Remediation Steps: Okta's engineering teams promptly responded, initiating immediate detection and diagnosis. Corrective measures, including a code fix deployed to all cells, were implemented to prevent any new access requests from becoming stuck. A remediation migration successfully transitioned most affected requests to a fixed state. Normal functionality was fully restored by April 13, 2026, at 5:18 PM PST, following the completion of a final migration to unblock remaining requests.On April 14, 2026, Okta took further steps to resolve in-flight requests that were stuck, moving them to a final, terminal state. Preventative Actions: Okta is taking several steps to prevent this issue from recurring. These include enhanced testing, deployment of safeguards, and improvements to our monitoring and alerting systems. Duration (# of minutes): 434

1. 24 marca 2026 23:32 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. We are committed to implementing improvements to the service to prevent similar occurrences. Detection and Impact: Okta internal monitoring alerted our engineering team to disruptions to the Okta status page and the commercial support portal. Okta Engineering identified a service disruption with our third-party provider and confirmed the impact. During the disruption, customer admins were unable to access the Okta Support Center (support.okta.com) to log support cases or view the primary status page (status.okta.com). Root Cause Summary: Okta's third-party provider, responsible for hosting the Okta Support Center and status page, experienced a service disruption. The third-party provider identified a version mismatch between their application and database layers as the technical trigger. This mismatch resulted in internal server errors and login failures, rendering the Okta Support Center and status page inaccessible for a portion of their disruption. Remediation Steps: Okta teams posted an admin banner within the Okta Admin Console to provide visibility into the disruption and offer a phone number for customers who needed to log support cases manually while the Okta Support Center was unavailable. Services were fully restored after the third-party provider successfully deployed a fix-forward release to the impacted infrastructure, which restored login access. Preventive Actions: As part of Okta's commitment to operational resilience, we have optimized our vendor engagement matrix to accelerate incident mitigation and downstream coordination. We are also conducting an expanded audit of external dependencies to formalize alternative response procedures within our disaster recovery plans. Simultaneously, Engineering has enhanced real-time monitoring and alerting for service endpoints, enabling faster detection and resolution. Timing: Incident start: March 16, 2026, at 08:58 PM PDT Incident resolved: March 16, 2026, at 11:34 PM PDT Duration (# of minutes): 156 minutes

1. 13 marca 2026 18:48 UTCresolved

   At around 11:20AM PT, Okta Engineering has confirmed that the issue has been resolved in both cells, EU1 and OK1. An RCA will be provided in five business days. We apologize for any inconvenience this may have caused.

2. 20 marca 2026 20:35 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this kind. Detection and Impact On March 13, 2026, at 10:49 AM PT, Okta detected a service degradation that prevented some customers on the OK1 and EU1 cells from performing directory operations, viewing or searching for users, groups, and devices in the Okta Admin Console. Customers may have experienced "Invalid search query" messages or 5xx errors. This issue also affected several API endpoints related to users, groups, and devices, which may have impacted customer integrations relying on this functionality. End-user authentication was not impacted. Root Cause Summary The root cause of this incident was a planned configuration change that exposed a bug in the underlying service, resulting in system errors and disrupting both directory-based APIs. Remediation Steps Upon detection, Okta's engineering teams initiated incident response procedures. Once the problematic configuration change was identified as the source of the errors, it was immediately reverted. After the reversion was applied and verified, full functionality was restored to all impacted customers. Preventative Actions Okta is taking steps to prevent future occurrences of this kind, including enhancing our testing processes, hardening and improving our configuration rollout strategy, and upgrading our monitoring and alerting systems for enhanced detection. Start Time: 03/13/2026 10:17 AM PT End Time: 03/13/2026 11:21 AM PT Duration (# of minutes): 64

1. 4 lutego 2026 12:37 UTCresolved

   Okta has implemented a fix for the LDAP issue affecting the OK9 environment. We are observing signs of service recovery and confirmed improvements from customers. We will continue to monitor the situation closely to ensure full resolution. We are monitoring the situation closely and will provide further updates within the next 30 minutes.

2. 4 lutego 2026 12:50 UTCresolved

   This incident has been resolved. Internal monitoring and customer reports confirm that the LDAPi system in OK9 has fully recovered and is operating normally. We will continue to closely monitor the service to ensure stability. A full Root Cause Analysis (RCA) will be made available within 5 days. We apologize for any disruption this may have caused.

3. 11 lutego 2026 18:45 UTCresolved

   On February 4th, 2026, at 3:33 AM PT, Okta received customer reports of authentication failures within the OK9 (EMEA) cell. Customers attempting to access LDAP interface services encountered certificate validation errors related to hostname mismatches, preventing successful authentication. Root Cause Summary: The incident was triggered by a misconfiguration introduced during a scheduled update of our LDAP interface to a new configuration source on February 4th 2:24 AM PT. This update inadvertently applied an incorrect SSL certificate profile to the LDAP interface within the OK9 environment. This misconfiguration caused certificate validity errors, resulting in connection issues when attempting to use LDAP services. Remediation Steps: Once the source of the issue was identified, Okta engineering team rolled back changes at 4:07 AM PT. These actions successfully addressed the issue and restored normal operations by 4:26 AM PT. Preventative Actions: To prevent future incidents, Okta has updated synthetic tests and enhanced monitoring. Teams also plan to add new tooling to improve changes to the LDAP service certificates. In addition, we are reviewing our internal processes and procedures, refining our automated rollback processes to further reduce the customer impact time for similar issues in the future. Duration (# of minutes): Total Duration (Minutes): 122 minutes Actual Time: 02:24 AM PT - 04:26 AM PT

1. 28 stycznia 2026 19:24 UTCresolved

   We are seeing significant and steady system stability as our third-party provider recovery continues in the EU-West-1 region. We will continue monitoring the service to ensure a full recovery. We will provide another update in 60 minutes or as soon as more information becomes available.

2. 28 stycznia 2026 19:36 UTCresolved

   The third-party provider has confirmed that the issue has been resolved. A root cause analysis (RCA) will be posted here within five business days.

3. 5 lutego 2026 01:26 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On January 29th, 2026, at 8:28 AM PT, Okta internal monitoring alerted our team of intermittent connectivity issues accessing Okta Cell 9 (EMEA). During this period, customers may have experienced intermittent errors establishing network connections and latency when trying to access Okta services. Clients configured to retry failed connections likely saw successful connectivity on secondary attempts. Root Cause Summary: The incident stemmed from a failure of a component that manages configuration changes to the networking infrastructure with our Cloud Service Provider (CSP) in the region hosting Okta Cell 9. Remediation Steps: Immediately upon receiving the alerts, Okta Engineering began investigating several isolated spikes but determined that cell health was stable. At 9:35 AM PT, Okta Engineering received more alerts and immediately initiated incident response procedures. At 9:51 AM PT, Okta Engineering began working with the CSP to diagnose the issue. At 10:13 AM PT, the latency began to stabilize. At 11:22 AM PT, the issue was resolved. Preventative Actions: To prevent similar incidents from recurring, Okta Engineering is improving our monitoring, working with our CSP to enhance their monitoring, and reviewing incident response processes associated with this event. Duration (# of minutes): 186

4. 11 lutego 2026 18:40 UTCresolved

1. 22 stycznia 2026 21:46 UTCresolved

   We are continuing to monitor the third-party email service provider's progress toward a resolution. At this time, we have not received an estimated time for recovery (ETR). If you are attempting to sign in and have configured alternative MFA factors (such as Okta Verify, SMS, or Security Keys/Biometrics), we recommend using those options to avoid delays associated with email delivery. Our engineering teams remain on standby to verify service restoration the moment it begins. We will continue to provide updates as soon as the impacted provider shares new information.

2. 22 stycznia 2026 23:24 UTCresolved

   We're continuing to track the ongoing service disruption with the third-party email provider. We appreciate your patience while we await the provider's resolution of the root cause. We'll post our next update in 90 minutes or as soon as we have a significant change in status.

3. 23 stycznia 2026 00:46 UTCresolved

   The third-party email provider has identified the root cause as a service infrastructure issue within the North America region. They are currently implementing load-balancing configurations to stabilize the environment. While recovery is underway, users may continue to experience intermittent delays or failures in receiving emails. We are monitoring the provider's progress and will provide another update as they move toward full resolution.

4. 23 stycznia 2026 03:55 UTCresolved

   The third-party provider continues to see improvements across their impacted North American infrastructure. While our internal systems remain healthy, our team is on standby to validate the restoration of all external dependencies. We will provide a final update once the provider confirms that their services have fully returned to normal operations.

5. 23 stycznia 2026 06:46 UTCresolved

   The third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.

6. 30 stycznia 2026 22:34 UTCresolved

   Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service Timing: Incident start: January 22, 2026, at 10:55 AM PST Incident resolved: January 22, 202,6 at 7:50 PM PST Detection: The issue was initially identified through customer reports that they were not receiving expected email notifications. Okta Engineering confirmed the service disruption after internal monitoring indicated a high volume of deferred email delivery attempts to specific third-party domains. Impact: Customers across all Okta cells with email addresses hosted by Microsoft Exchange Online may have experienced intermittent delays or failures in receiving automated email notifications, such as Multi-Factor Authentication (MFA) codes and enrollment links. Okta services remained healthy and attempted to resend deferred messages. Root Cause: Microsoft reports that it experienced a service issue within its North American data centers during a planned maintenance activity. As a result, emails sent from Okta to the affected provider resulted in “soft bounce” errors, indicating that the provider's servers were temporarily unable to accept the messages. Remediation Steps: To mitigate the impact on users attempting to sign in, Okta recommended using alternative MFA factors, such as Okta Verify, security keys, or SMS, to bypass delays associated with email delivery. Okta Engineering continuously monitored the third-party provider's recovery efforts and validated that mail delivery returned to baseline levels once the provider stabilized their environment.

1. 20 stycznia 2026 16:04 UTCresolved

   We've identified that the service interruption is due to an issue with a third-party provider. We are actively working with the provider to ensure a swift resolution and are closely monitoring progress. We will provide further updates as more information becomes available.

2. 20 stycznia 2026 16:35 UTCresolved

   We are continuing to monitor progress with our third-party provider. The provider is currently implementing mitigation steps, and we are seeing signs of recovery. Several customers have already confirmed that service has been restored on their end. We are working to ensure this resolution is consistent across all accounts. We will provide the next updates within 30 minutes, or sooner if additional information becomes available.

3. 20 stycznia 2026 17:10 UTCresolved

   Our third-party provider is continuing their recovery efforts. While we are no longer seeing active errors, we remain in a period of close monitoring as they work toward a final resolution. We recognize that some users may still experience residual effects; our Support teams are working with them to resolve these errors. Our next update will be in 60 minutes or sooner if additional information becomes available.

4. 20 stycznia 2026 17:21 UTCresolved

   Our third-party provider has confirmed that a fix has been successfully deployed. A root cause analysis (RCA) will be posted here within ten business days. We sincerely apologize for the impact this had on you and your users.

5. 26 stycznia 2026 18:31 UTCresolved

   Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. Timing: Incident start: January 19, 2026, at 10:10 AM PST Incident resolved: January 20, 2026, at 11:49 AM PST Detection: Okta teams were notified via customer cases and an increase in Google Workspace import errors. Impact: Any customers performing Google Workspace imports during the incident window may have encountered an error stating “UserImportJob: Failed to download users. Json field=primaryEmail does not exist for object=[...]” Root Cause: Google Workspaces, a third-party provider, confirmed that a faulty code change introduced caused certain fields, such as primary email addresses, to be missing in API call results. As a result, Okta imports from Google Workspace could not complete, leading to import failures. Google provides additional details for this disruption: https://www.google.com/appsstatus/dashboard/incidents/9q5n4sfDnxYzHj8FxEua Remediation Steps: Okta teams soon identified that a provider-side disruption was the cause of the incident and opened a formal support case to track the resolution. The third-party provider resolved the incident by rolling back a faulty code change and restoring the missing metadata. Recovery occurred in stages, with some customers successfully remediated before others. Okta teams monitored the recovery in real-time and confirmed successful import signals across multiple impacted customers before standing down.

1. 3 stycznia 2026 01:52 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this kind. Detection and Impact: On December 26, 2025, at 3:27 AM PST, Okta engineering was alerted to increased errors in US Cell 6. During this time, US Cell 6 experienced errors, connection timeouts, and slow responses while attempting to access resources. Admins would have seen a banner on the admin portal stating that the cell was in read-only mode. Root Cause Summary: Okta has determined that the issue was caused by an outage with our cloud service provider. All instances fully recovered by 5:43 AM PT. Remediation Steps: Upon detection, Okta's engineering teams immediately began diagnosing the issue and worked with our cloud service provider to resolve the issue. In addition, the Incident response teams continued to review and analyze the incident, applying additional measures to improve service availability for end-user authentications. Preventative Actions: Okta is taking steps to prevent a recurrence of this issue. We are making improvements to our monitoring and response procedures to more quickly diagnose and recover from this kind of failure in the future. Total Duration: 2 hours and 16 minutes Start Time: December 26, 2025, 03:27 AM PT End Time: December 26, 2025, 05:43 AM PT

1. 14 grudnia 2025 16:40 UTCresolved

   The Okta Engineering team is continuing to work with our third-party vendor and addressing this issue with urgency related to the custom domain email delivery issues.

2. 14 grudnia 2025 16:42 UTCresolved

   The next update will be posted in the next 60 minutes.

3. 14 grudnia 2025 17:50 UTCresolved

   Our Engineering team is continuing to work with the third-party provider on mitigation actions to help resolve this outstanding issue. We are treating the issue with the utmost urgency to restore our services as soon as possible. The next update will be provided within the next 60 minutes or sooner, if additional information becomes available.

4. 14 grudnia 2025 18:48 UTCresolved

   We have identified a potential root cause of this issue, and are currently investigating next steps towards resolution. We will provide the next update in 60 minutes, unless new information becomes available.

5. 14 grudnia 2025 19:39 UTCresolved

   This issue has been successfully resolved as of 11:07AM PDT. All services have been restored. If you continue to see issues, please update your support case for assistance. Additional root cause information will be available within 5 Business days.

6. 23 grudnia 2025 14:49 UTCresolved

   We sincerely apologize for any impact this incident has caused to you, your business, or your customers. At Okta, trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent similar future occurrences. Detection and Impact: On December 14, 2025, at 3:01 a.m. PST, Okta detected an issue that prevented email delivery for customers using custom email domains. This affected end-users' ability to receive emails for Multi-Factor Authentication (MFA), password resets, registration activation, account lockout notifications, and other notification emails, such as rate-limit notifications for administrators. Root Cause Summary: Okta has determined that the issue was caused by an unintended configuration change on our Mail Transfer Agents (MTAs). This change incorrectly routed emails from custom domains without proper DMARC sender authentication. As a result, email service providers rejected the emails, causing the delivery failures. Remediation Steps: Upon detection, Okta's engineering teams immediately began diagnosing the delivery failures. After identifying the incorrect routing, we updated the configuration to ensure emails were sent through the appropriate authenticated channels. Normal email functionality was fully restored after the updated configuration was applied. Preventative Actions: Okta is taking several steps to prevent a recurrence of this issue. We are enhancing our monitoring and alerting for email services and improving our configuration management tools to add further safeguards. Duration (# of minutes):1140