Cronologia delle interruzioni di Okta

1. 3 settembre 2026 alle ore 10:42 UTCresolved

   Il team di Ingegneria continua a indagare sull'errore 500 problema in OP1. Durante questo periodo, gli utenti possono sperimentare problemi intermittenti all'interno del nostro sistema. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

2. 3 settembre 2026 alle ore 11:02 UTCresolved

   Il team di Ingegneria continua a indagare sull'errore 500 problema in OP1. Durante questo periodo, gli utenti possono sperimentare problemi intermittenti all'interno del nostro sistema. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

3. 3 settembre 2026 alle ore 11:34 UTCresolved

   Il team di Ingegneria continua a indagare sull'errore 500 problema in OP1. Durante questo periodo, gli utenti possono sperimentare problemi intermittenti all'interno del nostro sistema. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

4. 3 settembre 2026 alle ore 12:00 UTCresolved

   Il team di Ingegneria continua a indagare sull'errore 500 problema in OP1. Durante questo periodo, gli utenti possono sperimentare problemi intermittenti all'interno del nostro sistema. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

5. 3 settembre 2026 alle ore 12:30 UTCresolved

   Il team di Ingegneria continua a indagare sull'errore 500 problema in OP1. Durante questo periodo, gli utenti possono sperimentare problemi intermittenti all'interno del nostro sistema. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

6. 3 settembre 2026 alle ore 13:03 UTCresolved

   Okta Engineering è stata in grado di prendere le azioni necessarie per mitigare il problema ed è attualmente il monitoraggio per la stabilità. La causa del problema e le specifiche sulle azioni intraprese saranno pubblicate nella pagina Trust.

7. 3 settembre 2026 alle ore 14:09 UTCresolved

   Dopo il monitoraggio per un periodo prolungato, abbiamo confermato che il problema non si è occupato. Un'analisi della causa principale (RCA) verrà posta qui entro cinque giorni lavorativi. Ci scusiamo sinceramente per l'impatto che ha avuto su di voi e i vostri utenti.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 14 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 agosto 2026 alle ore 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 luglio 2026 alle ore 13:55 UTCresolved

   Dopo un periodo di stabilità e monitoraggio, possiamo ora confermare che il problema del servizio è stato completamente risolto. Ulteriori informazioni causa radice saranno disponibili entro cinque giorni lavorativi.

2. 1 agosto 2026 alle ore 03:28 UTCresolved

   Ci scusiamo sinceramente per qualsiasi impatto questo incidente ha causato a voi, la vostra attività e i vostri clienti. A Okta, la fiducia e la trasparenza sono le nostre priorità principali. Di seguito sono riportati i fatti relativi a questo incidente. Ci impegniamo ad implementare miglioramenti ai nostri servizi per prevenire eventi futuri. Rilevamento e impatto Il 24 luglio 2026, a circa 3:55 PDT, Okta ha osservato il degrado dei servizi per OK7, OK12, OK14 e OP3. L'incidente ha influenzato specificamente i clienti che utilizzano l'autenticazione delegata AD/LDAP e i client OAuth token-endpoint situati all'interno della regione AWS us-west-2. Durante l'evento, gli utenti hanno riscontrato errori di accesso alle risorse, guasti di autenticazione, timeout di connessione dell'agente, latenza e richieste di token OAuth. Sintesi della causa radice La causa principale deriva da errori all'interno di un provider di servizi cloud per la regione interessata. Procedura di bonifica Il provider di servizi cloud ha recuperato la connettività, e il servizio Okta stabilizzato di circa 4:10 AM PDT, e i nostri team hanno confermato un ritorno completo alle operazioni di base a 4:19 AM PDT. Azioni Preventative Okta sta esaminando ed eseguendo attivamente diverse iniziative per prevenire eventi futuri. Queste misure includono: l'audit e il miglioramento dei nostri processi di risposta agli incidenti in caso di problemi estesi all'interno di una regione, e la raffinazione del nostro monitoraggio e l'avviso in base a questo incidente. Durata totale Durata totale (Minutes): 15 minuti Tempo di inizio: 3:55 AM PDT Fine Time: 4:10 AM PDT Durata (# di minuti): 15

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 22 luglio 2026 alle ore 15:14 UTCresolved

   Si prega di notare che la nostra manutenzione programmata è ancora in corso, e i team di Okta Engineering sono attivamente impegnati. Durante questa finestra estesa, i clienti possono verificarsi errori durante l'accesso a Okta Workflows. Apprezziamo la vostra pazienza mentre i nostri team lavorano per completare questa operazione il più rapidamente e in modo sicuro possibile.   Per capire come questo potrebbe avere un impatto sulla vostra organizzazione e per vedere i metodi di lavoro consigliati, consultare il nostro articolo di supporto dettagliato: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en US . Forniamo ulteriori aggiornamenti in 30 minuti, o prima, come ulteriori informazioni diventa disponibile.

