Okta driftsforstyrrelser

1. 15. september 2026 kl. 16.22 UTCupdate

   Okta Engineering teams arbejder aktivt på en løsning og koordinere med serviceleverandøren for at genoprette direkte flise funktionalitet. Vi vil give en opdatering om 30 minutter, eller før, som yderligere oplysninger bliver tilgængelige.

2. 15. september 2026 kl. 16.54 UTCupdate

   Vi fortsætter med at arbejde direkte med vores tredjeparts serviceudbyder til fejlfinding og løse de intermitterende HTTP 401 omdirigere fejl, der påvirker Office 365 applikationer. Vi vil give en anden opdatering, så snart nye oplysninger er tilgængelige.

3. 15. september 2026 kl. 18.30 UTCupdate

   Aktiv fejlfinding med vores leverandør forbliver en høj prioritet eskalering på tværs af begge ingeniørhold. Mens grundlæggende beslutsomhed stadig er i gang, forstår vi den operationelle virkning og fokuserer fuldt ud på at få dette til at gå i opløsning. Vores næste opdatering vil blive bogført, så snart nye oplysninger er tilgængelige.

4. 15. september 2026 kl. 23.02 UTCupdate

   Vores tredjeparts leverandør har identificeret den grundlæggende årsag, der er periodisk påvirke Microsoft 365-tjenester og er i øjeblikket ved at implementere en rettelse. Indsættelsen er i gang fra den 15. september 2026, selvom fuldstændig formering på tværs af alle brugerkonti forventes at tage omkring 48 timer at løse problemet fuldt ud. Vi er aktivt at overvåge udrulningen fremskridt og vil give yderligere opdateringer, når nye detaljer bliver tilgængelige. Yderligere root årsag oplysninger vil være tilgængelige, når sælgeren har afsluttet udrulningen af fix og valideret fuld opløsning.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. september 2026 kl. 12.50 UTCresolved

   Engineering har identificeret problemet og taget oprydning skridt til at afbøde problemet. Forbindelse til brugerdefinerede domæner er blevet genoprettet og tjenesten er vendt tilbage til normal. Otta vil fortsætte med at overvåge.

2. 11. september 2026 kl. 13.10 UTCresolved

   Okta har opklaret OK9 konnektivitet spørgsmål. Forbindelsesfejl holdt fra 5: 00 AM PDT til 5: 36 AM PDT. Vi vil fortsætte med at overvåge og producere en RCA i 5 hverdage.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 10.42 UTCresolved

   Engineering team fortsætter med at undersøge fejlen 500 problem i OP1. I denne periode kan brugerne opleve intermitterende problemer i vores system. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

2. 3. september 2026 kl. 11.02 UTCresolved

   Engineering team fortsætter med at undersøge fejlen 500 problem i OP1. I denne periode kan brugerne opleve intermitterende problemer i vores system. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

3. 3. september 2026 kl. 11.34 UTCresolved

   Engineering team fortsætter med at undersøge fejlen 500 problem i OP1. I denne periode kan brugerne opleve intermitterende problemer i vores system. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

4. 3. september 2026 kl. 12.00 UTCresolved

   Engineering team fortsætter med at undersøge fejlen 500 problem i OP1. I denne periode kan brugerne opleve intermitterende problemer i vores system. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

5. 3. september 2026 kl. 12.30 UTCresolved

   Engineering team fortsætter med at undersøge fejlen 500 problem i OP1. I denne periode kan brugerne opleve intermitterende problemer i vores system. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

6. 3. september 2026 kl. 13.03 UTCresolved

   Okta Engineering var i stand til at træffe de nødvendige foranstaltninger til at afbøde problemet og er i øjeblikket overvågning for stabilitet. Årsagen til problemet og detaljerne om de trufne foranstaltninger vil blive lagt på Trust-siden.

7. 3. september 2026 kl. 14.09 UTCresolved

   Efter at have overvåget i en længere periode har vi bekræftet, at spørgsmålet ikke er opstået igen. En grundlæggende årsag analyse (RCA) vil blive lagt her inden for fem bankdage. Vi undskylder for den virkning, det havde på dig og dine brugere.

