Histórico de interrupções do Okta

1. 15 Gwengolo 2026 da 16:22 UTCupdate

   As equipes de engenharia da Okta estão trabalhando ativamente em uma solução e coordenando com o fornecedor de serviços para restaurar a funcionalidade direta do azulejo. Forneceremos uma atualização em 30 minutos, ou mais cedo, conforme informações adicionais estiverem disponíveis.

2. 15 Gwengolo 2026 da 16:54 UTCupdate

   Continuamos trabalhando diretamente com nosso provedor de serviços de terceiros para solucionar problemas e resolver os erros intermitentes de redirecionamento HTTP 401 que afetam aplicativos do Office 365. Forneceremos outra atualização assim que novos detalhes estiverem disponíveis.

3. 15 Gwengolo 2026 da 18:30 UTCupdate

   Resolver problemas ativos com nosso fornecedor continua sendo uma escalada de alta prioridade em ambas as equipes de engenharia. Enquanto a determinação da causa raiz ainda está em andamento, entendemos o impacto operacional e estamos totalmente focados em conduzir isso para a resolução. Nossa próxima atualização será publicada assim que novos detalhes estiverem disponíveis.

4. 15 Gwengolo 2026 da 23:02 UTCupdate

   Nosso fornecedor de terceiros identificou a causa raiz que está impactando intermitentemente os serviços Microsoft 365 e está atualmente implementando uma correção. A implantação está em andamento a partir de 15 de setembro de 2026, embora a propagação completa em todas as contas de usuários seja esperada para levar aproximadamente 48 horas para resolver totalmente o problema. Estamos monitorando ativamente o progresso da implantação e forneceremos novas atualizações à medida que novos detalhes estiverem disponíveis. Informações adicionais sobre a causa raiz estarão disponíveis uma vez que o fornecedor tenha concluído completamente o lançamento da correção e a resolução completa validada.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Gwengolo 2026 da 12:50 UTCresolved

   A engenharia identificou o problema e tomou medidas de remediação para mitigar o problema. A conectividade aos domínios personalizados foi restaurada e o serviço voltou ao normal. O Okta continuará a monitorizar.

2. 11 Gwengolo 2026 da 13:10 UTCresolved

   A Okta remedia os problemas de conectividade OK9. Os erros de conectividade persistiram de 5:00 PDT a 5:36 PDT. Continuaremos a monitorar e produzir uma RCA em 5 dias úteis.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Gwengolo 2026 da 10:42 UTCresolved

   A equipe de Engenharia continua investigando o erro 500 na OP1. Durante esse tempo, os usuários podem estar experimentando problemas intermitentes dentro do nosso sistema. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

2. 3 Gwengolo 2026 da 11:02 UTCresolved

   A equipe de Engenharia continua investigando o erro 500 na OP1. Durante esse tempo, os usuários podem estar experimentando problemas intermitentes dentro do nosso sistema. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

3. 3 Gwengolo 2026 da 11:34 UTCresolved

   A equipe de Engenharia continua investigando o erro 500 na OP1. Durante esse tempo, os usuários podem estar experimentando problemas intermitentes dentro do nosso sistema. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

4. 3 Gwengolo 2026 da 12:00 UTCresolved

   A equipe de Engenharia continua investigando o erro 500 na OP1. Durante esse tempo, os usuários podem estar experimentando problemas intermitentes dentro do nosso sistema. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

5. 3 Gwengolo 2026 da 12:30 UTCresolved

   A equipe de Engenharia continua investigando o erro 500 na OP1. Durante esse tempo, os usuários podem estar experimentando problemas intermitentes dentro do nosso sistema. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

6. 3 Gwengolo 2026 da 13:03 UTCresolved

   A Okta Engineering foi capaz de tomar as ações necessárias para mitigar o problema e atualmente está monitorando a estabilidade. A causa do problema e as especificidades das ações tomadas serão postadas na página Confiança.