2. 22 luglio 2026 alle ore 15:49 UTCresolved

   L'attività di manutenzione è ancora in corso in quanto garantiamo che la migrazione sia completata in modo sicuro e con successo.   Continueremo a condividere gli aggiornamenti in 30 minuti o prima, come diventano disponibili. Nel frattempo, si prega di fare riferimento all'articolo di supporto qui sotto per le ultime indicazioni su soluzioni di lavoro e comportamenti attesi: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en US

3. 22 luglio 2026 alle ore 16:19 UTCresolved

   Stiamo ora osservando prestazioni di sistema stabili a seguito delle attività di migrazione. I nostri team di ingegneria rimangono attivamente impegnati nel monitoraggio di tutti i servizi. I flussi di lavoro core stanno recuperando, e i clienti dovrebbero vedere i miglioramenti continui. Forniamo il nostro prossimo aggiornamento in 30 minuti, o prima se nuove informazioni diventano disponibili.

4. 22 luglio 2026 alle ore 16:59 UTCresolved

   Dopo un periodo di stabilità e monitoraggio, possiamo ora confermare che il problema del servizio è stato completamente risolto. Ulteriori informazioni causa radice saranno disponibili entro cinque giorni lavorativi.

5. 29 luglio 2026 alle ore 23:34 UTCresolved

   Ci scusiamo sinceramente per qualsiasi impatto questo incidente ha causato a voi, la vostra attività e i vostri clienti. A Okta, la fiducia e la trasparenza sono le nostre priorità principali. Di seguito sono riportati i fatti relativi a questo incidente. Ci impegniamo ad implementare miglioramenti ai nostri servizi per prevenire eventi futuri. Riconosciamo che questa manutenzione è andata oltre la sua finestra originariamente comunicata e che il nostro stato aggiornamenti durante tale estensione non ha tenuto i clienti informati in modo tempestivo. Ci scusiamo per questo; migliorare è parte delle nostre azioni preventive qui sotto. Rilevamento e impatto Il 22 luglio 2026, alle 5:15 PDT, Okta Workflows nella nostra regione del Nord America (cellula FL1) ha iniziato a sperimentare problemi che hanno interessato gli utenti dei flussi di lavoro attraverso le celle degli Stati Uniti 1, 2, 3, 4, 6, 7, e 11. Durante questo periodo, alcune esecuzioni del flusso di lavoro sono fallite o sono finite prematuramente, e gli utenti hanno riscontrato errori di caricamento della console Workflows. Inoltre, alcune connessioni app hanno smesso di funzionare, richiedendo agli utenti di ripristinare manualmente la funzionalità. Sintesi della causa radice Il problema si è verificato durante un aggiornamento del sistema pianificato. Un difetto del software di un fornitore di terze parti ha causato l'aggiornamento a funzionare significativamente più lungo del previsto. Durante la migrazione a un nuovo sistema di datastore, un fallimento di comunicazione tra i componenti del sistema ha impedito al servizio di tornare al suo stato normale all'interno della finestra prevista. Durante questo periodo, il Workflows Console non ha degradato con grazia quando il data store sottostante non era disponibile; invece, ha superato gli errori direttamente agli utenti. Inoltre, le connessioni delle app le cui credenziali non potevano essere aggiornate durante l'interruzione sono state lasciate in uno stato fallito e non sono state aggiornate automaticamente, motivo per cui alcuni errori sono proseguiti dopo l'aggiornamento completato, fino a quando la connessione interessata non è stata riautorizzata. Procedura di bonifica Il fornitore di terze parti ha confermato il cluster stabilizzato a 8:34 AM PDT. Dopo la stabilizzazione, Okta Engineering ha recuperato i servizi interessati per cancellare le cache di configurazione stanti. Tutti i clienti che hanno sperimentato errori di aggiornamento di OAuth durante questo periodo sono stati tenuti a riautorizzare manualmente qualsiasi connessione di app. La funzionalità completa è stata ripristinata dalle 9:33 AM PDT. Se sei ancora interessato: riautorizza manualmente le credenziali di connessione colpite nella console Workflows (vedi KB: Okta Workflows: Cell Migration Expected Behaviors and Workarounds). Le esecuzioni del flusso di lavoro che sono fallite durante la finestra possono essere rielaborate usando il vostro processo normale; contattate Okta Support se volete aiutare a identificare le esecuzioni colpite. Azioni preventive Per evitare incidenti simili che si verificano, Okta ha preso i seguenti passaggi. Abbiamo applicato una tenuta a livello di flotta su tutte le ulteriori migrazioni del motore di datastore fino a quando il nostro fornitore di terze parti distribuisce una correzione per il difetto confermato e conferma che è sicuro procedere. Stiamo anche aggiornando il Workflows Console per non riuscire velocemente e recuperare automaticamente quando l'infrastruttura è temporaneamente non disponibile, assicurando agli utenti di vedere uno stato di ricollegamento piuttosto che errori di sistema grezzi. Parallelamente, stiamo aggiungendo un monitoraggio automatizzato diretto e un avviso per i guasti cluster-convergenza per garantire un rilevamento più rapido durante le finestre di manutenzione. Infine, stiamo migliorando il modo in cui comunichiamo durante la manutenzione che scorre a lungo, tra cui una pagina di stato piÃ1 tempestiva e aggiornamenti di progresso / completamento. Per domande sull'affidabilità dei flussi di lavoro o sulla roadmap, il vostro team di account Okta può aiutare. Durata totale Durata totale (Minutes): 258 minuti (4 ore e 18 minuti) Tempo di inizio: 5:15 AM PDT Tempo di fine: 9:33 PDT Durata (n. di minuti): 258 minuti

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 luglio 2026 alle ore 21:23 UTCresolved

   Il nostro team di ingegneria ha applicato un potenziale fix all'ambiente di anteprima impatto e sta monitorando attivamente il sistema per il recupero. Forniamo un altro aggiornamento entro 30 minuti, o prima se nuove informazioni diventano disponibili. Ci scusiamo sinceramente per qualsiasi inconveniente.

