Istoricul incidentelor Okta

1. 3 septembrie 2026 la 10:42 UTCresolved

   Echipa Inginerie continuă să investigheze eroarea 500 în OP1. În acest timp, utilizatorii pot experimenta probleme intermitente în sistemul nostru. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

2. 3 septembrie 2026 la 11:02 UTCresolved

   Echipa Inginerie continuă să investigheze eroarea 500 în OP1. În acest timp, utilizatorii pot experimenta probleme intermitente în sistemul nostru. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

3. 3 septembrie 2026 la 11:34 UTCresolved

   Echipa Inginerie continuă să investigheze eroarea 500 în OP1. În acest timp, utilizatorii pot experimenta probleme intermitente în sistemul nostru. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

4. 3 septembrie 2026 la 12:00 UTCresolved

   Echipa Inginerie continuă să investigheze eroarea 500 în OP1. În acest timp, utilizatorii pot experimenta probleme intermitente în sistemul nostru. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

5. 3 septembrie 2026 la 12:30 UTCresolved

   Echipa Inginerie continuă să investigheze eroarea 500 în OP1. În acest timp, utilizatorii pot experimenta probleme intermitente în sistemul nostru. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

6. 3 septembrie 2026 la 13:03 UTCresolved

   Okta Engineering a fost în măsură să ia măsurile necesare pentru a atenua problema și este în prezent de monitorizare pentru stabilitate. Cauza problemei și specificul acțiunilor întreprinse vor fi postate pe pagina Trust.

7. 3 septembrie 2026 la 14:09 UTCresolved

   După monitorizarea pe o perioadă îndelungată, am confirmat că problema nu s-a reluat. O analiză a cauzelor profunde (RCA) va fi postată aici în termen de cinci zile lucrătoare. Ne cerem sincer scuze pentru impactul pe care acest lucru l-a avut asupra dumneavoastră și a utilizatorilor.

Traducere automată din actualizarea oficială a incidentului.

1. 14 august 2026 la 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 la 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 la 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 la 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 iulie 2026 la 13:55 UTCresolved

   După o perioadă de stabilitate și monitorizare, putem confirma acum că problema serviciilor a fost rezolvată pe deplin. Informații suplimentare privind cauzele profunde vor fi disponibile în termen de cinci zile lucrătoare.