8. 11. september 2026 kl. 17.26 UTCresolved

   Vi undskylder oprigtigt for enhver virkning denne hændelse har forårsaget for dig, din virksomhed, og dine kunder. hos Otta er tillid og gennemsigtighed vores topprioriteter. Nedenfor er de fakta om denne hændelse. Vi er forpligtet til at gennemføre forbedringer af tjenesten for at forhindre fremtidige hændelser af denne hændelse. Detection and Impact: Den 2. september 2026 på 11: 43 PM PDT, Okta intern overvågning og kunderapporter advarede vores team af spørgsmål for brugere adgang til Okta Preview Cell OP1 i Nordamerika. I denne periode, nogle kunder på OP1 kan have oplevet HTTP 500 Intern Server Fejl eller 503 Service Utilgængelige svarkoder for forskellige slutpunkter, herunder dem, der vedrører godkendelse og SSO. Rodårsagen Oversigt: En udgivelse indført en midlertidig cache datastruktur mismatch mellem softwareversioner. Denne cache data anvendes som en del af anmodningen evaluering og forventes at være fremad og bagud kompatibel. Som et resultat, disse mislykkede cache objekt evalueringer resulterede i fejl på tværs af kernen godkendelse og API endepunkter. Oprydning Trin: Okta Engineering hændelsesrespons teams tog en række korrigerende handlinger, herunder rullende back service ændringer og isolere og rydde uforenelige data værdier fra cache butik. Forebyggende foranstaltninger: For at forhindre lignende hændelser i at ske igen, Otta har i øjeblikket gennemført følgende: Løs datastrukturen til en opgradering sikker implementering Implementeret drift detektering data håndhævelse regler og tilføjet yderligere automatiserede tests i forbindelse med håndhævelse kompatibilitet mellem tjenester implementeringer Derudover er vi i færd med at gennemgå og forbedre vores interne testprocesser og procedurer for at forhindre dette problem i at gentage sig i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. juli 2026 kl. 13.55 UTCresolved

   Efter en periode med stabilitet og overvågning kan vi nu bekræfte, at servicespørgsmålet er blevet løst fuldt ud. Yderligere root årsag oplysninger vil være tilgængelige inden for fem bankdage.