2. 13 luglio 2026 alle ore 21:39 UTCresolved

   Il nostro team di Ingegneria ha applicato una correzione, e stiamo osservando il ripristino di servizio al nostro ambiente di anteprima OP2. Stiamo monitorando attentamente il sistema e forniremo un altro aggiornamento entro 30 minuti.

3. 13 luglio 2026 alle ore 21:53 UTCresolved

   Abbiamo confermato che l'ambiente di anteprima OP2 è completamente stabilizzato, e il problema precedente è completamente risolto. Ulteriori informazioni causa radice saranno disponibili entro cinque giorni lavorativi.

4. 21 luglio 2026 alle ore 01:57 UTCresolved

   Ci scusiamo sinceramente per qualsiasi impatto questo incidente ha causato a voi, la vostra attività e i vostri clienti. A Okta, la fiducia e la trasparenza sono le nostre priorità principali. Di seguito sono riportati i fatti relativi a questo incidente. Ci impegniamo a implementare miglioramenti al servizio per prevenire futuri eventi di questo incidente. Rilevamento e impatto: il 13 luglio 2026 alle 1:01 PM PT, il monitoraggio interno di Okta ha avvertito il nostro team di elevare errori nell'ambiente EMEA Preview Cell. Durante questo periodo, tutti i clienti dell'ambiente EMEA Preview Cell sono stati colpiti, sperimentando guasti di autenticazione e lentezza di servizio. Gli amministratori e gli utenti finali possono aver incontrato messaggi "Internal Server Error" e altri errori durante il tentativo di accedere o accedere ai servizi Okta. Root Cause Sommario: L'incidente è stato attivato durante un aggiornamento di servizio programmato. Una cattiva configurazione ha causato il cluster EMEA Preview Cell per ricevere inavvertitamente una versione errata di un componente di routing infrastruttura critica. Questo aggiornamento ha rotto il routing di rete interna, che ha impedito la comunicazione tra componenti infrastrutturali altrimenti sani. Poiché le richieste non possono raggiungere l'applicazione principale, ha portato a errori di servizio diffusi e guasti di autenticazione. Remediation Steps: il team di ingegneria di Okta ha identificato il problema e ha iniziato immediatamente a distribuire la versione precedente e stabile della configurazione di routing. Dopo il rollback, gli ingegneri hanno riavviato sistematicamente i servizi interessati (compresi gateway e proxy) per ripristinare la connettività interna. Queste azioni hanno affrontato con successo il problema, e l'impatto del cliente è stato completamente mitigato da 2:20 PM PT. Azioni preventive: stiamo rifinanziando i nostri processi operativi per migliorare la stabilità dei servizi. Questo include il lavoro in corso per migliorare le capacità di rilevamento e monitoraggio automatico, aiutandoci a identificare e affrontare i potenziali problemi in modo più efficace. Durata totale (Minutes): 79 minuti (1 ora 19 minuti) Orario di inizio: 1:01 PM PT Fine Time: 2:20 PM PT

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 luglio 2026 alle ore 20:50 UTCresolved

   L'ingegneria Okta ha identificato un problema che riguarda i flussi di lavoro di Okta e sta attualmente prendendo misure per rimediare. I clienti possono vedere 500 errori o timeout nella console Okta Workflows, endpoint API e webhooks in entrata. Forniamo un altro aggiornamento entro i prossimi 30 minuti, o prima se ulteriori informazioni diventano disponibili.