2. 1 august 2026 la 03:28 UTCresolved

   Ne cerem sincer scuze pentru orice impact pe care acest incident ţi l-a cauzat ţie, afacerii tale şi clienţilor tăi. La Okta, încrederea și transparența sunt prioritățile noastre principale. De mai jos sunt prezentate faptele cu privire la acest incident. Ne-am angajat să punem în aplicare îmbunătățiri ale serviciilor noastre pentru a preveni evenimentele viitoare. Detectare și impact La 24 iulie 2026, la aproximativ 3:55 AM PDT, Okta a observat degradarea serviciului pentru OK7, OK12, OK14 și OP3. Incidentul a avut un impact special asupra clienților care au utilizat autentificarea delegată AD/LDAP și clienții OAuth token-endpoint situate în regiunea AWS ne-west-2. Pe parcursul evenimentului, utilizatorii au întâmpinat erori de acces la resurse, eșecuri de autentificare, timeout-uri de conectare agent, latență, și OAuth token cereri. Rezumat cauza rădăcină Cauza principală provine din erori în cadrul unui furnizor de servicii de cloud pentru regiunea afectată. Etape de redresare Furnizorul de servicii cloud recuperat conectivitate, iar serviciul Okta stabilizat de aproximativ 4:10 AM PDT, și echipele noastre au confirmat o revenire completă la operațiunile de bază la 4:19 AM PDT. Acțiunile preventive Okta revizuiesc și execută în mod activ mai multe inițiative pentru a preveni evenimentele viitoare. Printre aceste măsuri se numără: auditarea și îmbunătățirea proceselor de răspuns la incidente în cazul unor probleme extinse într-o regiune și rafinarea monitorizării și alertei noastre pe baza acestui incident. Durata totala Durata totala (Minute): 15 minute Timp de pornire: 3:55 AM PDT Timp de sfarsit: 4:10 AM Durata TFD (# de minute): 15

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 15:14 UTCresolved

   Vă rugăm să fiţi atenţi că întreţinerea noastră programată este încă în curs de desfăşurare, iar echipele Okta Engineering sunt angajate activ. În timpul acestei ferestre extinse, clienții pot experimenta erori atunci când se conectează la fluxurile de lucru Okta. Apreciem răbdarea dumneavoastră ca echipele noastre lucrează pentru a finaliza această operațiune cât mai repede și în siguranță posibil.   Pentru a înțelege modul în care acest lucru ar putea avea un impact asupra organizației dumneavoastră și pentru a vizualiza programul de lucru recomandat, vă rugăm să revedeți articolul nostru de suport detaliat: https://support.okta.com/help/s/article/okta-workflows-cell-migration-asteptate-comaviors-and-working arounds? language=en US . Vom oferi actualizări suplimentare în 30 de minute, sau mai devreme, pe măsură ce mai multe informații devin disponibile.

2. 22 iulie 2026 la 15:49 UTCresolved

   Activitatea de întreținere este încă în curs de desfășurare, deoarece ne asigurăm că migrația este finalizată în condiții de siguranță și cu succes.   Vom continua să partajeze actualizări în 30 de minute sau mai devreme, ca acestea devin disponibile. Între timp, vă rugăm să consultați articolul de sprijin de mai jos pentru cele mai recente orientări cu privire la aranjamentele și comportamentele preconizate: http://support.okta.com/help/s/article/okta-working fluxs-cell-migration-asteptate-behaviors-and-workarounds?language=ro US

3. 22 iulie 2026 la 16:19 UTCresolved

   Observăm acum performanța stabilă a sistemului în urma activităților de migrație. Echipele noastre de ingineri rămân active în monitorizarea tuturor serviciilor. Fluxurile de lucru de bază se recuperează, iar clienții ar trebui să vadă îmbunătățiri continue. Vom furniza următoarea actualizare în 30 de minute, sau mai devreme în cazul în care informațiile noi devin disponibile.

4. 22 iulie 2026 la 16:59 UTCresolved

   După o perioadă de stabilitate și monitorizare, putem confirma acum că problema serviciilor a fost rezolvată pe deplin. Informații suplimentare privind cauzele profunde vor fi disponibile în termen de cinci zile lucrătoare.

5. 29 iulie 2026 la 23:34 UTCresolved

   Ne cerem sincer scuze pentru orice impact pe care acest incident ţi l-a cauzat ţie, afacerii tale şi clienţilor tăi. La Okta, încrederea și transparența sunt prioritățile noastre principale. De mai jos sunt prezentate faptele cu privire la acest incident. Ne-am angajat să punem în aplicare îmbunătățiri ale serviciilor noastre pentru a preveni evenimentele viitoare. Noi recunoaștem că această întreținere a fugit dincolo de fereastra sa inițial comunicate și că actualizările noastre de stare în timpul acestei prelungiri nu a ținut clienții informați în timp util. Ne cerem scuze pentru acest lucru; îmbunătățirea acestuia face parte din acțiunile noastre preventive de mai jos. Detectie si impact La 22 iulie 2026, la 5:15 AM PDT, Okta Fluxuri de lucru in regiunea noastra din America de Nord (celula FL1) au inceput sa se confrunte cu probleme care au afectat utilizatorii fluxurilor de lucru in intre celulele SUA 1, 2, 3, 4, 6, 7 si 11. În acest timp, unele execuţii ale fluxului de lucru au eşuat sau s-au încheiat prematur, iar utilizatorii au întâmpinat erori de încărcare a Consolei de lucru. În plus, unele conexiuni aplicații oprit de lucru, care necesită utilizatorilor să reautentice manual pentru a restabili funcționalitatea. Rezumat cauza rădăcină Problema a avut loc în timpul unei actualizări planificate a sistemului. Un defect în software-ul unui furnizor de terțe părți a cauzat actualizarea pentru a rula semnificativ mai mult decât se aștepta. În timp ce migrează către un nou sistem de stocare a datelor, o eroare de comunicare între componentele sistemului a împiedicat serviciul să revină la starea sa normală în cadrul ferestrei preconizate. În această perioadă, Consola de lucru nu s-a degradat grațios atunci când magazinul de date suport nu a fost disponibil; în schimb, a ieșit la suprafață erori direct către utilizatori. În plus, conexiunile aplicației ale căror acreditări nu au putut fi reîmprospătate în timpul întreruperii au fost lăsate într-o stare eșuată și nu au fost reîmprospătate automat, motiv pentru care unele erori au continuat după actualizarea finalizată, până când conexiunea afectată a fost reautorizată. Etape de redresare Vânzătorul terţ a confirmat că grupul s-a stabilizat la 8:34 AM PDT. După stabilizare, Okta Engineering a recuperat serviciile afectate pentru a șterge cache-urile de configurare vechi. Orice client care a experimentat erori de reîmprospătare OAuth în această perioadă au fost necesare pentru a reautoriza manual orice conexiuni de aplicație. Funcţionalitatea completă a fost restabilită la ora 9:33 AM PDT. Dacă sunteți încă afectate: reautorizează manual acreditările de conectare afectate în Consola de fluxuri de lucru (a se vedea KB: Okta Fluxuri de lucru: Migrația celulară preconizată Comportamente și Workarounds). Execuțiile de flux de lucru care au eșuat în timpul ferestrei pot fi refuncționate utilizând procesul normal; contactați Okta Support dacă doriți să ajutați la identificarea execuțiilor afectate. Acțiuni preventive Pentru a preveni apariţia unor incidente similare, Okta a luat următoarele măsuri. Am pus în aplicare o așteptare la nivelul întregii flote asupra tuturor migrărilor ulterioare ale motoarelor de la magazinul de date până când vânzătorul nostru de terțe părți trimite un fix pentru defectul confirmat și confirmă că este sigur să continuăm. De asemenea, actualizăm Console-ul fluxurilor de lucru pentru a eşua rapid şi a recupera automat atunci când infrastructura este temporar indisponibilă, asigurându-ne că utilizatorii văd o stare de reconectare mai degrabă decât erori de sistem brut. În paralel, adăugăm monitorizare automată directă și alertăm eșecurile de convergență a grupurilor pentru a asigura detectarea mai rapidă în timpul ferestrelor de întreținere. În cele din urmă, îmbunătățim modul în care comunicăm în timpul întreținerii, care durează mult, inclusiv o pagină de stare mai oportună și actualizări ale progreselor/finalizării. Pentru întrebări despre fiabilitatea fluxurilor de lucru sau foaia de parcurs, echipa dvs. de cont Okta vă poate ajuta. Durata totală Durata totală (Minute): 258 minute (4 ore și 18 minute) Timpul de începere: 5:15 AM PDT Timpul de finalizare: 9:33 AM PDT Durata (# de minute): 258 minute

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 21:23 UTCresolved

   Echipa noastră de ingineri a aplicat o posibilă fixare a mediului de previzualizare afectat și monitorizează activ sistemul de recuperare. Vom oferi o altă actualizare în 30 de minute, sau mai devreme în cazul în care informațiile noi devin disponibile. Ne cerem scuze sincer pentru neplăceri.

2. 13 iulie 2026 la 21:39 UTCresolved

   Echipa noastră de Inginerie a aplicat un fix şi observăm restaurarea serviciului în mediul nostru de previzualizare OP2. Monitorizăm îndeaproape sistemul și vom oferi o altă actualizare în 30 de minute.

3. 13 iulie 2026 la 21:53 UTCresolved

   Am confirmat că mediul de previzualizare OP2 s-a stabilizat complet, iar problema anterioară este complet rezolvată. Informații suplimentare privind cauzele profunde vor fi disponibile în termen de cinci zile lucrătoare.

4. 21 iulie 2026 la 01:57 UTCresolved

   Ne cerem sincer scuze pentru orice impact pe care acest incident ţi l-a cauzat ţie, afacerii tale şi clienţilor tăi. La Okta, încrederea și transparența sunt prioritățile noastre principale. De mai jos sunt prezentate faptele cu privire la acest incident. Ne-am angajat să punem în aplicare îmbunătățiri ale serviciului pentru a preveni evenimentele viitoare ale acestui incident. Detectare și impact: La 13 iulie 2026 la 1:01 PM PT, monitorizarea internă Okta a alertat echipa noastră la erori ridicate în mediul de celule Preview EMEA. În această perioadă, toţi clienţii din mediul celulelor de previzualizare EMEA au fost afectaţi, experimentând eşecuri de autentificare şi încetinire a serviciilor. Administratorii și utilizatorii finali pot să fi întâlnit mesaje "Eroare de server intern" și alte erori atunci când încearcă să se conecteze sau să acceseze serviciile Okta. Root Cause Rezumat: Incidentul a fost declanșat în timpul unui upgrade de serviciu programat. O configuraţie greşită a determinat grupul de celule de previzualizare EMEA să primească accidental o versiune incorectă a unei componente critice de rutare a infrastructurii. Această actualizare a întrerupt ruta de rețea internă, ceea ce a împiedicat comunicarea între componente de infrastructură sănătoase. Deoarece cererile nu au putut ajunge la cererea de bază, acestea au dus la erori de serviciu extinse și la deficiențe de autentificare. Pasi de reabilitare: echipa de inginerie Okta a identificat problema și a început imediat implementarea versiunii anterioare, stabile a configurației de rutare. După răsturnare, inginerii au reluat în mod sistematic serviciile afectate (inclusiv porțile de acces și proxy-urile) pentru a restabili conectivitatea internă. Aceste acțiuni au abordat cu succes problema, iar impactul asupra clienților a fost pe deplin atenuat de PT de 2:20 PM. Acțiuni preventive: Ne perfecționăm procesele operaționale pentru a îmbunătăți stabilitatea serviciilor. Aceasta include activități în curs de desfășurare de îmbunătățire a capacităților de detectare și monitorizare auto, ajutându-ne să identificăm și să abordăm mai eficient potențialele probleme. Durata totală (Minute): 79 minute (1 oră 19 minute) Timp de pornire: 1:01 PM PT Timp de sfârșit: 2:20 PM PT

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 20:50 UTCresolved

   Ingineria Okta are o problemă identificată care afectează fluxurile de lucru Okta și ia în prezent măsuri de remediere. Clienții pot vedea 500 de erori sau timeout-uri în consola Okta Workflows, API obiective, și inbound webhooks. Vom oferi o altă actualizare în următoarele 30 de minute, sau mai devreme în cazul în care informațiile suplimentare devin disponibile.

2. 7 iulie 2026 la 21:03 UTCresolved

   Problema fluxurilor de lucru Okta a fost rezolvată. Toate fluxurile de lucru sunt acum de procesare în mod normal. O analiză a cauzelor profunde (RCA) va fi postată aici în termen de cinci zile lucrătoare. Ne cerem scuze pentru orice neplăceri cauzate.

3. 15 iulie 2026 la 15:22 UTCresolved

   Ne cerem sincer scuze pentru orice impact pe care acest incident vi l-a cauzat, dvs. sau clienţilor dvs. La Okta, încrederea și transparența sunt prioritățile noastre principale. De mai jos sunt prezentate faptele cu privire la acest incident. Ne-am angajat să punem în aplicare îmbunătățiri ale serviciului pentru a preveni evenimentele viitoare ale acestui incident. Detectie si impact: Pe 7 iulie 2026, la 1:01 PM PDT, monitorizarea interna Okta si rapoartele clientilor ne-au alertat echipa de problemele cu utilizatorii accesand Fluxurile de Lucru pe celula Okta OK14 din America de Nord. În această perioadă, clienții de pe FL14 ar fi putut experimenta erori HTTP 500, 503, sau 504 Gateway Timeout atunci când navigau la fluxurile de lucru de la portalul admin sau încercarea de a se conecta la Console fluxuri de lucru prin intermediul SSO. Este posibil ca sesiunile existente să se fi defectat intermitent. Fluxuri de lucru programate și la cerere, cârlige de linie, și site-uri pot fi experimentat erori și timeouts. În plus, execuţiile în timpul zborului s-au prelungit. Root Cause Rezumat: Acest incident a avut loc în timpul implementării planificate de eliberare 2027.07.0 la celula FL14. În cursul procesului de desfășurare, o capsulă de serviciu responsabilă cu executarea actualizărilor schema a fost încheiată prematur. Această terminare timpurie a condus la conexiuni neaşteptate, de lungă durată, care au cauzat în cele din urmă epuizarea conexiunii în baza de date primară a celulei. Etape de reabilitare: La primirea alertelor și a rapoartelor clienților, echipa a început diagnosticarea la 12:44 PM PDT. Până la 1:30 PM PDT, au izolat și eliminat capsula de service efectuarea actualizări schema. Acest lucru a permis conexiunile bazei de date pentru a șterge, restaurarea serviciului complet de 1:45 PM PDT. Acțiuni preventive: Pentru a preveni evenimentele viitoare, Okta se angajează să consolideze stabilitatea infrastructurii și să consolideze capacitățile noastre de monitorizare. În prezent punem în aplicare îmbunătățiri strategice ale proceselor noastre de implementare și ale sistemelor de alertă pentru a asigura o detectare mai rapidă, un răspuns și o mai mare reziliență în cadrul serviciilor noastre. Durata totală: 67 minute

Traducere automată din actualizarea oficială a incidentului.

1. 26 iunie 2026 la 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 iunie 2026 la 23:50 UTCresolved

3. 30 iunie 2026 la 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 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 11:21 UTCresolved

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

2. 2 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 18:40 UTCresolved

1. 22 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 16:42 UTCresolved

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

3. 14 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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