2. 1. august 2026 kl. 03.28 UTCresolved

   Vi undskylder oprigtigt for enhver virkning denne hændelse har forårsaget for dig, din virksomhed, og dine kunder. hos Otta er tillid og gennemsigtighed vores topprioriteter. Nedenfor er de fakta om denne hændelse. Vi er forpligtet til at gennemføre forbedringer af vores tjenester for at forhindre fremtidige hændelser. Detektering og virkning På 24 juli 2026, på ca. 3: 55 AM PDT, Otta observeret service nedbrydning for OK7, OK12, OK14 og OP3. Hændelsen specifikt påvirket kunder bruger AD / LDAP delegeret godkendelse og OAuth endpoint klienter beliggende i AWS us- west-2 region. Under hele arrangementet, brugere stødt på fejl adgang ressourcer, autentificering fejl, agent forbindelse timeouts, latency, og OAuth token anmodninger. Oversigt over rodårsag Den grundlæggende årsag opstod fra fejl inden for en cloud-udbyder for den berørte region. Rengøring trin Den cloud-udbyder genvundet forbindelse, og Otta service stabiliseret ved ca. 4: 10 AM PDT, og vores hold bekræftede en komplet tilbagevenden til baseline operationer på 4: 19 AM PDT. Forebyggende aktioner Otta er aktivt at gennemgå og gennemføre flere initiativer for at forhindre fremtidige hændelser. Disse foranstaltninger omfatter: revision og forbedring af vores reaktion på hændelser i tilfælde af udvidede spørgsmål i en region, og raffinere vores overvågning og varsling baseret på denne hændelse. Varighed i alt (minutter): 15 minutter Starttid: 3: 55 AM PDT Sluttid: 4: 10 AM PDT Varighed (# af minutter): 15

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juli 2026 kl. 15.14 UTCresolved

   Vær opmærksom på, at vores planlagte vedligeholdelse stadig er i gang, og Okta Engineering teams er aktivt engageret. I dette udvidede vindue kan kunderne opleve fejl, når de logger ind på OCL Workflows. Vi sætter pris på din tålmodighed som vores hold arbejder på at fuldføre denne operation så hurtigt og sikkert som muligt. & nbsp; For at forstå hvordan dette kan påvirke din organisation og for at se anbefalede workarounds, skal du gennemgå vores detaljerede supportartikel: & nbsp; https: / / support.okta.com / help / s / article / octa- workflows- cell - migration- expected- adfærds- and- workarounds? language = en _ US. Vi vil give yderligere opdateringer om 30 minutter, eller før, som flere oplysninger bliver tilgængelige.

2. 22. juli 2026 kl. 15.49 UTCresolved

   Vedligeholdelsesaktiviteten er stadig i gang, da vi sikrer, at migrationen er gennemført sikkert og vellykket. & nbsp; Vi vil fortsætte med at dele opdateringer om 30 minutter eller før, da de bliver tilgængelige. I mellemtiden henvises til nedenstående støtteartikel for den seneste vejledning om arbejdsområder og forventet adfærd: http: / / support.okta.com / help / s / article / octa- workflows- cell-migration- expected-adfærds- and-workarounds? language = en _ US

3. 22. juli 2026 kl. 16.19 UTCresolved

   Vi observerer nu stabile systempræstationer efter migrationsaktiviteterne. Vores ingeniørhold er fortsat aktivt involveret i overvågningen af alle tjenester. Kernearbejdsgange er ved at komme sig, og kunderne bør se fortsatte forbedringer. Vi vil give vores næste opdatering om 30 minutter, eller før hvis nye oplysninger bliver tilgængelige.

4. 22. juli 2026 kl. 16.59 UTCresolved

   Efter en periode med stabilitet og overvågning kan vi nu bekræfte, at servicespørgsmålet er blevet løst fuldt ud. Yderligere root årsag oplysninger vil være tilgængelige inden for fem bankdage.

5. 29. juli 2026 kl. 23.34 UTCresolved

   Vi undskylder oprigtigt for enhver virkning denne hændelse har forårsaget for dig, din virksomhed, og dine kunder. hos Otta er tillid og gennemsigtighed vores topprioriteter. Nedenfor er de fakta om denne hændelse. Vi er forpligtet til at gennemføre forbedringer af vores tjenester for at forhindre fremtidige hændelser. Vi erkender, at denne vedligeholdelse løb ud over sit oprindeligt kommunikerede vindue, og at vores status opdateringer under denne udvidelse ikke holde kunderne informeret i tide. Vi undskylder for dette; at forbedre det er en del af vores forebyggende foranstaltninger nedenfor. Detection and Impact On July 22, 2026, på 5: 15 AM PDT, Okta Workflows i vores Nordamerika region (FL1 celle) begyndte at opleve problemer, der påvirkede Workflows brugere på tværs af amerikanske celler 1, 2, 3, 4, 6, 7 og 11. I løbet af denne tid, nogle workflow henrettelser mislykkedes eller sluttede for tidligt, og brugerne stødte fejl indlæsning Workflows Console. Derudover er nogle app-forbindelser stoppet med at arbejde, hvilket kræver, at brugerne skal manuelt autentificere for at gendanne funktionalitet. Oversigt over rodårsag Problemet opstod under en planlagt systemopgradering. En defekt i en tredjeparts sælgers software fik opgraderingen til at køre betydeligt længere end forventet. Mens migrere til en ny datastore system, en kommunikation fiasko mellem systemkomponenter forhindrede tjenesten i at vende tilbage til sin normale tilstand inden for det forventede vindue. I denne periode, Workflows Console ikke degraderes elegant, når den underliggende data butik var utilgængelig; i stedet, det dukkede fejl direkte til brugerne. Desuden, app-forbindelser, hvis legitimationsoplysninger ikke kunne genopfriskes under afbrydelsen blev efterladt i en mislykket tilstand og blev ikke automatisk genopfrisket, hvilket er grunden til nogle fejl fortsatte efter opgraderingen afsluttet, indtil den berørte forbindelse blev gengodkendt. Rengøring trin Den tredje part sælger bekræftede klyngen stabiliseret på 8: 34 AM PDT. Efter stabilisering, Okta Engineering genvundet berørte tjenester til klare gamle konfiguration cache. Alle kunder, der oplevede OAuth token genopfriske fejl i denne periode var forpligtet til manuelt at godkende enhver app-forbindelser. Fuld funktionalitet blev genoprettet 9: 33 AM PDT. Hvis du stadig er påvirket: manuelt genautorisere de berørte forbindelsesoplysninger i Workflows Konsole (se KB: Okta Workflows: Cell Migration Forventet Opførsel og Workarounds). Workflow henrettelser, der mislykkedes i løbet af vinduet kan re- køre ved hjælp af din normale proces; kontakt Okta Support, hvis du ønsker hjælp til at identificere berørte henrettelser. Forebyggende foranstaltninger For at undgå lignende hændelser har Otta taget følgende skridt. Vi har håndhævet en fleet- wide hold på alle yderligere datastore motor vandringer indtil vores tredjeparts leverandør anvender en rettelse for den bekræftede defekt og bekræfter, at det er sikkert at fortsætte. Vi er også opdatere Workflows Console til at mislykkes hurtigt og komme sig automatisk, når infrastrukturen er midlertidigt utilgængelig, hvilket sikrer brugerne se en gentilslutning tilstand snarere end rå systemfejl. Sideløbende hermed tilføjer vi direkte automatisk overvågning og varsling for fejl i cluster-konvergens for at sikre hurtigere detektion under vedligeholdelsesvinduer. Endelig, vi er ved at forbedre, hvordan vi kommunikerer under vedligeholdelse, der kører længe, herunder en mere rettidig status side og fremskridt / afslutning opdateringer. For spørgsmål om Workflows pålidelighed eller køreplan, kan din Okta konto team hjælpe. Varighed i alt (minutter): 258 minutter (4 timer og 18 minutter) Starttid: 5: 15 AM PDT Sluttid: 9: 33 AM PDT Varighed (# af minutter): 258 minutter

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. juli 2026 kl. 21.23 UTCresolved

   Vores ingeniørhold har anvendt en potentiel rettelse til den ramte preview miljø og er aktivt at overvåge systemet for inddrivelse. Vi vil give en anden opdatering inden for 30 minutter, eller før, hvis nye oplysninger bliver tilgængelige. Vi undskylder for ulejligheden.

2. 13. juli 2026 kl. 21.39 UTCresolved

   Vores Engineering team har anvendt et fix, og vi observere service restaurering til vores OP2 preview miljø. Vi overvåger systemet nøje og vil levere endnu en opdatering inden for 30 minutter.

3. 13. juli 2026 kl. 21.53 UTCresolved

   Vi har bekræftet, at OP2 forhåndsvisning miljø har fuldt stabiliseret, og det tidligere problem er helt løst. Yderligere root årsag oplysninger vil være tilgængelige inden for fem bankdage.

4. 21. juli 2026 kl. 01.57 UTCresolved

   Vi undskylder oprigtigt for enhver virkning denne hændelse har forårsaget for dig, din virksomhed, og dine kunder. hos Otta er tillid og gennemsigtighed vores topprioriteter. Nedenfor er de fakta om denne hændelse. Vi er forpligtet til at gennemføre forbedringer af tjenesten for at forhindre fremtidige hændelser af denne hændelse. Detection and Impact: Den 13. juli 2026 kl. 1: 01 PT, Otta intern overvågning advarede vores team om forhøjede fejl i EMEA Preview Cell miljø. I denne periode blev alle kunder i EMEA Preview Cell miljøet påvirket, oplever autentificering svigt og service langsommelighed. Administratorer og slutbrugere kan have stødt på "Intern Server Error" meddelelser og andre fejl, når de forsøger at logge ind eller få adgang til Okta tjenester. Root Cause Oversigt: hændelsen blev udløst under en planlagt opgradering af tjenesten. En forkert konfiguration fik EMEA Preview Cell klyngen til utilsigtet at modtage en forkert version af en kritisk infrastrukturroutingkomponent. Denne opdatering brød intern netværksforbindelse, hvilket forhindrede kommunikation mellem ellers sunde infrastrukturkomponenter. Fordi anmodninger ikke kunne nå den centrale applikation, det resulterede i udbredte servicefejl og autentificering fejl. Oprydning Steps: Oktas ingeniørhold identificerede problemet og straks begyndte at implementere den tidligere, stabile version af routing konfiguration. Efter rollback, ingeniører systematisk genstartet de berørte tjenester (herunder gateways og proxyes) for at genoprette interne konnektivitet. Disse handlinger med succes behandlet problemet, og kundernes indvirkning blev fuldt afbødet med 2: 20 PM PT. Forebyggende aktioner: Vi raffinerer vores operationelle processer for at forbedre servicestabiliteten. Dette omfatter løbende arbejde med at forbedre auto-detektion og overvågning kapaciteter, hjælpe os med at identificere og løse potentielle spørgsmål mere effektivt. Samlet varighed (minutter): 79 minutter (1 time 19 minutter) Starttid: 1: 01 PM PT Sluttid: 2: 20 PM PT

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 20.50 UTCresolved

   Okta engineering har et identificeret et problem, der påvirker Okta Workflows og er i øjeblikket at tage skridt til at afhjælpe. Kunderne kan se 500 fejl eller timeouts i Okta Workflows konsol, API endepunkter og indgående webkroge. Vi vil give en anden opdatering inden for de næste 30 minutter, eller før hvis yderligere oplysninger bliver tilgængelige.

2. 7. juli 2026 kl. 21.03 UTCresolved

   Problemet med Okta Workflows er blevet løst. Alle arbejdsgange behandles nu normalt. En grundlæggende årsag analyse (RCA) vil blive lagt her inden for fem bankdage. Vi undskylder for eventuelle ulemper.

3. 15. juli 2026 kl. 15.22 UTCresolved

   Vi undskylder oprigtigt for enhver virkning denne hændelse kan have forårsaget for dig, din virksomhed, eller dine kunder. hos Otta er tillid og gennemsigtighed vores topprioriteter. Nedenfor er de fakta om denne hændelse. Vi er forpligtet til at gennemføre forbedringer af tjenesten for at forhindre fremtidige hændelser af denne hændelse. Detection and Impact: Den 7. juli 2026, på 1: 01 PM PDT, Okta intern overvågning og kunderapporter advarede vores team til problemer med brugere adgang Workflows på OK14-cellen i Nordamerika. I denne periode, kunder på FL14 kan have oplevet HTTP 500, 503, eller 504 Gateway Timeout fejl, når man navigerer til Workflows fra admin portal eller forsøger at logge ind på Workflows Console via SSO. Eksisterende sessioner kan have udslettet periodisk. Planlagte og on-demand arbejdsgange, inline kroge og webkroge kan have oplevet fejl og timeouts. Derudover oplevede henrettelser inden for flyvningen timeouts. Rodårsag Oversigt: Denne hændelse opstod under den planlagte implementering af udgivelse 2027.07.0 til FL14 celle. I løbet af introduktionsprocessen blev en tjenestepod med ansvar for udførelse af schema opdateringer afsluttet for tidligt. Denne tidlige afslutning førte til uventede, langlivede databaseforbindelser, som i sidste ende forårsagede tilslutningsudmattelse på cellens primære database. Oprydning Trin: Ved modtagelse af advarsler og kunderapporter, holdet begyndte diagnostik på 12: 44 PM PDT. Ved 1: 30 PM PDT, isolerede og fjernede de service pod udfører schema opdateringer. Dette gav databasen forbindelser til at rydde, genoprette fuld service ved 1: 45 PM PDT. Forebyggende aktioner: For at forhindre fremtidige hændelser er Otta forpligtet til at styrke vores infrastrukturstabilitet og styrke vores overvågningskapacitet. Vi er i øjeblikket ved at gennemføre strategiske forbedringer af vores implementeringsprocesser og varslingssystemer for at sikre hurtigere detektion, reaktion og større modstandsdygtighed på tværs af vores tjenester. Samlet varighed: 67 minutter

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. juni 2026 kl. 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. juni 2026 kl. 23.50 UTCresolved

3. 30. juni 2026 kl. 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. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 11.21 UTCresolved

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

2. 2. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 18.40 UTCresolved

1. 22. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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.