2. 7 luglio 2026 alle ore 21:03 UTCresolved

   Il problema con Okta Workflows è stato risolto. Tutti i flussi di lavoro stanno ora elaborando normalmente. Un'analisi della causa principale (RCA) verrà posta qui entro cinque giorni lavorativi. Ci scusiamo per qualsiasi inconveniente che possa aver causato.

3. 15 luglio 2026 alle ore 15:22 UTCresolved

   Ci scusiamo sinceramente per qualsiasi impatto questo incidente potrebbe aver causato a voi, il vostro business, o i vostri clienti. A Okta, la fiducia e la trasparenza sono le nostre priorità principali. Di seguito sono riportati i fatti relativi a questo incidente. Ci impegniamo a implementare miglioramenti al servizio per prevenire futuri eventi di questo incidente. Rilevamento e impatto: il 7 luglio 2026, alle 13:00 PDT, il monitoraggio interno di Okta e i rapporti dei clienti hanno avvertito il nostro team di problemi con gli utenti che hanno accesso ai flussi di lavoro nella cella OK14 di Okta in Nord America. Durante questo periodo, i clienti di FL14 potrebbero aver sperimentato errori HTTP 500, 503, o 504 Gateway Timeout durante la navigazione ai flussi di lavoro dal portale di amministrazione o il tentativo di accedere al Console di flusso di lavoro tramite SSO. Le sessioni esistenti possono essere disattese intermittenti. Flussi di lavoro programmati e on-demand, ganci in linea, e webhooks possono avere errori e timeouts esperti. Inoltre, le esecuzioni in volo hanno sperimentato timeout. Riepilogo della causa della radice: Questo incidente si è verificato durante la prevista distribuzione del rilascio 2027.07.0 alla cella FL14. Nel corso del processo di implementazione, una capsula di servizio responsabile per l'esecuzione degli aggiornamenti dello schema è stata terminata prematuramente. Questa risoluzione precoce ha portato a connessioni di database inaspettate e di lunga durata, che alla fine ha causato esaurimento della connessione sul database primario della cella. Remediation Steps: Dopo aver ricevuto avvisi e rapporti con i clienti, il team ha iniziato la diagnostica a 12:44 PM PDT. Entro le ore 1:30 PDT, hanno isolato e rimosso il pod di servizio che esegue aggiornamenti di schema. Ciò ha permesso alle connessioni del database di cancellare, ripristinando il servizio completo di 1:45 PM PDT. Azioni preventive: Per prevenire gli eventi futuri, Okta si impegna a rafforzare la nostra stabilità delle infrastrutture e migliorare le nostre capacità di monitoraggio. Attualmente stiamo implementando miglioramenti strategici per i nostri processi di distribuzione e sistemi di avviso per garantire un rilevamento più rapido, una risposta e una maggiore resilienza nei nostri servizi. Durata totale: 67 minuti

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 26 giugno 2026 alle ore 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 giugno 2026 alle ore 23:50 UTCresolved

3. 30 giugno 2026 alle ore 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 luglio 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 11:21 UTCresolved

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

2. 2 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 18:40 UTCresolved

1. 22 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 16:42 UTCresolved

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

3. 14 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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