7. 3 Gwengolo 2026 da 14:09 UTCresolved

   Após o acompanhamento por um período prolongado, confirmamos que a questão não voltou a ocorrer. Uma análise de causa raiz (RCA) será postada aqui dentro de cinco dias úteis. Nós sinceramente pedimos desculpas pelo impacto que isso teve em você e seus usuários.

8. 11 Gwengolo 2026 da 17:26 UTCresolved

   Nós sinceramente pedimos desculpas por qualquer impacto que este incidente causou para você, seu negócio e seus clientes. Em Okta, confiança e transparência são nossas principais prioridades. Abaixo estão os fatos sobre este incidente. Estamos empenhados em implementar melhorias no serviço para evitar futuras ocorrências deste incidente. Detecção e Impacto: Em 2 de setembro de 2026 às 11:43 PDT, o monitoramento interno da Okta e os relatórios dos clientes alertaram nossa equipe de problemas para usuários que acessam o Okta Preview Cell OP1 na América do Norte. Durante este período, alguns clientes na OP1 podem ter experimentado HTTP 500 Erro Interno Server ou 503 Serviços Códigos de resposta indisponível para vários endpoints, incluindo aqueles relacionados à autenticação e SSO. Root Cause Resumo: Uma versão introduziu uma estrutura temporária de dados de cache descompasso entre versões de software. Estes dados de cache são usados como parte da avaliação de solicitação e esperados para ser avançado e backward compatível. Como resultado, essas avaliações falhadas de objetos de cache resultaram em erros entre os principais parâmetros de autenticação e API. Etapas de Remediação: Equipes de resposta de incidentes da Okta Engineering tomaram várias ações corretivas, incluindo mudanças no serviço de retorno e isolamento e limpeza de valores de dados incompatíveis da loja de cache. Acções de prevenção: A fim de evitar incidentes semelhantes acontecer novamente, Okta tem implementado atualmente o seguinte: Estrutura de dados resolvida para uma implementação segura de atualização Regras de execução de consistência de dados de detecção de deriva implementadas e testes automatizados adicionais relacionados com a aplicação de compatibilidade entre implantações de serviços Além disso, estamos revisando e aprimorando nossos processos e procedimentos internos de teste para evitar que esta questão se repita no futuro.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Gouere 2026 da 13:55 UTCresolved

   Após um período de estabilidade e monitorização, podemos agora confirmar que a questão dos serviços foi totalmente resolvida. Informação adicional da causa raiz estará disponível dentro de cinco dias úteis.

2. 1 Eost 2026 da 03:28 UTCresolved

   Nós sinceramente pedimos desculpas por qualquer impacto que este incidente causou para você, seu negócio e seus clientes. Em Okta, confiança e transparência são nossas principais prioridades. Abaixo estão os fatos sobre este incidente. Estamos empenhados em implementar melhorias em nossos serviços para evitar ocorrências futuras. Detecção e Impacto Em 24 de julho de 2026, aproximadamente 3:55 PDT AM, Okta observou degradação do serviço para OK7, OK12, OK14 e OP3. O incidente afetou especificamente os clientes utilizando a autenticação delegada AD/LDAP e clientes OAuth token-endpoint situados na região us-west-2 da AWS. Ao longo do evento, os usuários encontraram erros acessando recursos, falhas de autenticação, tempo limite de conexão do agente, latência e solicitações de token OAuth. Resumo da Causa Raiz A causa raiz originou-se de erros dentro de um provedor de serviço de nuvem para a região afetada. Passos de Remediação O provedor de serviços de nuvem recuperou conectividade e o serviço Okta estabilizou por aproximadamente 4:10 AM PDT, e nossas equipes confirmaram um retorno completo às operações de base às 4:19 AM PDT. Ações Preventivas O Okta está ativamente revisando e executando várias iniciativas para evitar ocorrências futuras. Estas medidas incluem: auditoria e melhoria dos nossos processos de resposta a incidentes no caso de questões alargadas dentro de uma região, e refinar o nosso acompanhamento e alerta com base neste incidente. Duração total Duração total (minutos): 15 minutos Tempo de início: 3:55 PDT Tempo de fim: 4:10 PDT Duração (# de minutos): 15

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 15:14 UTCresolved

   Esteja avisado de que nossa manutenção programada ainda está em andamento, e as equipes de Engenharia Okta estão ativamente envolvidas. Durante esta janela estendida, os clientes podem experimentar erros ao iniciar sessão no Okta Workflows. Agradecemos a sua paciência enquanto nossas equipes trabalham para concluir esta operação o mais rápido e seguro possível.   Para entender como isso pode afetar sua organização e visualizar soluções recomendadas, por favor, reveja nosso artigo de suporte detalhado: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarrounds?language=en US . Forneceremos atualizações adicionais em 30 minutos, ou mais cedo, à medida que mais informações estiverem disponíveis.

2. 22 Gouere 2026 da 15:49 UTCresolved

   A atividade de manutenção ainda está em curso, pois garantimos que a migração seja concluída com segurança e sucesso.   Continuaremos a partilhar actualizações dentro de 30 minutos ou mais cedo, à medida que estiverem disponíveis. Entretanto, consulte o artigo de apoio abaixo para as últimas orientações sobre soluções alternativas e comportamentos esperados: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en US

3. 22 Gouere 2026 da 16:19 UTCresolved

   Estamos agora a observar um desempenho estável do sistema após as actividades de migração. Nossas equipes de engenharia permanecem ativamente envolvidas em monitorar todos os serviços. Os fluxos de trabalho principais estão se recuperando, e os clientes devem ver melhorias contínuas. Forneceremos nossa próxima atualização em 30 minutos, ou mais cedo se novas informações estiverem disponíveis.

4. 22 Gouere 2026 da 16:59 UTCresolved

   Após um período de estabilidade e monitorização, podemos agora confirmar que a questão dos serviços foi totalmente resolvida. Informação adicional da causa raiz estará disponível dentro de cinco dias úteis.

5. 29 Gouere 2026 da 23:34 UTCresolved

   Nós sinceramente pedimos desculpas por qualquer impacto que este incidente causou para você, seu negócio e seus clientes. Em Okta, confiança e transparência são nossas principais prioridades. Abaixo estão os fatos sobre este incidente. Estamos empenhados em implementar melhorias em nossos serviços para evitar ocorrências futuras. Reconhecemos que essa manutenção foi além de sua janela originalmente comunicada e que nossas atualizações de status durante essa extensão não mantiveram os clientes informados em tempo hábil. Pedimos desculpas por isso; melhorá-lo faz parte de nossas ações preventivas abaixo. Detecção e Impacto Em 22 de julho de 2026, às 5:15 AM PDT, Okta Workflows em nossa região da América do Norte (Célula FL1) começou a experimentar problemas que afetaram os usuários de Workflows através das Células 1, 2, 3, 4, 6, 7 e 11. Durante esse tempo, algumas execuções de fluxo de trabalho falharam ou terminaram prematuramente, e os usuários encontraram erros ao carregar o Console Workflows. Além disso, algumas conexões de aplicativos pararam de funcionar, exigindo que os usuários reautentiquem manualmente para restaurar a funcionalidade. Resumo da Causa Raiz O problema ocorreu durante uma atualização planejada do sistema. Um defeito no software de um fornecedor de terceiros fez com que a atualização fosse significativamente maior do que o esperado. Ao migrar para um novo sistema de datastore, uma falha de comunicação entre componentes do sistema impediu o serviço de retornar ao seu estado normal dentro da janela esperada. Durante este período, o Workflows Console não se degradava graciosamente quando o armazenamento de dados subjacente estava indisponível; em vez disso, ele apareceu erros diretamente para os usuários. Além disso, as conexões de aplicativos cujas credenciais não puderam ser atualizadas durante a interrupção foram deixadas em um estado falhado e não foram automaticamente atualizadas, razão pela qual alguns erros continuaram após a atualização concluída, até que a conexão afetada foi reautorizada. Passos de Remediação O fornecedor de terceiros confirmou que o cluster se estabilizou às 8:34 AM PDT. Após estabilização, a Okta Engineering recuperou serviços afetados para limpar caches de configuração. Todos os clientes que experimentaram erros de atualização de token OAuth durante este período foram obrigados a reautorizar manualmente quaisquer conexões de aplicativos. A funcionalidade completa foi restaurada por 9:33 PDT. Se você ainda estiver afetado: autorize manualmente as credenciais de conexão afetadas no Console Workflows (veja KB: Okta Workflows: Cell Migration Expected Behaviors and Workarounds). As execuções de fluxo de trabalho que falharam durante a janela podem ser re-executadas usando seu processo normal; contate o Suporte do Okta se quiser ajudar a identificar execuções afetadas. Ações preventivas Para evitar incidentes semelhantes de ocorrer, Okta tomou as seguintes medidas. Impulsionamos toda a frota em todas as migrações adicionais do motor da datastore até que o nosso fornecedor terceiro implante uma correção para o defeito confirmado e confirme que é seguro prosseguir. Também estamos atualizando o Console Workflows para falhar rapidamente e recuperar automaticamente quando a infraestrutura está temporariamente indisponível, garantindo que os usuários vejam um estado de reconexão ao invés de erros de sistema brutos. Paralelamente, estamos adicionando monitoramento e alerta automático direto para falhas de convergência de clusters para garantir uma detecção mais rápida durante as janelas de manutenção. Finalmente, estamos melhorando a forma como nos comunicamos durante a manutenção que é longa, incluindo uma página de status mais oportuna e atualizações de progresso/completo. Para perguntas sobre confiabilidade de fluxos de trabalho ou roteiro, sua equipe de contas Okta pode ajudar. Duração Total Duração Total (Minutos): 258 minutos (4 horas e 18 minutos) Tempo de início: 5:15 PDT Tempo de fim: 9:33 PDT Duração (# de minutos): 258 minutos

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gouere 2026 da 21:23 UTCresolved

   Nossa equipe de engenharia aplicou uma correção potencial ao ambiente de visualização impactado e está monitorando ativamente o sistema para recuperação. Forneceremos outra atualização dentro de 30 minutos, ou mais cedo se novas informações estiverem disponíveis. Pedimos sinceras desculpas por qualquer inconveniente.

2. 13 Gouere 2026 da 21:39 UTCresolved

   Nossa equipe de engenharia aplicou uma correção, e estamos observando restauração de serviço em nosso ambiente de visualização OP2. Estamos acompanhando de perto o sistema e forneceremos outra atualização dentro de 30 minutos.

3. 13 Gouere 2026 da 21:53 UTCresolved

   Confirmámos que o ambiente de pré-visualização da OP2 se estabilizou totalmente, e a questão anterior está completamente resolvida. Informação adicional da causa raiz estará disponível dentro de cinco dias úteis.

4. 21 Gouere 2026 da 01:57 UTCresolved

   Nós sinceramente pedimos desculpas por qualquer impacto que este incidente causou para você, seu negócio e seus clientes. Em Okta, confiança e transparência são nossas principais prioridades. Abaixo estão os fatos sobre este incidente. Estamos empenhados em implementar melhorias no serviço para evitar futuras ocorrências deste incidente. Detecção e Impacto: No dia 13 de julho de 2026 às 01:01 PM PT, o monitoramento interno da Okta alertou nossa equipe para erros elevados no ambiente de Preview Cell da EMEA. Durante este período, todos os clientes no ambiente de Preview Cell da EMEA foram afetados, experimentando falhas de autenticação e lentidão do serviço. Administradores e usuários finais podem ter encontrado mensagens de "Erro no Servidor Interno" e outros erros ao tentar entrar ou acessar serviços Okta. Resumo da causa raiz: O incidente foi acionado durante uma atualização programada do serviço. Uma configuração incorreta fez com que o cluster de células de visualização da EMEA recebesse inadvertidamente uma versão incorreta de um componente crítico de roteamento de infraestrutura. Esta atualização quebrou o roteamento de rede interna, o que impediu a comunicação entre componentes de infraestrutura saudáveis. Como as solicitações não puderam chegar ao aplicativo principal, resultou em erros de serviço generalizados e falhas de autenticação. Passos de Remediação: A equipe de engenharia da Okta identificou o problema e imediatamente começou a implantar a versão anterior e estável da configuração de roteamento. Após o retorno, os engenheiros reiniciaram sistematicamente os serviços afetados (incluindo gateways e proxies) para restaurar a conectividade interna. Essas ações abordaram com sucesso a questão e o impacto do cliente foi totalmente atenuado pelas 2:20 PM PT. Ações Preventivas: Estamos refinando nossos processos operacionais para melhorar a estabilidade do serviço. Isso inclui o trabalho contínuo para melhorar as capacidades de detecção e monitoramento de automóveis, ajudando-nos a identificar e resolver problemas potenciais de forma mais eficaz. Duração Total (Minutos): 79 minutos (1 hora 19 minutos) Hora de início: 1:01 PM PT Hora de fim: 2:20 PM PT

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Gouere 2026 da 20:50 UTCresolved

   A engenharia Okta identificou um problema que afeta Okta Workflows e atualmente está tomando medidas para corrigir. Os clientes podem ver 500 erros ou timeouts no console Okta Workflows, terminais de API e webhooks de entrada. Nós forneceremos outra atualização dentro dos próximos 30 minutos, ou mais cedo se informações adicionais estiverem disponíveis.

2. 7 Gouere 2026 da 21:03 UTCresolved

   O problema com Okta Workflows foi resolvido. Todos os fluxos de trabalho estão agora a processar normalmente. Uma análise de causa raiz (RCA) será postada aqui dentro de cinco dias úteis. Pedimos desculpa por qualquer inconveniente que isto possa ter causado.

3. 15 Gouere 2026 da 15:22 UTCresolved

   Pedimos sinceras desculpas por qualquer impacto que este incidente possa ter causado a você, ao seu negócio ou aos seus clientes. Em Okta, confiança e transparência são nossas principais prioridades. Abaixo estão os fatos sobre este incidente. Estamos empenhados em implementar melhorias no serviço para evitar futuras ocorrências deste incidente. Detecção e Impacto: Em 7 de julho de 2026, às 01:01 PM PDT, o monitoramento interno da Okta e os relatórios dos clientes alertaram nossa equipe para problemas com usuários acessando fluxos de trabalho na célula Okta OK14 na América do Norte. Durante este período, os clientes no FL14 podem ter experimentado erros HTTP 500, 503 ou 504 Gateway Timeout ao navegar para Workflows do portal de administração ou tentar fazer login no Workflows Console via SSO. As sessões existentes podem ter errado intermitentemente. Fluxos de trabalho agendados e sob demanda, ganchos em linha e webhooks podem ter experimentado erros e timeouts. Além disso, execuções em voo experimentaram timeouts. Resumo da causa raiz: Este incidente ocorreu durante a implantação planejada da liberação 2027.07.0 para a célula FL14. No decorrer do processo de implantação, um módulo de serviço responsável pela execução de atualizações de esquema foi encerrado prematuramente. Esta terminação precoce levou a conexões inesperadas de banco de dados de longa duração, o que acabou por causar exaustão de conexão no banco de dados primário da célula. Etapas de Remediação: Ao receber alertas e relatórios de clientes, a equipe iniciou o diagnóstico às 12:44 PM PDT. Até 1:30 PDT, eles isolaram e removeram o módulo de serviço realizando atualizações de esquema. Isto permitiu que as conexões do banco de dados para limpar, restaurando serviço completo até 1:45 PDT. Ações Preventivas: Para evitar ocorrências futuras, a Okta está empenhada em fortalecer nossa estabilidade de infraestrutura e melhorar nossas capacidades de monitoramento. Atualmente estamos implementando melhorias estratégicas em nossos processos de implantação e alertando os sistemas para garantir detecção, resposta e maior resiliência em nossos serviços. Duração total: 67 minutos

Traduzido automaticamente da atualização oficial do incidente.

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

3. 30 Mezheven 2026 da 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 Gouere 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 11:21 UTCresolved

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

2. 2 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 18:40 UTCresolved

1. 22 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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 Genver 2026 da 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.