Address
:
[go:
up one dir
,
main page
]
Include Form
Remove Scripts
Accept Cookies
Show Images
Show Referer
Rotate13
Base64
Strip Meta
Strip Title
Session Cookies
Okta Status | System Status
[{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001dgs2AA"},"Id":"a9CWR0000001dgs2AA","Name":"I-10318","Duration__c":0,"Log__c":"Okta Engineering team became aware of the third-party issue that impacted access to support.okta.com and status.okta.com, and confirmed that the third-party provider has resolved the issue and services are restored. A root cause analysis (RCA) will be posted here within five business days. We apologize for any inconvenience this may have caused.","Status__c":"Resolved","Start_Date__c":"2026-03-16","End_Date__c":"2026-03-16","Last_Updated__c":"2026-03-24T23:32:25.000+0000","LastModifiedDate":"2026-03-24T23:32:25.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Third Party Issue impacted support.okta.com","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17;okta.com:18;okta.com:19","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Start_Time__c":"2026-03-16T08:42:00.000+0000","CreatedDate":"2026-03-17T06:37:46.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001dSM2AY"},"Id":"a9CWR0000001dSM2AY","Name":"I-10300","Duration__c":0,"Log__c":"At 10:30 AM PT on 3/13/2026, the Okta Engineering team became aware of an impact to the Okta Admin Console. affecting customers on OK1 and EU1 cells. During this time, customers may not be able to view all the users. The Okta Engineering team is investigating and working to mitigate the issue as soon as possible. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2026-03-13","End_Date__c":"2026-03-13","Last_Updated__c":"2026-03-20T20:35:05.000+0000","LastModifiedDate":"2026-03-20T20:35:05.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Okta Admin Console Issue Viewing Users","Impacted_Cells__c":"okta-emea.com:1;okta.com:1","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2026-03-13T18:40:00.000+0000","CreatedDate":"2026-03-13T18:31:02.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001b5a2AA"},"Id":"a9CWR0000001b5a2AA","Name":"I-10096","Duration__c":120,"Log__c":"At 04/02/2026 02:41 PT, the team became aware of an issue with to our service affecting customers in EMEA Cell 9. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2026-02-04","End_Date__c":"2026-02-04","Last_Updated__c":"2026-02-11T18:45:50.000+0000","LastModifiedDate":"2026-02-11T18:45:50.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Customer may notice Okta LDAPi issues in Okta Cell OK9.","Impacted_Cells__c":"okta.com:9","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2026-02-04T10:41:00.000+0000","CreatedDate":"2026-02-04T12:19:29.000+0000","CurrencyIsoCode":"GBP"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001SlS2AU"},"Id":"a9CWR0000001SlS2AU","Name":"I-10062","Duration__c":0,"Log__c":"Okta is aware of the intermittent latency and connection issues affecting OK9 at approximately 07:30 AM PT due to a service disruption in one of the third-party providers. The provider reports early signs of recovery and recommends that users continue retrying failed requests, as success rates are expected to improve steadily. We are monitoring the situation closely and will provide further updates as we move toward full mitigation.","Status__c":"Resolved","Start_Date__c":"2026-01-28","Last_Updated__c":"2026-02-11T18:41:00.000+0000","LastModifiedDate":"2026-02-11T18:41:00.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Intermittent Latency and Connection Issues in OK9","Impacted_Cells__c":"okta.com:9","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Third Party","Start_Time__c":"2026-01-28T15:30:00.000+0000","CreatedDate":"2026-01-28T19:03:42.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001HBi2AM"},"Id":"a9CWR0000001HBi2AM","Name":"I-10028","Duration__c":535,"Log__c":"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.","Status__c":"Resolved","Start_Date__c":"2026-01-22","Last_Updated__c":"2026-01-30T22:35:35.000+0000","LastModifiedDate":"2026-01-30T22:35:35.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Email Delivery Issues","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17;okta.com:18;okta.com:19","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2026-01-22T18:55:00.000+0000","CreatedDate":"2026-01-22T20:47:46.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000012EI2AY"},"Id":"a9CWR00000012EI2AY","Name":"I-9810","Duration__c":136,"Log__c":"At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-12-03","Last_Updated__c":"2026-01-26T20:26:28.000+0000","LastModifiedDate":"2026-01-26T20:26:28.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issues with Custom Domain in Cell OK7","Impacted_Cells__c":"okta.com:7","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-03T13:15:00.000+0000","CreatedDate":"2025-12-03T13:29:19.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oMJE2A2"},"Id":"a9CKZ000000oMJE2A2","Name":"I-9723","Duration__c":360,"Log__c":"Our Engineering team became aware of delivery delays in SMS MFA affecting US customers across all cells. Okta continues to monitor the current situation with our third-party provider. We recommend using alternative verification methods at this time.","Status__c":"Resolved","Start_Date__c":"2025-11-12","End_Date__c":"2025-11-13","Last_Updated__c":"2026-01-26T20:25:34.000+0000","LastModifiedDate":"2026-01-26T20:25:34.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"SMS Delivery Issues","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"MFA","Start_Time__c":"2025-11-12T19:40:00.000+0000","CreatedDate":"2025-11-12T19:45:50.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR0000001Gty2AE"},"Id":"a9CWR0000001Gty2AE","Name":"I-10002","Duration__c":1539,"Log__c":"At 1/20/2026 7:14 AM PT, Okta teams are aware of issues currently affecting Google Workspace imports. Admins may see \"Unexpected Error\" or \"Missing Required Field\" notifications within their dashboard. Our teams are investigating the root cause, and we will post another update in 30 minutes or sooner with more details.","Status__c":"Resolved","Start_Date__c":"2026-01-20","Last_Updated__c":"2026-01-26T18:34:41.000+0000","LastModifiedDate":"2026-01-26T18:34:41.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Service Disruption in Google Workspace Imports","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2026-01-19T18:10:00.000+0000","CreatedDate":"2026-01-20T15:42:50.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000017982AA"},"Id":"a9CWR00000017982AA","Name":"I-9905","Duration__c":136,"Log__c":"Around 3:30 AM PT on December 26, 2025, the Engineering team became aware of an issue affecting customers on Ok6 cells. We temporarily put the cell in read-only mode. During this time, customers on OK6 were still able to log in and access apps, but could not create or modify any data, users, or settings. \r\nThe issue has been resolved at 5:43 AM PST. Additional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2025-12-26","End_Date__c":"2025-12-26","Last_Updated__c":"2026-01-03T01:52:45.000+0000","LastModifiedDate":"2026-01-03T01:52:45.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"OK6 Okta Dashboard Access","Impacted_Cells__c":"okta.com:6","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-26T08:30:00.000+0000","CreatedDate":"2025-12-26T14:13:07.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000016Ze2AI"},"Id":"a9CWR00000016Ze2AI","Name":"I-9868","Duration__c":1140,"Log__c":"At 12/14/2025 3:00 AM PT, the Okta Engineering team became aware of an intermittent issue with email being sent through Custom Email Domains. This is affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 7, EMEA Cell 9, US Cell 12, US Cell 14, US Preview 3. Our team is actively investigating this issue and working with our third-party vendor to address the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-12-14","End_Date__c":"2025-12-14","Last_Updated__c":"2025-12-23T14:50:22.000+0000","LastModifiedDate":"2025-12-23T14:50:22.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Custom Domain Email Delivery Issues","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:7;okta.com:9;okta.com:12;oktapreview.com:3;okta.com:14","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-14T11:00:00.000+0000","CreatedDate":"2025-12-14T16:02:33.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000015s62AA"},"Id":"a9CWR00000015s62AA","Name":"I-9840","Duration__c":102,"Log__c":"Okta Engineering became aware of an increase in connections on custom domain routers affecting customers in Cell OK9. Our team is actively investigating this issue to determine the root cause and mitigate the impact.\r\n\r\nDuring this time, users accessing their Okta tenant via custom domains may experience intermittent connectivity issues, including timeouts, latency, or 503/504 error messages.\r\n\r\nWe will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-12-09","End_Date__c":"2025-12-10","Last_Updated__c":"2025-12-18T02:29:01.000+0000","LastModifiedDate":"2025-12-18T02:29:01.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Users in some orgs are unable to reach Custom URL domain","Impacted_Cells__c":"okta.com:9","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-10T07:42:00.000+0000","CreatedDate":"2025-12-10T08:41:50.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000012HW2AY"},"Id":"a9CWR00000012HW2AY","Name":"I-9812","Duration__c":75,"Log__c":"At 12/4/2025 12:31 AM PT, the team became aware of an issue with our LDAPi service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, and EMEA Cell 1. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue. We will provide another update within the next 30 minutes.","Status__c":"Resolved","Start_Date__c":"2025-12-04","Last_Updated__c":"2025-12-12T16:32:03.000+0000","LastModifiedDate":"2025-12-12T16:32:03.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"LDAP interface connectivity issues","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-04T08:31:00.000+0000","CreatedDate":"2025-12-04T08:41:36.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000012Cg2AI"},"Id":"a9CWR00000012Cg2AI","Name":"I-9808","Duration__c":42,"Log__c":"At 12/3/2025 12:35 AM PT, the Okta engineering team has taken service protection actions, and the service is now stable. \r\nAdditional root cause information will be available within five business days.","Status__c":"Resolved","Start_Date__c":"2025-12-02","End_Date__c":"2025-12-03","Last_Updated__c":"2025-12-10T07:55:57.000+0000","LastModifiedDate":"2025-12-10T07:55:57.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issues with Custom Domain in Cell OK7","Impacted_Cells__c":"okta.com:7","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-12-03T06:22:00.000+0000","CreatedDate":"2025-12-03T07:18:35.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CWR00000011QI2AY"},"Id":"a9CWR00000011QI2AY","Name":"I-9754","Duration__c":11,"Log__c":"We detected a service interruption that impacted all users for approximately 10 minutes at 10:34 AM PT. Users may have encountered intermittent delays, connection errors, or 503/504 error messages. The issue is no longer active. We are monitoring for residual effects and will provide an update in the next 30 minutes.","Status__c":"Resolved","Start_Date__c":"2025-11-17","Last_Updated__c":"2025-11-25T00:21:36.000+0000","LastModifiedDate":"2025-11-25T00:21:36.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Service Disruption on OK14","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-11-17T18:34:00.000+0000","CreatedDate":"2025-11-17T19:12:35.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oMAj2AM"},"Id":"a9CKZ000000oMAj2AM","Name":"I-9587","Duration__c":0,"Log__c":"We are investigating issues with our authentication service that are causing intermittent login problems with OktaVerify. Our initial findings suggest a conflict related to a recently installed third-party patch. Our team is actively working to gather more details, and we will provide updates in the next 30 minutes.","Status__c":"Resolved","Start_Date__c":"2025-10-15","Last_Updated__c":"2025-11-24T17:09:59.000+0000","LastModifiedDate":"2025-11-24T17:09:59.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Intermittent Okta Verify login issues","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"MFA;Single Sign-On","Start_Time__c":"2025-10-15T18:30:00.000+0000","CreatedDate":"2025-10-15T18:41:23.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oMAo2AM"},"Id":"a9CKZ000000oMAo2AM","Name":"I-9623","Duration__c":1138,"Log__c":"At 20/10/2025 00:15 PT, We're currently experiencing technical difficulties for workflows that are related to an issue with an upstream provider. We're working with the vendor and will provide updates in the next 30 minutes","Status__c":"Resolved","Start_Date__c":"2025-10-20","End_Date__c":"2025-10-20","Last_Updated__c":"2025-11-24T17:06:19.000+0000","LastModifiedDate":"2025-11-24T17:06:19.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Service issues affecting multiple services","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11;okta.com:12;okta.com:14","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-10-20T06:48:00.000+0000","CreatedDate":"2025-10-20T08:00:26.000+0000","CurrencyIsoCode":"GBP"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oMJ92AM"},"Id":"a9CKZ000000oMJ92AM","Name":"I-9665","Duration__c":530,"Log__c":"We are aware that some services may be degraded as our third-party vendors are currently experiencing issues. We are actively investigating the scope of the impact and coordinating closely with our providers on a resolution. We will provide an update as soon as more information is available.","Status__c":"Resolved","Start_Date__c":"2025-10-29","End_Date__c":"2025-10-29","Last_Updated__c":"2025-11-05T18:55:08.000+0000","LastModifiedDate":"2025-11-05T18:55:08.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Service Degradation on Multiple Services","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"API Services","Start_Time__c":"2025-10-29T18:40:00.000+0000","CreatedDate":"2025-10-29T18:40:44.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oM2E2AU"},"Id":"a9CKZ000000oM2E2AU","Name":"I-9571","Duration__c":90,"Log__c":"On September 24, 2025, customers may have experienced increased latency and repeated retries when running Google imports, which led us to recommend pausing all imports via an admin banner. We have confirmed that the disruption was caused by our third-party provider, and the issue has since been fully resolved. There is no active impact, services are operating normally, and no further action is required from customers. We are collaborating with our provider to complete a comprehensive root cause analysis and will provide it here.","Status__c":"Resolved","Start_Date__c":"2025-09-24","Last_Updated__c":"2025-10-31T00:54:28.000+0000","LastModifiedDate":"2025-10-31T00:54:28.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Latency Issue Affecting Google Imports","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-09-24T16:00:00.000+0000","CreatedDate":"2025-10-09T21:26:39.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oM1u2AE"},"Id":"a9CKZ000000oM1u2AE","Name":"I-9557","Duration__c":0,"Log__c":"Since September 22, 2025, the Okta Workflows Google Sheets connector has been intermittently returning 'Invalid Input' errors and/or exhibiting unexpected behavior on the New Row event and the Create Row, Read Row, and Read All Rows actions. Other cards may also be impacted. Our teams are actively investigating the root cause and working on a resolution with our third-party provider. We will provide an update as soon as more information is available.","Status__c":"Resolved","Start_Date__c":"2025-09-22","Last_Updated__c":"2025-10-27T23:00:28.000+0000","LastModifiedDate":"2025-10-27T23:00:28.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Intermittent Failures Affecting Google Sheets Workflows","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-09-22T20:23:00.000+0000","CreatedDate":"2025-10-01T21:31:20.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oM1z2AE"},"Id":"a9CKZ000000oM1z2AE","Name":"I-9563","Duration__c":0,"Log__c":"We have identified an issue with the Google Groups Query API, which is returning inconsistent or incomplete group data. This transient API issue can result in unintended group deletion of those groups in Okta.\r\n\r\nAs a workaround, we have implemented a protective measure to prevent accidental deletion during group imports from Google. When a large volume of group deletions is detected, the import is stopped to protect against importing bad data. Customers with a verified, legitimate need for a mass deletion can contact Support to enable a temporary override for this limit.\r\n\r\nOur team is collaborating with our third-party provider to implement a permanent fix, and a Root Cause Analysis will be forthcoming.","Status__c":"Resolved","Start_Date__c":"2025-09-22","End_Date__c":"2025-10-03","Last_Updated__c":"2025-10-23T02:52:10.000+0000","LastModifiedDate":"2025-10-23T02:52:10.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Intermittent import issue with Google Groups Query API","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-09-22T18:21:00.000+0000","CreatedDate":"2025-10-03T07:05:43.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oM2J2AU"},"Id":"a9CKZ000000oM2J2AU","Name":"I-9573","Duration__c":10,"Log__c":"We detected a service interruption that impacted all users for approximately 10 minutes starting at 4:14 PM PDT. Users may have encountered intermittent delays, connection errors, or 503/504 error messages. The issue is no longer active. We are monitoring for residual effects and will provide an update in the next 30 minutes.","Status__c":"Resolved","Start_Date__c":"2025-10-09","Last_Updated__c":"2025-10-17T21:49:37.000+0000","LastModifiedDate":"2025-10-17T21:49:37.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Service Disruption on OK14","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-10-09T23:14:00.000+0000","CreatedDate":"2025-10-09T23:58:25.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oLxh2AE"},"Id":"a9CKZ000000oLxh2AE","Name":"I-9545","Duration__c":1125,"Log__c":"At 9/22/2025 5:30 AM PT, the Workflows Automation and Extensibility team became aware of an issue with connectivity to our Workflows service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, US Preview 1, EMEA Preview 2, US Preview 3, EMEA Cell 1. Our team is actively investigating this issue and performing configurational changes to mitigate the issue. We will provide another update within the next 1 hour, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-09-22","End_Date__c":"2025-09-22","Last_Updated__c":"2025-10-07T23:28:08.000+0000","LastModifiedDate":"2025-10-07T23:28:08.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Google Sheets Workflows connector not working","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-09-22T12:30:00.000+0000","CreatedDate":"2025-09-22T12:32:23.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZgOEAW"},"Id":"a9C4z000001BZgOEAW","Name":"I-8983","Duration__c":326,"Log__c":"Okta is currently experiencing an issue with the service. We are actively investigating and will update this message with more information as soon as we have it.","Status__c":"Resolved","Start_Date__c":"2024-12-13","Last_Updated__c":"2025-09-10T19:52:17.000+0000","LastModifiedDate":"2025-09-10T19:52:17.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"HTTP 429 on login.okta.com","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-12-13T14:47:00.000+0000","CreatedDate":"2024-12-13T14:49:47.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZg9EAG"},"Id":"a9C4z000001BZg9EAG","Name":"I-8973","Duration__c":78,"Log__c":"Okta is currently experiencing an issue with end-user and admin logins. We are actively investigating and will update this message with more information as soon as we have it.","Status__c":"Resolved","Start_Date__c":"2024-12-11","End_Date__c":"2024-12-11","Last_Updated__c":"2025-09-10T19:51:44.000+0000","LastModifiedDate":"2025-09-10T19:51:44.000+0000","Category__c":"Major Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issue with end-user and admin logins","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:8;okta.com:16","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-12-11T18:32:00.000+0000","CreatedDate":"2024-12-11T19:07:14.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXInEAO"},"Id":"a9C4z000000TXInEAO","Name":"I-8909","Duration__c":272,"Log__c":"Okta Engineering implemented mitigating actions and restored the connectivity impacting some users in OK6. Okta Engineering will continue monitoring. Additional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-11-14","Last_Updated__c":"2025-09-10T19:51:18.000+0000","LastModifiedDate":"2025-09-10T19:51:18.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Issue with requests to US Cell OK6 from a specific geo location","Impacted_Cells__c":"okta.com:6","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-11-15T03:02:00.000+0000","CreatedDate":"2024-11-15T03:07:27.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZecEAG"},"Id":"a9C4z000001BZecEAG","Name":"I-8920","Duration__c":0,"Log__c":"At 8:40am on November 19th PST, the OIN team became aware of an Import issue with the Paylocity OIN integration affecting customers on all cells of the Okta Workforce Identity Cloud environment. During this time customers may experience import roadblocks. Okta recommends not running imports from Paylocity during this investigation.\r\n\r\nOkta Engineering is investigating and working to resolve this as quickly as possible.\r\nWe’ll provide an update in 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2024-11-19","End_Date__c":"2024-11-19","Last_Updated__c":"2025-09-10T19:48:47.000+0000","LastModifiedDate":"2025-09-10T19:48:47.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Paylocity Import Issue","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"API Products","Service_Feature__c":"Third Party","Start_Time__c":"2024-11-19T19:56:00.000+0000","CreatedDate":"2024-11-19T19:58:24.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZdAEAW"},"Id":"a9C4z000001BZdAEAW","Name":"I-8864","Duration__c":271,"Log__c":"Okta is currently experiencing an issue with the service. We are actively investigating and will update this message with more information as soon as we have it.","Status__c":"Resolved","Start_Date__c":"2024-10-28","Last_Updated__c":"2025-09-10T19:48:07.000+0000","LastModifiedDate":"2025-09-10T19:48:07.000+0000","Category__c":"Performance Issue","Is_Mis_Red__c":false,"Incident_Title__c":"Jobs Slow to Process","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-10-28T13:15:00.000+0000","CreatedDate":"2024-10-28T14:47:03.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZcREAW"},"Id":"a9C4z000001BZcREAW","Name":"I-8828","Duration__c":9884,"Log__c":"At 12:52 PM PDT on October 10, 2024, the Engineering team became aware of a provisioning setup issue with Office365 affecting customers on all cells. SSO and federation services are not impacted.\r\n\r\nThe Engineering team is investigating the root cause to mitigate the issue. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2024-10-10","End_Date__c":"2024-10-10","Last_Updated__c":"2025-09-10T19:47:43.000+0000","LastModifiedDate":"2025-09-10T19:47:43.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"O365 OIN Provisioning Setup Issue","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-10-03T22:38:00.000+0000","CreatedDate":"2024-10-10T20:22:35.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZcHEAW"},"Id":"a9C4z000001BZcHEAW","Name":"I-8826","Duration__c":553,"Log__c":"Okta has identified an issue with the latest Datadog app integration version used for SSO. Okta's Engineering Team is working to roll back the app update.\r\n\r\nWe’ll provide an update in 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2024-10-03","Last_Updated__c":"2025-09-10T19:46:50.000+0000","LastModifiedDate":"2025-09-10T19:46:50.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Issue with Datadog app integration update","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Single Sign-On","Start_Time__c":"2024-10-03T22:50:00.000+0000","CreatedDate":"2024-10-03T23:01:53.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZcCEAW"},"Id":"a9C4z000001BZcCEAW","Name":"I-8825","Duration__c":17882,"Log__c":"At 2:53pm PT on September 23rd, Okta's Engineering Team became aware of an O365 federation issue on all cells affecting customers federating new domains. During this time, customers federating new domains may experience a '400 Bad Request' error. Okta is documenting a workaround and developing a hotfix release to mitigate the issue. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2024-09-23","End_Date__c":"2024-09-24","Last_Updated__c":"2025-09-10T19:46:35.000+0000","LastModifiedDate":"2025-09-10T19:46:35.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"400 Bad Request Error when federating new domains","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-09-23T22:32:00.000+0000","CreatedDate":"2024-09-23T22:44:02.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZc7EAG"},"Id":"a9C4z000001BZc7EAG","Name":"I-8824","Duration__c":2728,"Log__c":"Okta is currently experiencing an issue with the service. We are actively investigating and will update this message with more information as soon as we have it.","Status__c":"Resolved","Start_Date__c":"2024-09-19","End_Date__c":"2024-09-19","Last_Updated__c":"2025-09-10T19:46:08.000+0000","LastModifiedDate":"2025-09-10T19:46:08.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Disruptions to Okta Verify Enrollment","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"MFA","Start_Time__c":"2024-09-19T15:10:00.000+0000","CreatedDate":"2024-09-19T15:14:15.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZbnEAG"},"Id":"a9C4z000001BZbnEAG","Name":"I-8812","Duration__c":1495,"Log__c":"At 10:00 AM PDT on September 17, 2024, our engineering team became aware of an issue impacting the Okta Sign-in Widget (SIW) for some end users using an embedded Internet Explorer browser. During this time, the end user may experience a popup message that says, \"An error has occurred in the script on this page.\" Our engineering has reverted the change, and we are in the process of confirming the resolution.","Status__c":"Resolved","Start_Date__c":"2024-09-17","End_Date__c":"2024-09-17","Last_Updated__c":"2025-09-10T19:44:12.000+0000","LastModifiedDate":"2025-09-10T19:44:12.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Sign-in Widget (SIW) issue when using embedded Internet Explorer","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-09-17T18:20:00.000+0000","CreatedDate":"2024-09-17T18:23:24.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIiEAO"},"Id":"a9C4z000000TXIiEAO","Name":"I-8813","Duration__c":148,"Log__c":"Okta has received multiple reports of SMS delivery issues affecting users in China. Okta's Engineering team is actively investigating. At this time, we recommend that customers in China use a secondary MFA option if available.","Status__c":"Resolved","Start_Date__c":"2024-09-17","End_Date__c":"2024-09-17","Last_Updated__c":"2025-09-10T19:43:35.000+0000","LastModifiedDate":"2025-09-10T19:43:35.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"SMS delivery issues in China","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"MFA","Start_Time__c":"2024-09-18T02:11:00.000+0000","CreatedDate":"2024-09-18T02:15:06.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZakEAG"},"Id":"a9C4z000001BZakEAG","Name":"I-8758","Duration__c":57,"Log__c":"Our Workflows team is investigating the issue impacting Workflows execution for a subset of Okta cells (US-Cell 1, 2, 3, 4, 6, 7, & 11). During this time, Okta Admins may experience slowness or time-outs on running the flows. Our Workflows team is performing corrective actions to mitigate the issues related to this degradation.\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\r\n\r\n3:29pm PDT: Our Workflows team continues to address the timeouts in Workflows executions for a subset of Okta US Cells with top priority. The team has identified the potential root cause and managing to adjust the configuration to mitigate the issue in the FL1 service.\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.\r\n\r\n3:32pm PDT: The issue impacting FL1 has been addressed. Okta’s monitoring shows recovery to normal conditions.\r\n\r\nAdditional root cause information will be available within 5 business days.","Status__c":"Resolved","Start_Date__c":"2024-08-08","Last_Updated__c":"2025-09-09T17:44:01.000+0000","LastModifiedDate":"2025-09-09T17:44:01.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows issue","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-08-08T22:17:00.000+0000","CreatedDate":"2024-08-08T22:20:21.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIdEAO"},"Id":"a9C4z000000TXIdEAO","Name":"I-8759","Duration__c":245,"Log__c":"At 12:00 AM PST on August 13, 2024, Okta became aware of Directory Agents connectivity issues resulting in 503 and 504 errors and affecting imports and Delauth. This issue has been resolved. Okta took corrective action to resolve the service interruption.\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-08-13","End_Date__c":"2024-08-13","Last_Updated__c":"2025-09-09T17:42:47.000+0000","LastModifiedDate":"2025-09-09T17:42:47.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Directory agents connection issues on OK14","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-08-13T07:00:00.000+0000","CreatedDate":"2024-08-13T10:08:11.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIYEA4"},"Id":"a9C4z000000TXIYEA4","Name":"I-8743","Duration__c":235,"Log__c":"Okta has received reports of SMS delivery issues affecting users in China. Okta’s Engineering team is actively investigating. At this time, we recommend that customers in China use a secondary MFA option if available.","Status__c":"Resolved","Start_Date__c":"2024-08-06","End_Date__c":"2024-08-06","Last_Updated__c":"2025-09-09T17:42:06.000+0000","LastModifiedDate":"2025-09-09T17:42:06.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"SMS delivery issues in China","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"MFA","Start_Time__c":"2024-08-07T05:01:00.000+0000","CreatedDate":"2024-08-07T05:05:01.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000sXz12AE"},"Id":"a9CKZ000000sXz12AE","Name":"I-9493","Duration__c":443,"Log__c":"At 8/18/2025 5:00 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting some customers. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-08-18","End_Date__c":"2025-08-18","Last_Updated__c":"2025-08-25T20:39:27.000+0000","LastModifiedDate":"2025-08-25T20:39:27.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Certain users are unable to access their Okta domain.","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-08-18T11:06:00.000+0000","CreatedDate":"2025-08-18T15:17:02.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ0000011DxR2AU"},"Id":"a9CKZ0000011DxR2AU","Name":"I-9481","Duration__c":1,"Log__c":"An issue impacting third party provider(s) regarding import slowness has been resolved. Additional root cause information will be available within 5 business days.","Status__c":"Resolved","Start_Date__c":"2025-08-13","End_Date__c":"2025-08-13","Last_Updated__c":"2025-08-20T23:29:00.000+0000","LastModifiedDate":"2025-08-20T23:29:00.000+0000","Category__c":"Performance Issue","Is_Mis_Red__c":false,"Incident_Title__c":"Import slowness related to third-party provider","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16","Impacted_Audience__c":"Admin","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-08-08T09:28:00.000+0000","CreatedDate":"2025-08-13T17:15:52.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ0000011Dws2AE"},"Id":"a9CKZ0000011Dws2AE","Name":"I-9464","Duration__c":454,"Log__c":"At 8/1/2025 7:29 AM PT, the Workflows Automation and Extensibility team became aware of an issue with timeouts to our service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, US Cell 11. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-08-01","Last_Updated__c":"2025-08-11T20:13:28.000+0000","LastModifiedDate":"2025-08-11T20:13:28.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows delayed and timing out.","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11;okta.com:14","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-08-01T14:29:00.000+0000","CreatedDate":"2025-08-01T15:35:02.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ0000011DwJ2AU"},"Id":"a9CKZ0000011DwJ2AU","Name":"I-9447","Duration__c":126,"Log__c":"At 7/22/2025 11:30 AM PT, the Core Identity team became aware of an issue with authentication to our Core Platform service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, APJ Cell 1, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, US Preview 1, EMEA Preview 2, US Preview 3, EMEA Cell 1. During this time, admins may notice some users that should be auto-activated stuck in 'Pending User Action' status. Our team is actively investigating this issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-07-22","End_Date__c":"2025-07-22","Last_Updated__c":"2025-07-30T00:03:37.000+0000","LastModifiedDate":"2025-07-30T00:03:37.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Users that should be auto-activated are set in a 'pending action' status.","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-07-22T18:00:00.000+0000","CreatedDate":"2025-07-22T18:44:36.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000sXyI2AU"},"Id":"a9CKZ000000sXyI2AU","Name":"I-9385","Duration__c":85,"Log__c":"Android Okta Verify end-users may not receive push notifications due to a third-party outage. Launching Android Okta Verify manually will allow authentication. Okta will provide an update as it becomes available.","Status__c":"Resolved","Start_Date__c":"2025-06-12","End_Date__c":"2025-06-12","Last_Updated__c":"2025-06-25T20:09:48.000+0000","LastModifiedDate":"2025-06-25T20:09:48.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Push Notifications for Android users are not received","Impacted_Cells__c":"okta.com:6;okta.com:9;okta.com:11","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Start_Time__c":"2025-06-12T17:50:00.000+0000","CreatedDate":"2025-06-12T18:39:15.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oLp72AE"},"Id":"a9CKZ000000oLp72AE","Name":"I-9383","Duration__c":18,"Log__c":"At 6:09 PM PST on June 11, 2025, Okta became aware of an issue with our service affecting customers in US Cell 6, APAC Cell 8. This issue has been resolved. Okta took corrective action to resolve the service interruption. The service was fully restored at 6:23 PM PST.\r\n\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2025-06-11","End_Date__c":"2025-06-11","Last_Updated__c":"2025-06-18T22:42:56.000+0000","LastModifiedDate":"2025-06-18T22:42:56.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Service Degradation on Multiple Cells","Impacted_Cells__c":"okta.com:6;okta.com:8","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-06-12T01:09:00.000+0000","CreatedDate":"2025-06-12T03:35:42.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oLp22AE"},"Id":"a9CKZ000000oLp22AE","Name":"I-9381","Duration__c":12,"Log__c":"At 6/11/2025 11:13 AM PT, the Okta Engineering team became aware of an issue with our service affecting customers in US Cell 4, US Cell 6, US Cell 7, US Cell 11, JP Cell 16. During this time, users may be experiencing elevated error rates within our system when attempting to connect to Okta service. Our team is actively investigating to mitigate the issue. We will provide another update within the next hour, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-06-11","Last_Updated__c":"2025-06-18T22:35:44.000+0000","LastModifiedDate":"2025-06-18T22:35:44.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Service Degradation on Multiple Cells","Impacted_Cells__c":"okta.com:4;okta.com:6;okta.com:7;okta.com:11;okta.com:16","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-06-11T18:13:00.000+0000","CreatedDate":"2025-06-11T18:38:47.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000sXyD2AU"},"Id":"a9CKZ000000sXyD2AU","Name":"I-9379","Duration__c":0,"Log__c":"We have identified an issue with Okta Personal where end users are unable use the application","Status__c":"Resolved","Start_Date__c":"2025-06-11","End_Date__c":"2025-06-11","Last_Updated__c":"2025-06-16T21:33:01.000+0000","LastModifiedDate":"2025-06-16T21:33:01.000+0000","Category__c":"Minor Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Okta Personal not available","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-06-11T18:05:00.000+0000","CreatedDate":"2025-06-11T18:09:34.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oLkp2AE"},"Id":"a9CKZ000000oLkp2AE","Name":"I-9288","Duration__c":60,"Log__c":"Okta Engineering became aware of an issue with a downstream email provider. Customers may experience errors with MFA Emails, password reset, and user activation.","Status__c":"Resolved","Start_Date__c":"2025-04-23","Last_Updated__c":"2025-04-30T16:47:04.000+0000","LastModifiedDate":"2025-04-30T16:47:04.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issue with a downstream email provider","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Start_Time__c":"2025-04-23T20:55:00.000+0000","CreatedDate":"2025-04-23T22:03:55.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000oLkk2AE"},"Id":"a9CKZ000000oLkk2AE","Name":"I-9260","Duration__c":0,"Log__c":"Okta Engineering became aware of an issue with the Apple Business Manager integration. Customers may experience errors while setting up the integration.\r\n\r\nAs of 5:54 PM PT Apple has informed us resolution of the issue","Status__c":"Resolved","Start_Date__c":"2025-04-15","End_Date__c":"2025-04-15","Last_Updated__c":"2025-04-23T22:17:50.000+0000","LastModifiedDate":"2025-04-23T22:17:50.000+0000","Category__c":"Feature Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issue with the Apple Business Manager intergration","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;API Products","Service_Feature__c":"Third Party","Start_Time__c":"2025-04-16T00:32:00.000+0000","CreatedDate":"2025-04-16T02:37:58.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9CKZ000000sXtm2AE"},"Id":"a9CKZ000000sXtm2AE","Name":"I-9238","Duration__c":107,"Log__c":"At 4/4/2025 8:00 AM PT, the team became aware of an issue with to our service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, US Cell 11, US Cell 12, US Cell 14. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next , or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-04-04","End_Date__c":"2025-04-04","Last_Updated__c":"2025-04-11T21:39:39.000+0000","LastModifiedDate":"2025-04-11T21:39:39.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Okta Identity Governance (OIG) Issue","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11;okta.com:12;okta.com:14","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"OIG Access Requests","Start_Time__c":"2025-04-04T15:00:00.000+0000","CreatedDate":"2025-04-04T16:10:59.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZi5EAG"},"Id":"a9C4z000001BZi5EAG","Name":"I-9045","Duration__c":37,"Log__c":"On 1/9/2025 10:42 AM PT, the Advanced Server Access team became aware of an issue with our Advanced Server Access service affecting customers in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, US Cell 7, US Cell 8, EMEA Cell 9, US Cell 11, US Cell 12, US Cell 14, JP Cell 16, Preview Cell 1, Preview Cell 2, and Preview Cell 3. During this time, administrators were unable to access the ASA dashboard. This issue has since been resolved.\r\n\r\nRoot cause information:\r\n\r\nWe 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.\r\n\r\nDetection and Impact:\r\n\r\nOn January 9, 2025 starting at approximately 10:42AM PT, Okta was alerted to an issue where Advanced Server Access (ASA) customers were unable to access the ASA UI console. All ASA UI actions were unavailable, including logins and administrative actions within the console. Any ASA actions via client API were unimpacted.\r\n\r\nRoot Cause Summary:\r\n\r\nOkta’s Engineering team determined the root cause of the issue was a recent update to the ASA dashboard which referenced a missing JavaScript asset. This resulted in all ASA UI access being temporarily unavailable. This did not impact client API access, server registration or other ASA resource actions.\r\n\r\nRemediation Steps & Preventative Actions:\r\n\r\nOkta identified the issue at 11:10AM PT and Okta engineering deployed the solution at 11:19AM PT, reverting to an earlier version and restoring access.\r\n\r\nOkta is adding additional automated test scenarios to prevent similar incidents from happening in the future. We will increase monitoring and implement additional sign-off during future service updates.","Status__c":"Resolved","Start_Date__c":"2025-01-09","End_Date__c":"2025-01-09","Last_Updated__c":"2025-02-24T19:21:23.000+0000","LastModifiedDate":"2025-02-24T19:21:23.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"ASA issue in all Okta Cells","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Advanced Server Access","Start_Time__c":"2025-01-09T19:32:00.000+0000","CreatedDate":"2025-01-09T19:33:49.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXJ3EAO"},"Id":"a9C4z000000TXJ3EAO","Name":"I-9131","Duration__c":993,"Log__c":"At 12/02/2025 15:08 PT, the team became aware of an issue with our service affecting customers in US Cell 14. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2025-02-12","End_Date__c":"2025-02-12","Last_Updated__c":"2025-02-21T18:20:09.000+0000","LastModifiedDate":"2025-02-21T18:20:09.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"No Access to Flows or Connections Tabs in Workflows Console","Impacted_Cells__c":"okta.com:14","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-02-12T15:08:00.000+0000","CreatedDate":"2025-02-12T15:35:44.000+0000","CurrencyIsoCode":"GBP"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIxEAO"},"Id":"a9C4z000000TXIxEAO","Name":"I-9059","Duration__c":100,"Log__c":"The Okta Workflows team became aware of missing telemetry affecting customers on OK1, OK2, OK3, OK4, OK6, OK7, and OK11 between 6pm and 1am PT on January 14th-15th, 2025.\r\n\r\nDuring this time, your flows continued to process properly. It may appear that flows did not execute during this timeframe. Telemetry processing has since been restored. \r\n\r\nRoot cause information:\r\n\r\nWe 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 incident.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn January 14th at 4:10 pm PST, Okta was alerted to an issue where 8% of Workflows execution history messages were unable to be processed in Cells OK1, OK2, OK3, OK4, OK6, OK7, OK8, OK11. This could result in the appearance that workflow executions were stalled or lost. Workflows continued to execute properly.\r\n\r\n \r\nRoot Cause Summary\r\n\r\nBased on our investigation and findings, the root cause of this issue was due to a configuration error within services managed by a 3rd party provider during a maintenance window. \r\n\r\n\r\nRemediation Steps\r\n\r\nImmediately upon receiving alerts of network disruptions, Okta Engineering escalated the issues with our provider and worked to implement internal mitigations. Okta worked directly with our provider to mitigate the issue and confirmed full service restoration. Okta's internal mitigations restored full service to the affected cells by 5:50 pm PST on January 14th. \r\n\r\n\r\nPreventative Actions\r\n\r\nOkta will continue working with our third-party service provider to enhance monitoring and expedite the detection of georegional issues with the queuing system. Additionally, we have updated our operational processes to further improve service recovery times. In parallel, we are rolling out a new, more resilient message delivery system for flow execution history data, reducing our dependency on this specific service.","Status__c":"Resolved","Start_Date__c":"2025-01-15","End_Date__c":"2025-01-15","Last_Updated__c":"2025-01-24T07:04:02.000+0000","LastModifiedDate":"2025-01-24T07:04:02.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows Telemetry issue","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2025-01-15T19:06:00.000+0000","CreatedDate":"2025-01-15T19:08:27.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZiUEAW"},"Id":"a9C4z000001BZiUEAW","Name":"I-9056","Duration__c":12,"Log__c":"At 1/14/2025 9:16 AM PST, the Core Identity team became aware of an issue with Custom Domains affecting customers in OK8. During this time, users may have experienced issues accessing resources powered by Okta custom domains. This issue has been resolved. Okta took corrective action to resolve the service interruption. The service was fully restored at 9:33 AM PST.\r\n\r\nRoot cause information:\r\n\r\nWe 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.\r\n\r\n\r\n\r\nDetection and Impact:\r\n\r\nOn January 14th at 9:22AM PT Okta internal monitoring alerts indicated errors in loading custom domains in OK Cell 8.\r\n\r\nDuring this time customers who utilize customized domains in OK Cell 8 experienced errors accessing the service.\r\n\r\n\r\n\r\nRoot Cause Summary:\r\n\r\nIn order to resolve an issue which was caught by our internal monitoring during a change the previous evening, Okta engineering staff was redeploying the edge servers. Due to a bug in the operating procedure used, the service became momentarily unavailable until corrective actions were taken to fully restore the service.\r\n\r\n\r\n\r\nRemediation Steps:\r\n\r\nAt 9:24AM PT, Okta Engineering quickly identified the issue and resolved it by placing healthy servers in service.\r\n\r\n\r\n\r\nPreventative Actions:\r\n\r\nOkta has updated the operating procedure and improved the tooling used for managing custom domain services. To ensure this does not happen again, Okta is enhancing current automated testing of this process.","Status__c":"Resolved","Start_Date__c":"2025-01-14","End_Date__c":"2025-01-14","Last_Updated__c":"2025-01-23T00:32:56.000+0000","LastModifiedDate":"2025-01-23T00:32:56.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Issues with Custom Domain in Cell OK8","Impacted_Cells__c":"okta.com:8","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2025-01-14T17:31:00.000+0000","CreatedDate":"2025-01-14T17:37:47.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIEEA4"},"Id":"a9C4z000000TXIEEA4","Name":"I-8576","Duration__c":0,"Log__c":"Out of an abundance of caution, an update was posted at 3:54am PDT. However following additional investigation, it was determined that a broad service degradation notice was not applicable.","Status__c":"Resolved","Start_Date__c":"2024-05-17","End_Date__c":"2024-05-17","Last_Updated__c":"2024-07-19T18:42:53.000+0000","LastModifiedDate":"2024-07-19T18:42:53.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":true,"Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"MFA","Start_Time__c":"2024-05-17T10:54:00.000+0000","CreatedDate":"2024-05-17T11:01:11.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZYoEAO"},"Id":"a9C4z000001BZYoEAO","Name":"I-8674","Duration__c":735,"Log__c":"Okta is currently experiencing an issue with the service. We are actively investigating and will update this message with more information as soon as we have it.","Status__c":"Resolved","Start_Date__c":"2024-06-25","End_Date__c":"2024-06-25","Last_Updated__c":"2024-07-19T18:42:25.000+0000","LastModifiedDate":"2024-07-19T18:42:25.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Okta Workflow's Google Auth Failing","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-06-25T16:41:00.000+0000","CreatedDate":"2024-06-25T16:49:30.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIOEA4"},"Id":"a9C4z000000TXIOEA4","Name":"I-8680","Duration__c":12309,"Log__c":"On July 10, Our engineering team deployed a patch for an interim resolution to improve the end user SSO experience. This patch has been applied to all Okta Production cells, and we continue to deploy it in Okta Preview cells. This approach was taken to minimize any introduction of unintended errors for users not experiencing Microsoft 365 OneDrive authentication issues. \r\n\r\nTo learn more about the SSO behavior, please visit the KBA: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive.","Status__c":"Resolved","Start_Date__c":"2024-07-02","End_Date__c":"2024-07-09","Last_Updated__c":"2024-07-19T18:42:02.000+0000","LastModifiedDate":"2024-07-19T18:42:02.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Single Sign On Issues for Microsoft O365 OneDrive","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Single Sign-On","Start_Time__c":"2024-07-02T15:00:00.000+0000","CreatedDate":"2024-07-02T15:21:04.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXITEA4"},"Id":"a9C4z000000TXITEA4","Name":"I-8711","Duration__c":276,"Log__c":"As previously noted, the issue to today’s Crowdstrike outage did not impact the Okta service, but it could have impacted any Okta Windows- related agents used. Crowdstrike has provided a workaround to the issue and instructed all customers to follow the steps found here: https://supportportal.crowdstrike.com/s/article/Tech-Alert-Windows-crashes-related-to-Falcon-Sensor-2024-07-19","Status__c":"Resolved","Start_Date__c":"2024-07-18","End_Date__c":"2024-07-19","Last_Updated__c":"2024-07-19T18:41:42.000+0000","LastModifiedDate":"2024-07-19T18:41:42.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Incidents on customers utilizing Crowdstrike Falcon on Windows","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin;End user","Service_Feature__c":"Third Party","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-07-19T06:30:00.000+0000","CreatedDate":"2024-07-19T07:38:40.000+0000","CurrencyIsoCode":"AUD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXIJEA4"},"Id":"a9C4z000000TXIJEA4","Name":"I-8637","Duration__c":244,"Log__c":"In production cells, from about 5:44 AM Pacific to 9:36 AM Pacific today (June 10th), customers utilizing the Microsoft Teams connector will have seen (Teams for Okta Workflows) is not configured as a multi-tenant application\" errors on their actions/flows. Steps have been taken to resolve this, and the team is confirming the resolution now. Additional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-06-10","End_Date__c":"2024-06-10","Last_Updated__c":"2024-06-19T00:05:53.000+0000","LastModifiedDate":"2024-06-19T00:05:53.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Microsoft Connector Disruption","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:14;okta.com:16","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-06-10T12:42:00.000+0000","CreatedDate":"2024-06-10T17:04:52.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z0000000oGpEAI"},"Id":"a9C4z0000000oGpEAI","Name":"I-8457","Duration__c":1785,"Log__c":"At 7:00AM PDT on March 20, 2024, our engineering team became aware of issues with Workday imports and provisioning. Customers may experience issues with imports and provisioning calls.\r\n\r\nWe will resolve this incident once we have received confirmation the issue has been resolved from Workday.","Status__c":"Resolved","Start_Date__c":"2024-03-21","End_Date__c":"2024-03-21","Last_Updated__c":"2024-06-17T18:24:36.000+0000","LastModifiedDate":"2024-06-17T18:24:36.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Workday Import Issue","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta.com:16","Impacted_Audience__c":"End user","Service_Feature__c":"Third Party","Start_Time__c":"2024-03-21T16:26:00.000+0000","CreatedDate":"2024-03-21T16:28:11.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXI9EAO"},"Id":"a9C4z000000TXI9EAO","Name":"I-8550","Duration__c":22,"Log__c":"From approximately 2:15pm PDT to 2:35pm PDT on May 8, 2024, our engineering team became aware of an issue impacting Okta Privilege Access (OPA) affecting all cells. During this time, customers may experience issues accessing OPA console and may receive an HTTP 50x & 401 response codes. The engineering team has reverted the configurational changes made in OPA to mitigate the issue.","Status__c":"Resolved","Start_Date__c":"2024-05-08","End_Date__c":"2024-05-08","Last_Updated__c":"2024-05-31T14:16:22.000+0000","LastModifiedDate":"2024-05-31T14:16:22.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Okta Privilege Access page load errors","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:11;okta.com:12;oktapreview.com:3;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Privileged Access","Start_Time__c":"2024-05-08T21:34:00.000+0000","CreatedDate":"2024-05-08T21:38:40.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000001BZVpEAO"},"Id":"a9C4z000001BZVpEAO","Name":"I-8549","Duration__c":122,"Log__c":"From approximately 8:06AM to 10:03AM on May 8, 2024, our engineering team became aware of an issue impacting Okta Privilege Access (OPA) affecting all cells. During this time, customers may experience issues accessing OPA console and may receive an HTTP 50x & 401 response codes. The engineering team has reverted the configurational changes made in OPA to mitigate the issue. Additional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-05-08","End_Date__c":"2024-05-08","Last_Updated__c":"2024-05-15T01:56:38.000+0000","LastModifiedDate":"2024-05-15T01:56:38.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"OPA Degradation","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:8;okta.com:9;okta.com:11;okta.com:12;okta.com:15;okta.com:14;okta.com:16;okta.com:17","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Privileged Access","Start_Time__c":"2024-05-08T16:53:00.000+0000","CreatedDate":"2024-05-08T17:00:18.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXI4EAO"},"Id":"a9C4z000000TXI4EAO","Name":"I-8538","Duration__c":21,"Log__c":"Issue experiencing slowness and request/response failures 50Xs in OK2 starting at 1:01 am PDT has been addressed in approximately 20 minutes. Additional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-05-01","End_Date__c":"2024-05-01","Last_Updated__c":"2024-05-09T00:32:34.000+0000","LastModifiedDate":"2024-05-09T00:32:34.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Extended slowness in US-Cell 2","Impacted_Cells__c":"okta.com:2","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-05-01T08:24:27.000+0000","CreatedDate":"2024-05-01T08:24:27.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXHzEAO"},"Id":"a9C4z000000TXHzEAO","Name":"I-8472","Duration__c":225,"Log__c":"On April 8th, Between 3:50 AM PST, and 7:15AM PST Okta’s monitoring system alerted our team of delays in Workflows Low Latency mode resulting in impacts to Workflows. At this time, all customers in US FL1 who were running flows would have been affected by delays in flow execution. Customers would have intermittently experienced slowdowns and timeout issues on their flows.\r\n\r\nOkta Workflows has been experiencing significant growth in usage. This has resulted FL1 hitting capacity boundaries frequently. We are making infrastructure changes later today to address this growth. This operation should be transparent to customers. We will provide a more specific time range once the latest testing is complete.","Status__c":"Resolved","Start_Date__c":"2024-04-08","End_Date__c":"2024-04-08","Last_Updated__c":"2024-04-12T22:34:29.000+0000","LastModifiedDate":"2024-04-12T22:34:29.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows Degradation in FL1 Service","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-04-08T11:50:00.000+0000","CreatedDate":"2024-04-08T16:58:35.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000L1d1EAC"},"Id":"a9C4z000000L1d1EAC","Name":"I-8471","Duration__c":105,"Log__c":"An issue disrupting Okta Workflows for customers in OK1, OK2, OK3, OK4, OK6, OK7, and OK11 from 2:30 until 3:55 PM PDT on April 4th has been resolved. Additional root cause information will be available [within 5 Business days](https://support.okta.com/help/s/article/changes-in-the-trust-incident-rca-timeline).","Status__c":"Resolved","Start_Date__c":"2024-04-04","Last_Updated__c":"2024-04-12T22:28:44.000+0000","LastModifiedDate":"2024-04-12T22:28:44.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows Disruption in FL1","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-04-04T21:30:00.000+0000","CreatedDate":"2024-04-05T17:25:12.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXHuEAO"},"Id":"a9C4z000000TXHuEAO","Name":"I-8459","Duration__c":33,"Log__c":"Our Engineering team is investigating an issue causing slowness and internal server error messages for users in US-Cell-2. During this time, Okta users may notice slowness or internal server error messages in the Okta UI and with API calls. \r\n\r\nOur engineering team is performing corrective actions to mitigate the issues related to this degradation.\r\n\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","Status__c":"Resolved","Start_Date__c":"2024-04-02","End_Date__c":"2024-04-02","Last_Updated__c":"2024-04-10T06:29:23.000+0000","LastModifiedDate":"2024-04-10T06:29:23.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Slowness and internal server errors in US-Cell-2","Impacted_Cells__c":"okta.com:2","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-04-02T16:40:00.000+0000","CreatedDate":"2024-04-02T16:40:50.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z0000000oGuEAI"},"Id":"a9C4z0000000oGuEAI","Name":"I-8458","Duration__c":865,"Log__c":"An issue impacting flow executions in the FL1 instance for a subset of cells has been addressed. Our monitoring shows a recovery to normal conditions. \r\n\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-03-26","End_Date__c":"2024-03-27","Last_Updated__c":"2024-04-03T22:57:47.000+0000","LastModifiedDate":"2024-04-03T22:57:47.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows Degradation in FL1 Service","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-03-26T17:38:00.000+0000","CreatedDate":"2024-03-26T17:45:33.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z000000TXHpEAO"},"Id":"a9C4z000000TXHpEAO","Name":"I-8456","Duration__c":141,"Log__c":"An issue impacting the degradation of service in US-Cell 1 has been addressed. \r\n\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-03-21","End_Date__c":"2024-03-21","Last_Updated__c":"2024-03-28T20:52:58.000+0000","LastModifiedDate":"2024-03-28T20:52:58.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Elevated Errors in US-Cell 1","Impacted_Cells__c":"okta.com:1","Impacted_Audience__c":"Admin;API Products;End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-03-21T14:43:00.000+0000","CreatedDate":"2024-03-21T14:45:41.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z0000000oGkEAI"},"Id":"a9C4z0000000oGkEAI","Name":"I-8455","Duration__c":218,"Log__c":"At 6:02AM PDT on March 19, 2024, our engineering team became aware of a replication lag on US-Cell 7 that caused queries to return stale data. Okta admins experienced HTTP 404 response codes when searching for new user/group objects. This issue was addressed and mitigated at 9:52AM PDT. \r\n\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-03-19","End_Date__c":"2024-03-19","Last_Updated__c":"2024-03-26T21:46:44.000+0000","LastModifiedDate":"2024-03-26T21:46:44.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Incident_Title__c":"Degraded Search Function in US-Cell 7","Impacted_Cells__c":"okta.com:7","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Core Platform","Start_Time__c":"2024-03-19T18:10:00.000+0000","CreatedDate":"2024-03-19T18:15:56.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v66.0/sobjects/Incident__c/a9C4z0000000oGfEAI"},"Id":"a9C4z0000000oGfEAI","Name":"I-8454","Duration__c":364,"Log__c":"Our Workflows team is seeing improvements in our Workflow service performance. Low-latency flows have recovered and are within expected service levels. We are still investigating Scheduled flow execution performance.\r\n\r\nOur engineering team continues to work on Scheduled flow latency and will work with impacted customers. \r\n\r\nFor more information on the differences between flows, please visit: https://help.okta.com/wf/en-us/content/topics/workflows/learn/about-low-latency.htm\r\n\r\nAdditional root cause information will be available within 5 Business days.","Status__c":"Resolved","Start_Date__c":"2024-03-19","End_Date__c":"2024-03-19","Last_Updated__c":"2024-03-26T20:37:36.000+0000","LastModifiedDate":"2024-03-26T20:37:36.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Incident_Title__c":"Workflows Degradation in FL1 Service","Impacted_Cells__c":"okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:6;okta.com:7;okta.com:11","Impacted_Audience__c":"Admin","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2024-03-19T14:56:00.000+0000","CreatedDate":"2024-03-19T14:57:39.000+0000","CurrencyIsoCode":"USD"}]
[]
Okta Status Site Guest User
Guest
okta.com:1,okta.com:2,okta.com:3,okta.com:4,okta.com:6,okta.com:7,okta.com:8,okta.com:9,okta.com:11,okta.com:12,okta.com:14,okta.com:16,okta.com:17,okta.com:18,okta.com:19,okta-emea.com:1,oktapreview.com:1,oktapreview.com:2,oktapreview.com:3
false
[{"year":2010, "uptime":99.98, "month":["100.000","100.000","100.000","100.000","99.955","100.000","100.000","99.933","99.928","99.960","100.000","100.000"]},{"year":2011, "uptime":99.96, "month":["99.973","99.980","100.000","99.977","99.969","99.954","100.000","99.917","99.889","99.964","100.000","99.953"]},{"year":2012, "uptime":99.9966, "month":["100.000","100.000","99.996","100.000","100.000","100.000","100.000","99.964","100.000","100.000","100.000","100.000"]},{"year":2013, "uptime":99.9994, "month":["99.993","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2014, "uptime":99.95, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","99.610","99.824","99.993","100.000","99.980"]},{"year":2015, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2016, "uptime":99.95, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","99.384","100.000","100.000"]},{"year":2017, "uptime":99.97, "month":["99.969","99.692","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2018, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2019, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2020, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2021, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2022, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2023, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2024, "uptime":99.99, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","99.825"]},{"year":2025, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000","100.000"]},{"year":2026, "uptime":100.0000, "month":["100.000","100.000","100.000","100.000","","","","","","","",""]}]
[]
[{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l23EAB"},"Id":"a1P4z00000A0l23EAB","CreatedDate":"2024-03-13T23:11:32.000+0000","IncidentId__c":"a9C4z000000TXHfEAO","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn March 6th at 5:27am (PT) Okta’s customer support reached out to engineering regarding slow processing of workflows in US Cell Workflows OK1 Cell (US), OK2 Cell (US), OK3 Cell (US), OK4 Cell (US), OK6 Cell (US), OK7 Cell (US), OK11 Cell (US). During this time, customers in these cells received execution delays, and latency sensitive flows experienced errors. \r\n\r\n\r\nRoot Cause Summary\r\n\r\nThis issue was a result of degraded responsiveness in an infrastructure component, which caused autoscaling to become unresponsive and led to interruptions in the flow execution service and caused an increased latency in the corresponding cells. \r\n\r\n\r\nRemediation Steps\r\n\r\nOkta began diagnosing the issue at 5:27am (PT). At 11:02am (PT) Okta identified the root cause and took action to restore the infrastructure component. At 1:33pm (PT) Okta saw a decrease in execution delays for the affected cell. At 3:15pm (PT) all functionality was restored and normal processing resumed. \r\n\r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, Okta is including additional latency monitoring and tooling improvement to avoid performance slowdowns. These monitoring changes will improve Workflow’s scalability and enable us to root cause slowdowns swiftly. \r\n\r\nTotal Duration (Minutes): 701","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l2wEAB"},"Id":"a1P4z00000A0l2wEAB","CreatedDate":"2024-03-19T15:20:01.000+0000","IncidentId__c":"a9C4z0000000oGfEAI","UpdateLog__c":"Our Workflows team continues to address the latency issues in Workflows executions for a subset of Okta US Cells with top priority. The team has managed to adjust the configuration and plans to allocate more resources for the Workflows service.\r\n\r\n\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l31EAB"},"Id":"a1P4z00000A0l31EAB","CreatedDate":"2024-03-19T15:43:59.000+0000","IncidentId__c":"a9C4z0000000oGfEAI","UpdateLog__c":"Our Workflows team continues to address the latency issues in Workflows executions for a subset of Okta US Cells with top priority. Our monitoring shows improvement after adjusting the configuration. \r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in workflow executions.\r\n\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l36EAB"},"Id":"a1P4z00000A0l36EAB","CreatedDate":"2024-03-19T16:04:04.000+0000","IncidentId__c":"a9C4z0000000oGfEAI","UpdateLog__c":"Our Workflows team is seeing improvements in our Workflow service performance. Low-latency flows have recovered and are within expected service levels. We are still investigating Scheduled flow execution performance.\r\n\r\nOur engineering team continues to work on Scheduled flow latency and will work with impacted customers. \r\n\r\nFor more information on the differences between flows, please visit: https://help.okta.com/wf/en-us/content/topics/workflows/learn/about-low-latency.htm\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3aEAB"},"Id":"a1P4z00000A0l3aEAB","CreatedDate":"2024-03-21T15:20:29.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"Our engineering team is performing configuration changes to add more capacity in US-Cell 1. End users may experience slowness or intermittent errors accessing US-Cell 1. \r\n\r\nWe'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3fEAB"},"Id":"a1P4z00000A0l3fEAB","CreatedDate":"2024-03-21T15:40:47.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"We have identified the potential cause of the issue. Our engineering team continues to mitigate the degradation by continuously monitoring and upsizing the capacity in US-Cell 1. However, end users may still experience slowness or intermittent errors accessing US-Cell 1. \r\n\r\nWe'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3kEAB"},"Id":"a1P4z00000A0l3kEAB","CreatedDate":"2024-03-21T16:18:15.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"Our engineering team continues to work on the root cause and continually mitigate the degradation by upsizing the capacity in US-Cell 1. However, end users may still experience slowness or intermittent errors accessing US-Cell 1.\r\n\r\nWe'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3pEAB"},"Id":"a1P4z00000A0l3pEAB","CreatedDate":"2024-03-21T16:51:27.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"Okta continues mitigating the degradation issue, and our monitoring shows an improvement with the degradation in US-Cell 1. Okta will continue to address the problem and work on the root cause.\r\n\r\nOur next update will be in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3uEAB"},"Id":"a1P4z00000A0l3uEAB","CreatedDate":"2024-03-21T17:22:35.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"Okta continues to monitor the current situation regarding service degradation at US-Cell 1. Our monitoring shows improvement in performance for US-Cell 1 customers.\r\n\r\nOur next update will be in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l3zEAB"},"Id":"a1P4z00000A0l3zEAB","CreatedDate":"2024-03-21T17:58:36.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"An issue impacting the degradation of service in US-Cell 1 has been addressed. \r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l44EAB"},"Id":"a1P4z00000A0l44EAB","CreatedDate":"2024-03-21T22:51:30.000+0000","IncidentId__c":"a9C4z0000000oGpEAI","UpdateLog__c":"Workday services are restored. We are seeing Workday imports and provisioning actions complete for Okta customers.\r\n\r\nAdditional root cause information will be available within 5 Business days","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l4iEAB"},"Id":"a1P4z00000A0l4iEAB","CreatedDate":"2024-03-26T18:09:20.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team continues to address the latency issues in Workflows executions for a subset of Okta US Cells with top priority. The team has identified the potential root cause and is managing to adjust the configuration to address the latency issue in the FL1 service.\r\n\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l4nEAB"},"Id":"a1P4z00000A0l4nEAB","CreatedDate":"2024-03-26T18:40:15.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team continues to address the latency issues in Workflows executions for a subset of Okta US Cells with top priority. Okta Admins may sporadically experience slowness or intermittent timeouts in workflow executions.\r\n\r\nThe Workflows team is preparing a patch to fix the issue, which will be completely deployed by 4PM PDT. \r\n\r\nWe'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l4sEAB"},"Id":"a1P4z00000A0l4sEAB","CreatedDate":"2024-03-26T19:08:14.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team continues to address the latency issues in Workflows executions for a subset of Okta US Cells with top priority. Okta Admins may sporadically experience slowness or intermittent timeouts in workflow executions.\r\n\r\nThe Workflows team has managed to adjust the configuration to bring down the flow execution failure rates. \r\n\r\nThe Workflows team is testing the patch to be deployed in FL1. This patch will fix the overall latency issues and will be completely deployed by 4PM PDT.\r\n\r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l4xEAB"},"Id":"a1P4z00000A0l4xEAB","CreatedDate":"2024-03-26T20:01:26.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team has resolved low latency timeouts. Okta Admins may sporadically experience slowness in scheduled workflow executions.\r\n\r\nThe Workflows team is testing the patch to fix the overall latency issue in FL1. This patch will be completely deployed by 4PM PDT.\r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l52EAB"},"Id":"a1P4z00000A0l52EAB","CreatedDate":"2024-03-26T20:39:07.000+0000","IncidentId__c":"a9C4z0000000oGfEAI","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn March 19th, at 6:13 am PDT Okta’s monitoring system alerted our team of execution delays in Workflows. During this time, all customers in FL1 who were running flows would have been affected by delays in flow execution. \r\n\r\n\r\nRoot Cause Summary\r\n\r\nThis issue was caused by increased latency and imposed rate limits on infrastructure components triggered by a significant surge in workflow executions. \r\n\r\nThis caused executions to back up in job queues, ultimately resulting in flow execution delays.\r\n\r\n\r\nRemediation Steps\r\n\r\nImmediately upon receiving alerts, Okta began diagnosing the issue. At 6:30 am PDT Okta began to troubleshoot and initiate remediation steps including applying various scaling operations, and initiating an org-specific block. At approximately 11:00 am PDT, Okta saw a decrease in execution delays, and by 11:34 am PST all functionality was restored and normal processing resumed. \r\n\r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, Okta plans to migrate to infrastructure with better scaling capabilities, and implement more sophisticated throttling mechanisms.\r\n\r\n\r\nTotal Duration\r\n\r\nTotal Duration (Minutes): 364","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l57EAB"},"Id":"a1P4z00000A0l57EAB","CreatedDate":"2024-03-26T21:46:30.000+0000","IncidentId__c":"a9C4z0000000oGkEAI","UpdateLog__c":"We apologize for any impact this incident may have caused to you and your business. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this recent incident that may have disrupted your ability to use some functionality of the Okta service.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn March 19th at 5:57AM (PT), Okta was alerted to database replication lag alerts for the Okta service in US Cell 7. During this time, administrators and end users may have experienced slowness in propagation of changes resulting in inconsistent UI and API experiences. Additionally, admins may have encountered 404 “page not found” error messages while fetching some records. At 9:41AM (PT) the service was restored back to normal processing times. \r\n\r\n\r\nRoot Cause Summary\r\n\r\nOkta determined that a substantial increase in background batch jobs exceeded the planned duration and impacted replication services. \r\n\r\n\r\nRemediation Steps\r\n\r\nUpon investigation, Okta identified the source of the jobs causing the replication lag, stopped the affected jobs, and deployed additional mitigation steps to handle the excess request traffic. The actions successfully addressed the issue, and the team confirmed that the service had fully returned to normal. \r\n\r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, the source jobs are in a moratorium state and under detailed review. Teams will review previous history, scheduling and focus on optimization for these jobs moving forward. \r\n\r\nDuration (# of minutes): 218","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l5CEAR"},"Id":"a1P4z00000A0l5CEAR","CreatedDate":"2024-03-26T22:04:36.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team has deployed the emergency patch to FL1, and we see a performance improvement.\r\n\r\nThe team continues to address the Scheduled flow execution latency issue by monitoring and scaling up resources to better improve the performance. \r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in Scheduled flow executions. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l5HEAR"},"Id":"a1P4z00000A0l5HEAR","CreatedDate":"2024-03-26T23:09:19.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team continues to address the Scheduled flow execution latency issue and is preparing another patch to support the change configuration in the FL1 instance.\r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in Scheduled flow executions. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l5MEAR"},"Id":"a1P4z00000A0l5MEAR","CreatedDate":"2024-03-27T00:54:29.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team is testing the new patch to be deployed in the FL1 instance. This change in configuration should improve our overall service reliability and quality.\r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in Scheduled flow executions. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l5qEAB"},"Id":"a1P4z00000A0l5qEAB","CreatedDate":"2024-03-28T16:42:25.000+0000","IncidentId__c":"a9C4z0000000oGpEAI","UpdateLog__c":"Following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue which impacted the Okta service\r\n \r\n\r\nDetection and Impact:\r\n\r\nOn March 20th starting at 8:30AM (PT), Okta became aware of intermittent connection timeout failure issues with Workday on all US Cells. Impacted customers experienced problems with imports and provisioning. During investigation the issues encountered were confirmed by Workday to be an issue within their services\r\n\r\n\r\nRoot Cause Summary\r\n\r\nThe error was related to a network issue at Workday. \r\n \r\n\r\nRemediation Steps\r\n\r\nThe service provider resolved the issue at 2:15PM (PT). At that time, Okta’s services fully recovered.\r\n\r\nDuration (# of minutes): 1785","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000A0l60EAB"},"Id":"a1P4z00000A0l60EAB","CreatedDate":"2024-03-28T20:53:12.000+0000","IncidentId__c":"a9C4z000000TXHpEAO","UpdateLog__c":"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.\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn March 21st at 7:23 a.m. PDT, Okta Technical Operations teams detected an issue where some users experienced increased error rates and response times, and may have received HTTP 503 response codes in US Cell OK1. \r\n\r\n\r\nRoot Cause Summary:\r\n\r\nBased on our investigation and findings, the root cause of increased error rates and response times was due to saturated CPU resources supporting internal cache services caused by an anomalous internal workload. \r\n\r\n\r\nRemediation Steps:\r\nOkta immediately implemented fixes, including resource capacity increases and rerouting traffic to alternate servers, in order to mitigate impact. As of March 21st at 9:37 a.m. PDT, the service returned to normal operation. \r\n\r\n\r\nPreventative Actions:\r\n\r\nTo ensure this does not happen again, we are enhancing the monitoring signals related to the affected internal services to improve alerting behaviors; further, in addition to resource capacity increases, engineering teams are engaged to tune cache services for more efficient handling of the underlying workload.\r\n\r\nDuration (# of minutes):141","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qMEEAZ"},"Id":"a1P4z00000C1qMEEAZ","CreatedDate":"2024-03-27T02:52:41.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team is testing the new patch to be deployed in the FL1 instance. This change in configuration should improve our overall service reliability and quality.\r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in Scheduled flow executions. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qMJEAZ"},"Id":"a1P4z00000C1qMJEAZ","CreatedDate":"2024-03-27T05:08:05.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team is currently deploying the new patch in the FL1 instance. This change in configuration should improve our overall service reliability and quality.\r\n\r\nThe incident is still ongoing. Okta Admins may sporadically experience slowness in Scheduled flow executions. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qMOEAZ"},"Id":"a1P4z00000C1qMOEAZ","CreatedDate":"2024-03-27T06:05:29.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"Our Workflows team has deployed the new emergency patch and continues monitoring the current FL1 performance issue. \r\n\r\nWe'll provide an update in 2 hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qMTEAZ"},"Id":"a1P4z00000C1qMTEAZ","CreatedDate":"2024-03-27T06:41:54.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"An issue impacting flow executions in the FL1 instance for a subset of cells has been addressed. Our monitoring shows a recovery to normal conditions. \r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qUGEAZ"},"Id":"a1P4z00000C1qUGEAZ","CreatedDate":"2024-04-02T17:03:29.000+0000","IncidentId__c":"a9C4z000000TXHuEAO","UpdateLog__c":"Our Engineering team has resolved the issue with US-Cell-2 slowness and internal server errors. \r\n\r\nOkta customers in US-Cell-2 should no longer see slowness and internal server errors.\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qXcEAJ"},"Id":"a1P4z00000C1qXcEAJ","CreatedDate":"2024-04-03T22:57:12.000+0000","IncidentId__c":"a9C4z0000000oGuEAI","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn March 26th, at 8:40AM PT, Okta’s monitoring system alerted our team of delays in Workflows Low Latency mode resulting in impacts to Workflows. At this time, all customers in US FL1 who were running flows would have been affected by delays in flow execution. Customers would have intermittently experienced slowdowns and timeout issues on their flows.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nThis issue was a result of the Workflows cell reaching maximum throughput capacity which caused flows to be completed at a slower rate. Two distinct areas were identified as bottlenecks and addressed. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nImmediately upon receiving alerts, Okta began diagnosing the issue and launched a series of scaling actions to help with stability. \r\n\r\n \r\n\r\nDuring this time, two bottlenecks were identified. First, a cache cluster had been impacted by increased traffic resulting in elevated CPU usage and network latency. Second, cloud storage operations were affected by a recent application change, which resulted in increased overall usage and reduced system throughput.\r\n\r\n \r\n\r\nAt 2:55PM PT, the team decided to offload specific use cases in the cache cluster to a new cluster. At 9:57PM PT the team cut over to the new cluster and network latency to the cache cluster dropped significantly. Simultaneously, a hotfix was applied to adjust cloud storage operations and system performance significantly improved. At 11:05PM PT normal processing resumed.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nThe fixes applied during this time have resolved this issue and further improved service reliability issues also seen in previous incidents. Additional updates and investments are under review and will be applied appropriately. \r\n\r\n \r\n\r\nAdditionally, Okta has identified a number of opportunities to enhance our monitoring capabilities in these areas.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qc1EAB"},"Id":"a1P4z00000C1qc1EAB","CreatedDate":"2024-04-08T20:49:04.000+0000","IncidentId__c":"a9C4z000000TXHzEAO","UpdateLog__c":"Infrastructure changes to address this growth are planned to begin at 2:00 P.M PDT. This operation will be transparent to customers. We will update the status page once these changes have been completed.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qjfEAB"},"Id":"a1P4z00000C1qjfEAB","CreatedDate":"2024-04-12T22:28:23.000+0000","IncidentId__c":"a9C4z000000L1d1EAC","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn April 4th, at 2:00PM PT, Okta’s monitoring system alerted our team of slowness and timeout issues in the US FL1 environment. At this time, customers who were running workflows would have been affected by intermittent high latency in flow execution. Customers may have experienced slowdown and timeouts issues on their flows and delays in viewing reports.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nThe issue was a result of a connection spike from the cloud provider’s cache cluster which resulted in an overconsumption of the service’s CPU. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nImmediately upon receiving alerts, Okta began diagnosing the issue and discovered high CPU usage in the cache cluster. The team scaled down the application containers to reduce pressure on the cache cluster and subsequently failed away from the impacted cluster. At 3:45PM PT normal processing resumed.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nOkta is currently engaged in making significant updates and upgrades to this environment to improve horizontal scalability and to address the recent issues and ensure stability.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1qjkEAB"},"Id":"a1P4z00000C1qjkEAB","CreatedDate":"2024-04-12T22:32:59.000+0000","IncidentId__c":"a9C4z000000TXHzEAO","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn April 8th, at 3:50AM PT, Okta monitoring alerted the team of large queue lengths in US FL1. At this time, all customers in US FL1 who were running flows would have experienced slowdown and timeouts issues.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nThe issue was a result of a large flow impacting queues which put additional stress on our cache cluster.\r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nImmediately upon receiving alerts, Okta began to investigate and discovered a large flow which had begun to impact queues. At 5:00AM Okta began taking actions to block and mitigate the large flow. Throughout the impact window, the team scaled up resources and performed additional cluster tuning to address the flow impact and subsequent backlog. At 7:15AM PT processing resumed to normal rates.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nOkta is currently engaged in making significant updates and upgrades to this environment to improve horizontal scalability and to address the recent issues and ensure stability.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1r4iEAB"},"Id":"a1P4z00000C1r4iEAB","CreatedDate":"2024-05-01T08:30:48.000+0000","IncidentId__c":"a9C4z000000TXI4EAO","UpdateLog__c":"Issue experiencing slowness and request/response failures 50Xs in OK2 starting at 1:01 am PDT has been addressed in approximately 20 minutes. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rGUEAZ"},"Id":"a1P4z00000C1rGUEAZ","CreatedDate":"2024-05-08T21:52:38.000+0000","IncidentId__c":"a9C4z000000TXI9EAO","UpdateLog__c":"From approximately 2:15pm PDT to 2:35pm PDT on May 8, 2024, our engineering team became aware of an issue impacting Okta Privilege Access (OPA) affecting all cells. During this time, customers may experience issues accessing OPA console and may receive an HTTP 50x & 401 response codes. The engineering team has reverted the configuration changes.\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rT3EAJ"},"Id":"a1P4z00000C1rT3EAJ","CreatedDate":"2024-07-02T15:59:24.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"At 2:27 UTC on July 2, 2024, Okta became aware of a single sign-on issue with Microsoft. Customers may experience 500s when clicking the chiclet in the Okta dashboard. End users may login via SP-Initiated SSO or access via link https://login.microsoftonline.com/. We'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rT8EAJ"},"Id":"a1P4z00000C1rT8EAJ","CreatedDate":"2024-07-02T16:38:41.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"Currently, our engineering team is working with Microsoft support on the issue.\r\nPublished Knowledge base article to assist with a workaround https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTDEAZ"},"Id":"a1P4z00000C1rTDEAZ","CreatedDate":"2024-07-02T17:03:01.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"As of 10:01 AM PST, our engineering team continues to work with Microsoft support on the issue.\r\nPublished Knowledge base article to assist with a workaround https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTIEAZ"},"Id":"a1P4z00000C1rTIEAZ","CreatedDate":"2024-07-02T17:59:40.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"As of 11:00 AM PST, A case has been opened with Microsoft, and they are actively reviewing what has changed. All Microsoft O365 Office applications are working except for OneDrive, and this is only for the IdP-initiated SSO login flow. SP-initiated SSO is working as expected. Please refer to the Published Knowledge base article to assist with a workaround https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We will continue to monitor and will provide an update in 24 hours.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTNEAZ"},"Id":"a1P4z00000C1rTNEAZ","CreatedDate":"2024-08-07T06:14:45.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our downstream providers regarding the SMS delivery issues to China. We recommend leveraging different MFA options for Okta end users in China. We will resolve this incident once we have received confirmation that the issue has been resolved by the downstream providers.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTSEAZ"},"Id":"a1P4z00000C1rTSEAZ","CreatedDate":"2024-08-07T12:50:39.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our upstream providers regarding the SMS OTP delivery delays. We recommend leveraging different MFA options for end users.\r\n\r\nTelesign confirmed the suspicion that the issue may lie downstream on the operator’s side. Updates are still pending from Twilio, who are also investigating.\r\n\r\nWe will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTXEAZ"},"Id":"a1P4z00000C1rTXEAZ","CreatedDate":"2024-08-08T11:01:40.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our downstream providers regarding the SMS OTP delivery delays. We recommend leveraging different MFA options for end users.\r\n\r\nOur telephony provider continues to work on a permanent fix for this issue.\r\n\r\nWe will resolve this incident once we have received confirmation the issue has been resolved from our downstream provider.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTcEAJ"},"Id":"a1P4z00000C1rTcEAJ","CreatedDate":"2024-08-09T00:52:22.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our downstream providers regarding the SMS OTP delivery delays. We recommend leveraging different MFA options for end users.\r\n\r\nOur telephony provider advised the issue is specific to the carrier in China and continues to work with their intermediate providers to resolve the issue.\r\n\r\nWe will resolve this incident once we have received confirmation the issue has been resolved from our downstream provider.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rThEAJ"},"Id":"a1P4z00000C1rThEAJ","CreatedDate":"2024-08-13T10:44:21.000+0000","IncidentId__c":"a9C4z000000TXIdEAO","UpdateLog__c":"We continue to investigate the AD agents connection issue on OK14, we will update this message with more information as soon as it becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTmEAJ"},"Id":"a1P4z00000C1rTmEAJ","CreatedDate":"2024-08-15T22:58:27.000+0000","IncidentId__c":"a9C4z000001BZakEAG","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact \r\n\r\nOn August 8th at 2:29 pm PT, Okta detected interruptions with customers using Workflows in US FL1. Impacted customers experienced timeout errors when attempting flow executions or any operations in workflow designers. \r\n\r\n \r\n\r\nRoot Cause Summary\r\n\r\nThe root cause of this incident was an internal service issuing a high volume of concurrent requests against our cache database and overwhelming it during a period of high activity. This caused degraded performance in the Workflows system and resulted in the timeout errors customers experienced.\r\n\r\n \r\n\r\nRemediation Steps\r\n\r\nUpon receiving alerts, Okta began diagnosing the issue. From 3:10 pm - 3:16 pm PT Okta observed that the service began to recover on its own. The Okta team continued to observe its progress. At 3:26 pm PT, processing returned to normal rates. \r\n\r\n \r\n\r\nPreventative Actions\r\n\r\nOkta is currently engaged in making performance optimizations in this environment to address the recent issue and ensure stability. We are also engaging in longer term architecture improvements to remove this cache. \r\n\r\n \r\n\r\nTotal Duration: 57 minutes\r\n\r\nAugust 8th 2:29 pm - 3:26 pm PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTrEAJ"},"Id":"a1P4z00000C1rTrEAJ","CreatedDate":"2024-09-18T02:40:00.000+0000","IncidentId__c":"a9C4z000000TXIiEAO","UpdateLog__c":"An issue impacting SMS OTP to end users in China has been resolved. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rTwEAJ"},"Id":"a1P4z00000C1rTwEAJ","CreatedDate":"2024-09-24T00:26:06.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is continuing to work on a hotfix release to mitigate the ’400 Bad Request error when federating new domains. Our engineering team is running tests and validating the patch to be deployed at approximately 2:30 am US Pacific Time, September 24, 2024. \r\n\r\nIn the meantime, the team has documented a workaround, available here:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rU1EAJ"},"Id":"a1P4z00000C1rU1EAJ","CreatedDate":"2024-09-24T02:55:55.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is continuing to work on a hotfix release to mitigate the ’400 Bad Request error when federating new domains. Our team is running tests and validating the patch to be deployed at approximately 2:30 a.m. US Pacific Time on September 24, 2024.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rU6EAJ"},"Id":"a1P4z00000C1rU6EAJ","CreatedDate":"2024-09-24T05:09:03.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is continuing to work on a hotfix release to mitigate the '400 Bad Request' error when federating new domains. Our team is running tests and validating the patch to be deployed at approximately 2:30 a.m. US Pacific Time on September 24, 2024.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rUBEAZ"},"Id":"a1P4z00000C1rUBEAZ","CreatedDate":"2024-09-24T07:10:17.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is continuing to work on a hotfix release to mitigate the '400 Bad Request' error when federating new domains. Our team is running tests and validating the patch to be deployed at approximately 2:30 a.m. US Pacific Time on September 24, 2024.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rUGEAZ"},"Id":"a1P4z00000C1rUGEAZ","CreatedDate":"2024-09-24T09:29:47.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"At 2:30 am US Pacific Time on September 24, 2024, Okta’s Engineering Team successfully applied a hotfix release to mitigate the '400 Bad Request' error when federating new domains to all Okta cells except OK7 and OK14. Our Team is continuing to work on deploying the patch in cells OK7 and OK14.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rULEAZ"},"Id":"a1P4z00000C1rULEAZ","CreatedDate":"2024-09-24T10:33:43.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team successfully applied a hotfix release to mitigate the '400 Bad Request' error when federating new domains to all Okta cells except OK7. Our Team is continuing to work on deploying the patch in cell OK7.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rUQEAZ"},"Id":"a1P4z00000C1rUQEAZ","CreatedDate":"2024-09-24T12:46:20.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is continuing to work on deploying the patch in cell OK7 to mitigate the '400 Bad Request' error when federating new domains.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rUVEAZ"},"Id":"a1P4z00000C1rUVEAZ","CreatedDate":"2024-09-24T17:00:38.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta’s Engineering Team is deploying the patch in cell OK7 to mitigate the '400 Bad Request' error when federating new domains.\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nDeployment to OK7 is estimated to be completed in 4 hours.\r\n\r\nWe’ll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rUaEAJ"},"Id":"a1P4z00000C1rUaEAJ","CreatedDate":"2024-10-10T20:50:03.000+0000","IncidentId__c":"a9C4z000001BZcHEAW","UpdateLog__c":"On October 3, at 2:00 pm PST, Okta was alerted to an issue where users who attempted to perform single sign-on to the Datadog application would have experienced errors. All users in production and preview cells who were trying to access the Datadog application in their respective orgs would have been impacted.\r\n\r\n \r\n\r\n \r\n\r\nImpact:\r\n\r\nUsers who attempted to login and access data dog applications within their org would have observed below SAML Error.\r\n\r\n \r\n\r\n \r\n\r\nRoot Cause:\r\n\r\nBeginning at 7:27 am PST, Okta rolled out an update for the Datadog SSO integration related to the SAML ACS URL value. This resulted in end users being unable to complete SAML SSO for the application.\r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nImmediately upon receiving alerts, the Okta team began diagnosing the issue. Okta rolled back the changes and in partnership with Datadog restored the service back to normal operation by 4:40pm PDT.\r\n\r\n \r\n\r\n \r\n\r\nPreventative Action:\r\n\r\nTo ensure this issue does not recur, Okta is reviewing and enhancing processes used for application integration updates, as well as reviewing and updating the test processes for application changes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rldEAB"},"Id":"a1P4z00000C1rldEAB","CreatedDate":"2024-11-04T23:25:23.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact \r\n\r\nOn October 28th at 5:06 AM (PT), Okta was alerted that a few customers experienced delays related to imports in US Cell 14. During this time customers may have observed delayed imports as a result, delays in user activation, provisioning, password sync and additional async tasks At 9:38am(PT) task processing in the cell was restored to normal processing times. \r\n\r\n \r\n\r\nRoot Cause Summary\r\n\r\nThis issue was a result of a build up of both active and queued asynchronous tasks. Under heavy load of these tasks, the scheduler dequeued records too slowly and created a large backlog. This large backlog resulted in scheduling delays of tasks such as imports.\r\n\r\n \r\n\r\nRemediation Steps\r\n\r\nOkta Engineering scaled out for additional processing capacities, and tuned the dequeuing parameters to pull more records from the queue. These actions successfully addressed the issue, and all imports returned to normal processing levels. \r\n\r\n \r\n\r\nPreventative Actions\r\n\r\nOkta Engineering is reviewing and updating alerting, making improvements to address tasks queuing, and updating logging to better identify future issues related to queueing.\r\n\r\n \r\n\r\nTotal Duration\r\n\r\nTotal Duration (Minutes): 271\r\n\r\nActual Time: 5:07am PT - 9:38am PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rliEAB"},"Id":"a1P4z00000C1rliEAB","CreatedDate":"2024-11-15T04:38:22.000+0000","IncidentId__c":"a9C4z000000TXInEAO","UpdateLog__c":"Okta Engineering implemented mitigating actions and restored the connectivity impacting some users in OK6. Okta Engineering will continue monitoring. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rlnEAB"},"Id":"a1P4z00000C1rlnEAB","CreatedDate":"2024-11-23T00:25:19.000+0000","IncidentId__c":"a9C4z000000TXInEAO","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact \r\n\r\nOn November 14th, at 6:14 pm PST, Okta was alerted to an issue where requests to US Cell OK6 from a specific geo location may have experienced increased errors and slow response times, and may have received HTTP 503 error messages.\r\n\r\n \r\n\r\nRoot Cause Summary\r\n\r\nBased on our investigation and findings, the root cause of this issue was due to a configuration error resulting from a software deployment by our 3rd party service provider. \r\n\r\n \r\n\r\nRemediation Steps\r\n\r\nImmediately upon receiving alerts of network disruptions, Okta Engineering escalated the issues with our provider and worked to implement internal mitigations. Okta worked directly with our provider to mitigate the issue and confirmed full service restoration. Okta's internal mitigations restored full service to US Cell OK6 by 7:16 pm PST on November 14th.\r\n\r\n \r\nPreventative Actions\r\n\r\nOkta plans to continue to work with our 3rd party service provider to monitor and detect georegional issues faster and have added new guidance to the operational processes further to improve time to service recovery.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rlsEAB"},"Id":"a1P4z00000C1rlsEAB","CreatedDate":"2024-11-25T23:05:21.000+0000","IncidentId__c":"a9C4z000001BZecEAG","UpdateLog__c":"Detection:\r\nCustomers began reporting that Paylocity OIN Integration imports were removing users from Okta. The import jobs were receiving an error response from the Paylocity SCIM API backend.\r\n\r\n\r\nImpact:\r\nPaylocity OIN Integration import jobs would receive an error from the Paylocity backend which would then cause the import job to remove users as not found if Paylocity was configured as the profile master.\r\n\r\n\r\nRoot Cause:\r\nPaylocity confirmed they had erroneously disabled the SCIM API that the Okta integration relies on. This API was disabled between 7:53 AM PST and 1:00 PM PST. \r\n\r\n\r\nRemediation Steps:\r\nOkta customers using the Paylocity OIN Integration would need to rerun any imports that occurred during this time window to restore users that had been removed. Import roadblock settings in Okta would prevent excessive removals if configured.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rlxEAB"},"Id":"a1P4z00000C1rlxEAB","CreatedDate":"2024-12-20T22:58:41.000+0000","IncidentId__c":"a9C4z000001BZgOEAW","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nBeginning on December 13th at 4:47AM PT, Okta became aware of customer reports regarding issues related to authentication and access, at which time the response teams began investigating the incident. \r\n\r\n \r\n\r\nDuring this time, customer admins in all commercial and FedRamp Moderate cells were unable to login to the Okta Help Center via login.okta.com. Additionally, users of embedded and custom browsers may have experienced error messages impacting log in flows in certain cases.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nOkta Engineering determined that the root cause of the issue was due to a DNS record deletion of a reserved subdomain that was executed as part of automated resource cleanup processes which began at 2:01AM PT. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nAt 7:07AM PT, the source of the error was identified and Okta engineering restored the DNS record at 7:15AM PT. At 7:25AM PT all processing had returned to normal.\r\n\r\n \r\n\r\nAfter determining that the clean up process was the source of the deletion, Okta engineering disabled it at 8:42AM PT. \r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nCertain cleanup operations have been paused until additional protections are put in place, including protecting reserved DNS records.\r\n\r\nIn order to prevent similar incidents from happening again, Okta is addressing the following:\r\nAdd stronger protections and enhanced monitoring around reserved DNS records in clean-up operations\r\n\r\nUpdates to our monitoring and runbooks for login.okta.com service issues\r\n\r\nIn the event that Okta Help Center is not available, customers can use the relevant support number found at: https://www.okta.com/contact/. When calling in, they will be asked for their Customer Support Account ID for caller verification.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rm2EAB"},"Id":"a1P4z00000C1rm2EAB","CreatedDate":"2025-01-22T23:52:14.000+0000","IncidentId__c":"a9C4z000001BZiUEAW","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn January 14th at 9:22AM PT Okta internal monitoring alerts indicated errors in loading custom domains in OK Cell 8.\r\n\r\nDuring this time customers who utilize customized domains in OK Cell 8 experienced errors accessing the service.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nIn order to resolve an issue which was caught by our internal monitoring during a change the previous evening, Okta engineering staff was redeploying the edge servers. Due to a bug in the operating procedure used, the service became momentarily unavailable until corrective actions were taken to fully restore the service. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nAt 9:24AM PT, Okta Engineering quickly identified the issue and resolved it by placing healthy servers in service.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nOkta has updated the operating procedure and improved the tooling used for managing custom domain services. To ensure this does not happen again, Okta is enhancing current automated testing of this process.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C1rm7EAB"},"Id":"a1P4z00000C1rm7EAB","CreatedDate":"2025-02-21T18:19:12.000+0000","IncidentId__c":"a9C4z000000TXJ3EAO","UpdateLog__c":"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.\r\n\r\n \r\n\r\nDetection and Impact: \r\n\r\nOn February 11, 2025 at 4:02pm PST Okta was alerted through its monitoring systems of a feature rollout failure in US Cell OK14. On February 12th 5:00am PST Okta began to receive reports that users were unable to view or access resources in the Workflows app. The impact was isolated to customers on US Cell OK14. \r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nOkta determined that the cause was a cache invalidation issue which prevented additional intended feature rollouts from occurring. This caused subsequent failures in the feature rollout system and resulted in Read Only or limited access for some Workflows users.\r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nUpon receiving the support cases Okta took action to remediate the situation. Okta redeployed the feature rollout and a manual workaround guide was made available to impacted customers. All functionality and normal processing resumed once redeployment was complete at 8:35am PST February 12th. \r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nOkta will work to improve our monitoring system in order to ensure cache invalidation does not disrupt deployment sequencing during future releases. Okta will modify the feature rollout system to account for the cache invalidation timeout.\r\n\r\nDuration (# of minutes): 993 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C9TQ0EAN"},"Id":"a1P4z00000C9TQ0EAN","CreatedDate":"2024-04-09T01:25:23.000+0000","IncidentId__c":"a9C4z000000TXHzEAO","UpdateLog__c":"Infrastructure changes to address growth have completed as of 6:00 P.M PDT. Customers may have experienced intermittent latency during the cutover. We have confirmed that this is resolved.\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000C9TQFEA3"},"Id":"a1P4z00000C9TQFEA3","CreatedDate":"2024-04-10T06:28:22.000+0000","IncidentId__c":"a9C4z000000TXHuEAO","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn April 2nd, at 9:00 a.m. PDT, Okta’s monitoring system alerted our team to an issue where some users experienced increased error rates and slow response times, and may have received HTTP 503 response codes in US Cell OK2. \r\n\r\n\r\nRoot Cause Summary\r\n\r\nBased on our investigation and findings, the root cause of increased error rates and slow response times was due to elevated resource usage within an internal cache service supporting sign-on workloads.\r\n\r\n\r\nRemediation Steps\r\n\r\nOkta immediately implemented mitigations, reducing overall resource utilization load on the impacted service, including configuration changes, and rerouting traffic to alternate servers, in order to minimize impact. As of April 2nd at 9:32 a.m. PDT, the service returned to normal operation. \r\n\r\n\r\nPreventative Actions\r\n\r\nOkta has previously implemented actions such as capacity increases, monitoring signals to improve alerting, and developed arun book to effectively handle similar issues. Engineering teams are actively focused on isolating and curing the underlying resource contention issue, and have added new guidance to the operational processes further to improve time to service recovery. \r\n \r\n\r\nTotal Duration\r\n\r\nTotal Duration (Minutes): 33 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0C8EAL"},"Id":"a1P4z00000CC0C8EAL","CreatedDate":"2024-05-09T00:31:46.000+0000","IncidentId__c":"a9C4z000000TXI4EAO","UpdateLog__c":"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 incident.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn May 1st, at 1:01 am PDT, Okta’s monitoring system alerted our team to an issue where some users experienced increased error rates, slow response times, and may have received HTTP 500 response code errors in US Cell OK2. The service was in read-only mode continuing to support authentication flows and read only operations, however write operations would fail during this period.\r\n\r\n\r\nRoot Cause Summary\r\n\r\nBased on our investigation and findings, the root cause of the issue was a sudden increase in system resources usage which caused a primary database to stop responding.\r\n\r\n\r\nRemediation Steps\r\n\r\nOkta immediately implemented mitigations by reducing overall resource utilization load on the impacted service, and executing a database failover per our standard procedure. As of May 1st at 1:22 am PDT, the service returned to normal operation. \r\n\r\n\r\nPreventative Actions\r\n\r\nOkta is taking action to improve capacity and alerting capabilities. Engineering teams are actively focused on isolating and curing the underlying resource contention issue, and have added new guidance to the operational processes further to improve time to service recovery. \r\n\r\n\r\nTotal Duration\r\n\r\nTotal Duration (Minutes): 21 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0ChEAL"},"Id":"a1P4z00000CC0ChEAL","CreatedDate":"2024-05-15T01:55:47.000+0000","IncidentId__c":"a9C4z000001BZVpEAO","UpdateLog__c":"We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are two of 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.\r\n\r\nDetection and Impact: \r\n\r\nOn May 8th at 8:03am PT, the Okta monitoring system alerted our team of customer errors in accessing the Okta Privileged Access (OPA) service in US Cell 2 and EU Cell 3. At the time, customers who were attempting to access OPA teams received an error message and were unable to access the service. \r\n\r\nRoot Cause Summary:\r\n\r\nThe issue was a result of a configuration change, incorrectly applied to all OPA cells, causing the OPA service to be inaccessible to customers when attempting to access OPA teams. \r\n\r\nRemediation Steps:\r\n\r\nUpon receiving alerts, Okta began diagnosing the incident and discovered that the issue was due to a configuration change made to a library used by OPA to manage how we enable features. The team rolled back the change and normal processing resumed at 10:05am PT. \r\n\r\nA second wave was triggered at 2:07pm PT when our build system accidentally pushed the flawed configuration to all cells a second time. The team immediately diagnosed the issue, again rolled back the configuration change, and implemented preventative measures in place by removing the automation so that the issue was not triggered again. \r\n\r\nPreventative Actions:\r\n\r\nTo ensure this does not happen again, Okta is enhancing our testing and promotion procedures to avoid future issues with library configuration changes. We are working to guarantee changes to deployable artifacts are further vetted before their release into our production environments, and once deployed, are immutable from further change.\r\n\r\nTotal Duration\r\n\r\nWave1:\r\n\r\nStart Time: 8:03am PT\r\n\r\nEnd Time: 10:05am PT\r\n\r\nDuration: 122 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0CiEAL"},"Id":"a1P4z00000CC0CiEAL","CreatedDate":"2024-05-15T01:57:26.000+0000","IncidentId__c":"a9C4z000000TXI9EAO","UpdateLog__c":"We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are two of 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.\r\n\r\nDetection and Impact: \r\n\r\nOn May 8th at 8:03am PT, the Okta monitoring system alerted our team of customer errors in accessing the Okta Privileged Access (OPA) service in US Cell 2 and EU Cell 3. At the time, customers who were attempting to access OPA teams received an error message and were unable to access the service. \r\n\r\nRoot Cause Summary:\r\n\r\nThe issue was a result of a configuration change, incorrectly applied to all OPA cells, causing the OPA service to be inaccessible to customers when attempting to access OPA teams. \r\n\r\nRemediation Steps:\r\n\r\nUpon receiving alerts, Okta began diagnosing the incident and discovered that the issue was due to a configuration change made to a library used by OPA to manage how we enable features. The team rolled back the change and normal processing resumed at 10:05am PT. \r\n\r\nA second wave was triggered at 2:07pm PT when our build system accidentally pushed the flawed configuration to all cells a second time. The team immediately diagnosed the issue, again rolled back the configuration change, and implemented preventative measures in place by removing the automation so that the issue was not triggered again. \r\n\r\nPreventative Actions:\r\n\r\nTo ensure this does not happen again, Okta is enhancing our testing and promotion procedures to avoid future issues with library configuration changes. We are working to guarantee changes to deployable artifacts are further vetted before their release into our production environments, and once deployed, are immutable from further change.\r\n\r\nTotal Duration\r\n\r\nTotal Duration (Minutes): \r\n\r\nWave2:\r\n\r\nStart Time: 2:07pm PT\r\n\r\nEnd Time: 2:35pm PT\r\n\r\nDuration: 28 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0DVEA1"},"Id":"a1P4z00000CC0DVEA1","CreatedDate":"2024-05-17T11:32:00.000+0000","IncidentId__c":"a9C4z000000TXIEEA4","UpdateLog__c":"Out of an abundance of caution, an update was posted at 3:54am PDT. However following additional investigation, it was determined that a broad service degradation notice was not applicable.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0FWEA1"},"Id":"a1P4z00000CC0FWEA1","CreatedDate":"2024-06-19T00:05:30.000+0000","IncidentId__c":"a9C4z000000TXIJEA4","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact: \r\n\r\nOn June 10th, at 8:53AM PT, Okta was alerted to a few customers experiencing errors in their Workflows for the Microsoft Teams connector. \r\n\r\nUsers of Okta Workflows in all cells would have experienced errors authenticating, managing, building or executing workflows that used the Microsoft Teams connector cards. \r\n\r\n\r\nRoot Cause Summary:\r\n\r\nThis issue was a result of an internal security policy enhancement that was applied to the OAuth client apps used by the Microsoft Teams Connector. The policy was too restrictive and resulted in traffic being denied to the affected endpoints causing an outage for the specific OAuth client app. Due to the on-behalf nature of the authentication, customer facing Microsoft OAuth client apps were not present in our internal Microsoft Azure staging environment, therefore this scenario was not caught during testing.\r\n \r\n\r\nRemediation Steps:\r\n\r\nThe change was implemented at 5:32AM PT. Immediately upon receiving the support requests at 8:53AM PT, Okta began to diagnose the problem. The issue was identified at 9:36AM PT and the application configuration change was reverted at that time. Okta confirmed at 9:43AM PT that the errors were no longer being observed.\r\n\r\n\r\nFor customers who may have tried to reauthenticate during the impacted timeframe, they may have needed to reauthenticate again after the restoration had taken place. \r\n\r\n\r\nPreventative Actions:\r\n\r\nOkta has already implemented an immediate change control process and is reviewing a number of opportunities to enhance our monitoring capabilities in these areas to prevent this issue from recurring. Okta has also added monitoring to rapidly detect this category of error. \r\n\r\nDuration (# of minutes): 244","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GAEA1"},"Id":"a1P4z00000CC0GAEA1","CreatedDate":"2024-06-25T16:56:51.000+0000","IncidentId__c":"a9C4z000001BZYoEAO","UpdateLog__c":"Okta is investigating an authentication issue with Workflows Google Connectors. Customers who are experiencing authentication failures can unblock the workflows by reauthenticating the connection.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GFEA1"},"Id":"a1P4z00000CC0GFEA1","CreatedDate":"2024-06-25T17:09:14.000+0000","IncidentId__c":"a9C4z000001BZYoEAO","UpdateLog__c":"Customers who may have experienced auth failures with Workflows Google Connectors can unblock the Workflows by reauthenticating the connection. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GUEA1"},"Id":"a1P4z00000CC0GUEA1","CreatedDate":"2024-07-03T06:19:58.000+0000","IncidentId__c":"a9C4z000001BZYoEAO","UpdateLog__c":"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.\r\n\r\n \r\nDetection and Impact: \r\n\r\nOn June 25th, at 7:55 AM PT, Okta was alerted to a Workflows issue where customers experienced authentication failures during flow execution. Users of Workflows Google Connectors created before February 5, 2024 may have experienced 401 Oauth refresh errors with Google Workspace Admin,, Google Calendar, Google Drive, Gmail, and Google Sheets. \r\n\r\n\r\nRoot Cause Summary:\r\n\r\nThe aforementioned authentication errors were caused by performing a Google Services connectors configuration update as part of our ongoing security protection protocol. \r\n\r\n\r\nRemediation Steps:\r\n\r\nOkta began diagnosing the issue immediately upon receiving reports of the error and customers experiencing auth failures were advised to unblock workflows by re-authenticating their connections. A fix was implemented which returned rates to expected range and by 5:05 pm PT pre-incident and normal rates were achieved.\r\n\r\n\r\nPreventative Actions:\r\n\r\nOkta plans to improve our alerting capabilities and enhance our testing processes to preventatively detect this category of error for occurring. \r\n\r\n\r\nTotal Duration\r\n\r\nStart: June 25th, 2024, 4:50 AM PT\r\n\r\nEnd: June 25th 2024, 5:05 PM PT\r\n\r\nDuration (# of minutes): 735","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GZEA1"},"Id":"a1P4z00000CC0GZEA1","CreatedDate":"2024-07-03T18:13:51.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"Our engineering team continues to work with Microsoft support on the root cause of the issue. In parallel, Okta is identifying potential workarounds to mitigate the issue. Please refer to the published KBA that provides affected users with a workaround: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We will continue to provide updates and address the issue as quickly as possible. The next update will be in 24 hours or sooner if new information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GeEAL"},"Id":"a1P4z00000CC0GeEAL","CreatedDate":"2024-07-04T21:21:39.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"No significant update to this incident. Our engineering team continues to work with Microsoft support on the root cause of the issue. In parallel, Okta has identified potential workarounds to mitigate the issue. Please refer to the published KBA that provides affected users with a workaround: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US.\r\n\r\nWe will continue to provide updates and address the issue as quickly as possible. The next update will be in 24 hours or sooner if new information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GjEAL"},"Id":"a1P4z00000CC0GjEAL","CreatedDate":"2024-07-05T17:41:13.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"As of 11:00 AM PST on July 2, a case has been opened with Microsoft, and they are actively reviewing this incident. Authentication to all Microsoft O365 Office applications is working as expected except for OneDrive; users receive an error when authenticating to Microsoft OneDrive via the IdP-initiated SSO login flow (the Okta org app dashboard). Authentication to OneDrive using the SP-initiated SSO (via the Microsoft Office login page) is working normally. A workaround is available for affected users. Please refer to this Knowledge Base article for details: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. \r\n\r\nWe will continue to monitor and will provide updates as they become available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0GyEAL"},"Id":"a1P4z00000CC0GyEAL","CreatedDate":"2024-07-08T20:47:33.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"Our engineering team continues to work with Microsoft support on the root cause of the issue. In parallel, we are deploying a patch today to a subset of Okta cells that will avoid the error when users authenticate to Microsoft OneDrive via the IdP-initiated SSO login flow (the Okta org app dashboard). When Okta's patch is deployed, users will be redirected to the Microsoft 365 single sign-on (SSO) URL and can access the OneDrive app from the Microsoft 365 site. This change is targeted only at Microsoft 365 OneDrive and will not impact any other applications.\r\n\r\nWhile we prepare and deploy the patch, please refer to the published KBA that provides affected users with a workaround: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We will continue to monitor and provide updates as the patch is deployed to all cells.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0H3EAL"},"Id":"a1P4z00000CC0H3EAL","CreatedDate":"2024-07-09T22:26:48.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"Our engineering team continues to deploy the patch to all cells. The patch has been deployed to US-Cell 1, JP-Cell 16, and EMEA-Cell 9. This patch will avoid errors when users authenticate to Microsoft OneDrive via the IdP-initiated SSO login flow (the Okta org app dashboard). Users will be redirected to the Microsoft 365 single sign-on (SSO) URL and can access the OneDrive app from the Microsoft 365 site. This change is targeted only at Microsoft 365 OneDrive and will not impact any other applications. \r\n\r\nAlso, our engineering team continues to work with Microsoft support on the root cause of the issue. While we continue to deploy the patch, please refer to the published KBA that provides affected users with a workaround: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive?language=en_US. We will continue to monitor and provide updates as the patch is deployed to all cells.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0HDEA1"},"Id":"a1P4z00000CC0HDEA1","CreatedDate":"2024-07-10T06:39:11.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"The issue impacting IdP-initiated single sign-on (SSO) for the Microsoft 365 OneDrive application has been addressed. Our engineering team will continue to work with Microsoft support on the root cause of the issue. Additional root cause information will be available within 5 Business days.\r\n\r\nIf you continue to experience the issue, please contact our Okta Customer Support for additional assistance.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0HNEA1"},"Id":"a1P4z00000CC0HNEA1","CreatedDate":"2024-07-10T18:49:54.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"On July 10, Our engineering team deployed a patch for an interim resolution to improve the end user SSO experience. This patch has been applied to all Okta Production cells, and we continue to deploy it in Okta Preview cells. This approach was taken to minimize any introduction of unintended errors for users not experiencing Microsoft 365 OneDrive authentication issues. \r\n\r\nTo learn more about the SSO behavior, please visit the KBA: https://support.okta.com/help/s/article/server-error-in-application-when-attempting-to-access-onedrive.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0HmEAL"},"Id":"a1P4z00000CC0HmEAL","CreatedDate":"2024-07-17T22:29:20.000+0000","IncidentId__c":"a9C4z000000TXIOEA4","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn July 2nd at 6:52pm(PT), Okta became aware of service interruptions with customers attempting to log into OneDrive via the Okta chiclet in some scenarios. Impacted customers were not able to authenticate into OneDrive during this time.\r\n \r\n\r\nRoot Cause Summary\r\n\r\nThe root cause of the incident is that Microsoft, one of Okta’s third party providers, pushed an update to OneDrive. This caused login connectivity errors that impacted some Okta customers in using the service through the Okta dashboard.\r\n \r\n\r\nRemediation Steps\r\n\r\nOkta provided its customers with a number of workarounds to successfully log in. Okta additionally rolled out a hotfix for all customers to redirect the user to the O365 dashboard to login rather than OneDrive on July 10th, at 8:24am. Microsoft resolved the issue in the OneDrive login flow on July 11th at 8:01am at a 60% roll out across their data centers, with an estimated 100% roll out in two weeks. Okta will re-enable the Okta chiclet direct login to OneDrive once Microsoft’s global roll out is completed.\r\n\r\n\r\nPreventative Actions\r\n\r\nWe are closely working with third party providers to notify our customers quickly and help to remediate future incidents. \r\n\r\n\r\nTotal Duration: 12,309 minutes\r\n\r\nJuly 2nd at 6:52pm - July 11th at 8:01am","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0ILEA1"},"Id":"a1P4z00000CC0ILEA1","CreatedDate":"2024-07-26T16:45:00.000+0000","IncidentId__c":"a9C4z000000TXITEA4","UpdateLog__c":"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\r\n \r\n\r\nTiming:\r\nIncident detection start: July 19, 2024, at 07:06 AM UTC\r\n \r\n\r\nDetection:\r\nOkta customers reliant on delegated authentication began reporting that they were unable to log in to Okta, and Okta teams were able to correlate these symptoms with CrowdStrike outage reports.\r\n \r\n\r\nImpact:\r\nOkta customers with Okta agents hosted on a Windows system affected by CrowdStrike’s Falcon sensor may have experienced an inability to perform actions that rely on an active Okta agent. CrowdStrike’s Falcon sensor disruptions would prevent the Okta agent from running. Notably, user sign-on reliant on delegated authentication could fail, leaving users unable to sign in to Okta.\r\n \r\n\r\nRoot Cause:\r\nCrowdStrike released a sensor configuration update to Windows systems, which triggered a logic error resulting in system crashes (BSOD) on impacted systems. The issue affected systems running Falcon sensor for Windows version 7.11 and above that downloaded the updated configuration between 04:09 UTC and 05:27 UTC on July 19, 2024.\r\n \r\nAny Okta agents installed on an impacted Windows system would be unable to run until the CrowdStrike issue was resolved.\r\n \r\n\r\nRemediation Steps:\r\nCrowdStrike remediated the sensor configuration update error at 05:27 UTC on July 19, 2024. Okta Support advised impacted customers to remediate the systems affected by CrowdStrike in order to get the Okta agents running again.\r\n \r\n\r\nCustomers seeking ways to mitigate disruptions to delegated authentication can review when caching is used here: https://support.okta.com/help/s/article/Cache-AD-Credentials-using-Delegated-Authentication\r\n\r\n\r\nMore details, as provided by CrowdStrike, can be found here: https://www.crowdstrike.com/blog/falcon-update-for-windows-hosts-technical-details/","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0IpEAL"},"Id":"a1P4z00000CC0IpEAL","CreatedDate":"2024-08-07T18:40:46.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our downstream providers regarding the SMS OTP delivery delays. We recommend leveraging different MFA options for end users.\r\n\r\nOne of our telephony providers has implemented a temporary workaround as it continues to work with downstream providers on the operator’s side.\r\n\r\nWe will resolve this incident once we have received confirmation the issue has been resolved from our downstream provider.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0J4EAL"},"Id":"a1P4z00000CC0J4EAL","CreatedDate":"2024-08-09T18:15:22.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Okta continues to monitor the current situation with our downstream providers regarding the SMS OTP delivery delays. We recommend leveraging different MFA options for end users.\r\n\r\nOur telephony provider advised that the issue is specific to the carrier in China. They have implemented additional improvements with their providers at 3 AM PDT and 5 AM PDT, which have returned delivery success rates to expected levels.\r\n\r\nOur support team is working with our impacted customers to confirm the resolution. We will resolve this incident once we have received confirmation from our customers that the issue is resolved.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0J9EAL"},"Id":"a1P4z00000CC0J9EAL","CreatedDate":"2024-08-12T15:31:07.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"An issue impacting SMS OTP to end users in China has been resolved. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0JiEAL"},"Id":"a1P4z00000CC0JiEAL","CreatedDate":"2024-08-19T20:29:29.000+0000","IncidentId__c":"a9C4z000000TXIYEA4","UpdateLog__c":"Timing:\r\n\r\nIncident start: August 6, 2024, at 12:12 AM PDT\r\n\r\nIncident resolved: August 9, 2024, at 4:07 AM PDT\r\n\r\n\r\nDetection:\r\n\r\nOkta Engineering was notified on August 6, 2024, at 9:39 PM PDT as Okta customers began reporting failures in receiving SMS OTP messages in China.\r\n\r\n \r\nImpact:\r\n\r\nUsers in China may have experienced failures in receiving SMS OTP messages, which disrupted their ability to complete authentication. This affected both individual users and organizations relying on SMS-based multi-factor authentication.\r\n\r\n \r\nRoot Cause:\r\n\r\nThe disruption in SMS OTP delivery was caused by the sudden enforcement of regulatory changes implemented by China Mobile, one of China’s largest mobile carriers, on August 6, 2024. This change required all SMS messages sent to China to include a pre-registered signature associated with a local Chinese entity. As a result, SMS traffic originating from brands without a Chinese presence was blocked or filtered by the local carrier, leading to widespread delivery failures.\r\n\r\n \r\nPreventive Actions:\r\n\r\nOkta teams have worked with our telephony providers to establish a more robust routing mechanism that includes pre-registered Chinese entity signatures to comply with local regulations.\r\n\r\nAdditional details about the new standard signatures can be found here: https://support.okta.com/help/s/article/new-standard-signatures-applied-to-sms-sent-to-certain-chinese-carriers\r\n\r\n \r\nRemediation Steps:\r\n\r\nOkta strongly recommends customers adopt alternative MFA methods, which are more reliable and less susceptible to local regulatory changes compared to SMS-based OTPs.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0JnEAL"},"Id":"a1P4z00000CC0JnEAL","CreatedDate":"2024-08-21T05:48:30.000+0000","IncidentId__c":"a9C4z000000TXIdEAO","UpdateLog__c":"On August 13th at 12:02 am PST, Okta was alerted to an anomaly in US cell 14 with some customers using AD, LDAP and Okta On Prem Provisioning (OPP) agents. A small set of customers experienced intermittent Okta agent connectivity issues, timeouts, and slow authentication response times, and may have received 401 and 500 error codes. \r\n\r\n\r\nImpact:\r\n\r\nDelegated Authentication users would have seen intermittent delays and errors logging in, while users who updated their profiles or their passwords might have seen additional errors.\r\n\r\n\r\nRoot Cause:\r\n\r\nDuring scheduled maintenance of a messaging cluster, the application that retrieves messages from this cluster experienced an unexpected error. This error caused it to flood the messaging cluster with network connections. The cluster subsequently began rejecting new connections and the system could not process agent traffic.\r\n\r\n\r\nRemediation Steps:\r\n\r\nImmediately upon receiving alerts, the Okta team began diagnosing the issue. The initial focus of the investigation was the messaging cluster, but upon further diagnosis, it became clear that it was the aforementioned application, and restarting this application restored service. \r\n\r\n\r\nPreventative Action:\r\n\r\nTo ensure this issue does not recur, Okta has added capacity to the messaging cluster. Okta is also remediating the software error that caused the connection issue, tuning network connectivity for the messaging cluster, and adding new incident response tooling. Finally, enhanced monitoring with updated runbooks for swifter response have been put in place.\r\n\r\n\r\nDuration (# of minutes): 245","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KMEA1"},"Id":"a1P4z00000CC0KMEA1","CreatedDate":"2024-09-17T18:31:34.000+0000","IncidentId__c":"a9C4z000001BZbnEAG","UpdateLog__c":"An issue impacting the Okta Sign-in Widget (SIW) for some end users using an embedded Internet Explorer browser has been resolved. Our engineering team has confirmed the resolution. \r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KgEAL"},"Id":"a1P4z00000CC0KgEAL","CreatedDate":"2024-09-19T15:27:47.000+0000","IncidentId__c":"a9C4z000001BZc7EAG","UpdateLog__c":"Customers with the early access feature \"Same-Device Enrollment for Okta FastPass\" are not able to enroll Okta Verify accounts via QR code or SMS. Okta System Logs will indicate that the enrollment is successful, but the account will not be added to the Okta Verify app due to an error \"Operation Failed—unknown ('E0000191').\" \r\n\r\nOkta Engineering teams are working to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KlEAL"},"Id":"a1P4z00000CC0KlEAL","CreatedDate":"2024-09-19T15:55:58.000+0000","IncidentId__c":"a9C4z000001BZc7EAG","UpdateLog__c":"Customers with the early access feature \"Same-Device Enrollment for Okta FastPass\" are not able to enroll Okta Verify accounts via QR code or SMS. Users in impacted orgs that attempt to enroll receive an error \"Operation Failed—unknown ('E0000191').\"\r\n\r\nOkta Engineering has isolated the issue and has disabled “Same-Device Enrollment for Okta FastPass.\" We are seeing the error rates subside and will continue to monitor the situation.\r\n\r\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KmEAL"},"Id":"a1P4z00000CC0KmEAL","CreatedDate":"2024-09-19T16:21:35.000+0000","IncidentId__c":"a9C4z000001BZc7EAG","UpdateLog__c":"Customers with the early access feature \"Same-Device Enrollment for Okta FastPass\" are not able to enroll Okta Verify accounts via QR code or SMS. Users in impacted orgs that attempt to enroll receive an error \"Operation Failed—unknown ('E0000191').\"\r\n\r\nOkta Engineering has isolated the issue and has disabled “Same-Device Enrollment for Okta FastPass\" in all cells other than OK11 (which is currently underway). We continue to see the error rates subside and will continue to monitor the situation.\r\n\r\nWe’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KqEAL"},"Id":"a1P4z00000CC0KqEAL","CreatedDate":"2024-09-19T16:31:03.000+0000","IncidentId__c":"a9C4z000001BZc7EAG","UpdateLog__c":"Customers with the early access feature \"Same-Device Enrollment for Okta FastPass\" were not able to enroll Okta Verify accounts via QR code or SMS. Users in impacted orgs that attempt to enroll were shown an error \"Operation Failed—unknown ('E0000191').\"\r\n\r\nThis issue impacting Okta Verify Enrollment has been addressed. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0KvEAL"},"Id":"a1P4z00000CC0KvEAL","CreatedDate":"2024-09-23T23:21:27.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta's Engineering Team is continuing to work on a hotfix release to mitigate the '400 Bad Request' error when federating new domains. The hotfix to resolve this issue will be deployed at approximately 10:00pm US Pacific Time, today, September 23, 2024. \r\n\r\nIn the meantime, the team has documented a workaround, available here: \r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe’ll provide another update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0L0EAL"},"Id":"a1P4z00000CC0L0EAL","CreatedDate":"2024-09-23T23:51:20.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta's Engineering Team is continuing to work on a hotfix release to mitigate the '400 Bad Request error when federating new domains. Our engineering team is running tests and validating the patch to be deployed at approximately 10:00pm US Pacific Time today, September 23, 2024.\r\n\r\nIn the meantime, the team has documented a workaround, available here:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe'll provide another update in an hour or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0L5EAL"},"Id":"a1P4z00000CC0L5EAL","CreatedDate":"2024-09-24T00:04:06.000+0000","IncidentId__c":"a9C4z000001BZbnEAG","UpdateLog__c":"We sincerely apologize for any impact this incident has caused you, your business, and your customers. At Okta, trust and transparency are our top priorities. The facts regarding this incident are outlined below. We are committed to implementing improvements to the service to prevent future occurrences of this incident.\r\n\r\nDetection and Impact \r\nOn September 16th at 11:57 AM PT, Okta was alerted that a few customers using embedded legacy browsers encountered a Javascript error when logging in. \r\n\r\nUsers were presented with a pop-up window displaying a script error and asked if they would like to continue running scripts. When selecting ‘Yes,’ the page would continue to load correctly.\r\n\r\n\r\nRoot Cause Summary\r\nA monitoring enhancement to detect client side errors was rolled out, however the library contained modern syntax, which was unrecognized by legacy browsers, resulting in a JS syntax error. \r\n\r\n\r\nRemediation Steps\r\nThe monitoring enhancement was rolled out at 10:31 AM PT on September 16th. On September 17th, Okta Engineering began rolling back the monitoring changes. The root cause of the issue was identified at 9:42 AM PT. Okta confirmed at 11:17 AM PT that the errors were no longer being observed.\r\n\r\n\r\nPreventative Actions\r\nOkta is reviewing and updating our runbooks, improving support case escalation processes to decrease response and resolution times. Additional changes to our rollout processes to mitigate risk are also being applied.\r\n\r\nDuration (# of minutes): 1495 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LAEA1"},"Id":"a1P4z00000CC0LAEA1","CreatedDate":"2024-09-24T18:59:26.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"Okta's Engineering Team continues to deploy the patch in cell OK7 to mitigate the '400 Bad Request' error when federating new domains. We expect this deployment to be complete by approximately 1:30 p.m. US Pacific Time on September 24, 2024.\r\n\r\nThe team has documented a solution in the tech note below that will need to be applied either before or after the hotfix is deployed:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nWe'll provide another update in two hours or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LFEA1"},"Id":"a1P4z00000CC0LFEA1","CreatedDate":"2024-09-24T20:02:03.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"The patch deployment to all cells to mitigate the '400 Bad Request' error when federating new domains has been completed. Okta's Engineering Team has confirmed the resolution.\r\n\r\nA documented solution in the tech note below will need to be applied if it has not already been:\r\n\r\nhttps://support.okta.com/help/s/article/microsoft-o365-federation-issue-september-23-2024\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LKEA1"},"Id":"a1P4z00000CC0LKEA1","CreatedDate":"2024-09-25T23:21:25.000+0000","IncidentId__c":"a9C4z000000TXIiEAO","UpdateLog__c":"Timing:\r\nIncident start: September 17, 2024, at 5:00 PM PDT\r\nIncident resolved: September 17, 2024 at 7:28 PM PDT\r\n\r\nDetection:\r\nOkta Customers reported that users in China were not receiving their multi-factor authentication (MFA) one-time passwords (OTP) via SMS.\r\n\r\nImpact:\r\nUsers in China were unable to receive SMS-based OTPs for MFA during the incident period.\r\n\r\nRoot Cause:\r\nOne of Okta’s telephony providers implemented an unannounced configuration change, leading to SMS delivery disruption to users in China.\r\n\r\nRemediation Steps:\r\nOkta teams immediately notified our telephony provider of the disruption. The provider was able to identify and reverse the problematic change, restoring SMS service to China.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LPEA1"},"Id":"a1P4z00000CC0LPEA1","CreatedDate":"2024-09-27T00:46:38.000+0000","IncidentId__c":"a9C4z000001BZc7EAG","UpdateLog__c":"We sincerely apologize for any impact this incident has caused you, your business, and your customers. At Okta, trust and transparency are our top priorities. The facts regarding this incident are outlined below. We are committed to implementing improvements to the service to prevent future occurrences of this incident.\r\n\r\nDetection and Impact: \r\nOn September 19th, at 1:22 AM PT, Okta began receiving customer reports about issues encountered when adding a new account using Okta Verify on their mobile devices. \r\n\r\nAt the time, some customers attempting to enroll a device using Okta Verify would receive an error on the device upon completing the process even though the end user dashboard would show the device as enrolled. \r\n\r\nRoot Cause Summary:\r\nOkta determined that a change to the new ‘same device enrollment flow’ was causing other enrollment flows (email, QR Code) to fail due to a cached transaction handle interfering with the usage of the current session's transaction handle. This impacted only customers who enabled the Early Access feature “Same-Device Enrollment for Okta FastPass” for their organization.\r\n\r\nRemediation Steps:\r\nAfter confirming the details of the incident and successfully reproducing the error, Okta rolled back the feature flag for the orgs that had enabled this feature, and the issue was resolved at 9:25 AM PT on September 19th. We have resolved the defective code and rolled out the Same-Device Enrollment feature back to Self-Service Early Access so customers can turn it back on. Please refer to the knowledge base article for more details: https://support.okta.com/help/s/article/same-device-enrollment-for-okta-fastpass\r\n\r\nPreventative Actions:\r\nOkta is reviewing and adding additional test automation coverage for this functionality. Additionally, processes are being reviewed to ensure the issue does not occur again.\r\n\r\nDuration (# of minutes): 2,728","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LUEA1"},"Id":"a1P4z00000CC0LUEA1","CreatedDate":"2024-10-03T17:45:49.000+0000","IncidentId__c":"a9C4z000001BZcCEAW","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact \r\n\r\nOn September 23rd at 10:49am (PT), Okta’s Engineering team became aware of errors for customers attempting to federate new domains to the Office 365 application. Impacted users attempting to perform Service Provided (SP) initiated authentication flows received 400 (“Bad Request”) errors. Identity Provider (IdP) initiated authentication flows worked normally during this time. \r\n\r\n\r\nRoot Cause Summary\r\n\r\nThe root cause of the incident is that Okta’s third party provider pushed an unannounced backwards-incompatible update to the WS Fed implementation for Office 365. This caused application Single Sign-on (SSO) errors for newly federated domain users.\r\n \r\n\r\nRemediation Steps\r\n\r\nOkta provided its customers with a work around to successfully use this service. In parallel, Okta rolled out a hotfix for all cells to adhere to the workaround suggested by the third party. Okta observed that access rates began to improve and, on September 24th at 1:09pm PT, Okta confirmed service functionality was restored. \r\n \r\n\r\nPreventative Actions\r\n\r\nWe are closely working with third party providers to notify Okta and our mutual customers quickly and help to remediate future incidents.\r\n\r\n\r\nTotal Duration\r\n\r\nTotal Duration: 12 days, 10 hours, and 2 minutes\r\n\r\nActual Time: Sept 13th, 2024 02:53 AM PT - Sep 24th, 2024, 01:09 PM","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LZEA1"},"Id":"a1P4z00000CC0LZEA1","CreatedDate":"2024-10-03T23:39:45.000+0000","IncidentId__c":"a9C4z000001BZcHEAW","UpdateLog__c":"Okta is continuing roll back of the Datadog app integration version. We’ll provide another update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LeEAL"},"Id":"a1P4z00000CC0LeEAL","CreatedDate":"2024-10-04T00:25:59.000+0000","IncidentId__c":"a9C4z000001BZcHEAW","UpdateLog__c":"Okta is continuing roll back of the Datadog app integration version. We’ll provide another update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LjEAL"},"Id":"a1P4z00000CC0LjEAL","CreatedDate":"2024-10-04T00:44:01.000+0000","IncidentId__c":"a9C4z000001BZcHEAW","UpdateLog__c":"The app integration rollback for all cells to mitigate the Datadog SSO issue has been completed.\r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LoEAL"},"Id":"a1P4z00000CC0LoEAL","CreatedDate":"2024-10-10T21:00:28.000+0000","IncidentId__c":"a9C4z000001BZcREAW","UpdateLog__c":"The Engineering team has confirmed that only the provisioning setup is impacted and is still investigating the root cause to mitigate the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LtEAL"},"Id":"a1P4z00000CC0LtEAL","CreatedDate":"2024-10-10T21:39:24.000+0000","IncidentId__c":"a9C4z000001BZcREAW","UpdateLog__c":"The Engineering team has confirmed that only the provisioning setup is impacted and is still investigating the root cause to mitigate the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0LyEAL"},"Id":"a1P4z00000CC0LyEAL","CreatedDate":"2024-10-10T22:14:35.000+0000","IncidentId__c":"a9C4z000001BZcREAW","UpdateLog__c":"Okta customers attempting to setup an Office 365 provisioning integration may run into issues due to Microsoft configurations requiring MFA for admin service accounts. Administrators should review their Microsoft configurations if they face an error when validating the API integration. Customers should follow the guidance outlined in our documentation: \r\n\r\n<a href=https://help.okta.com/en-us/content/topics/apps/office365-deployment/provision-users.htm#1” target=\"_blank\">https://help.okta.com/en-us/content/topics/apps/office365-deployment/provision-users.htm#1</a>\r\n\r\nThe following KB article is available with details on how to ensure the configuration is correct: <a href=”https://support.okta.com/help/s/article/how-to-check-for-mfa-enforcement-in-entra?language=en_U” target=\"_blank\">https://support.okta.com/help/s/article/how-to-check-for-mfa-enforcement-in-entra?language=en_US</a>","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0MSEA1"},"Id":"a1P4z00000CC0MSEA1","CreatedDate":"2024-10-21T17:20:04.000+0000","IncidentId__c":"a9C4z000001BZcREAW","UpdateLog__c":"Timing:\r\n\r\nIncident start: October 3, 2024, at 6:38 PM PDT\r\n\r\nIncident resolved: October 10, 2024, at 3:22 PM PDT\r\n\r\n\r\nDetection:\r\n\r\nCustomers began reporting that they were unable to save their Office 365 application in Okta when “User Sync” or “Universal Sync” was selected for provisioning.\r\n\r\n\r\nImpact:\r\n\r\nCustomers would receive a 400 error when attempting to save an Office 365 application after completing the Microsoft consent page.\r\n\r\n\r\nRoot Cause:\r\n\r\nOkta Engineering has confirmed that impacted customers had Microsoft Entra conditional access policy enforcing MFA for the service account used by Okta’s provisioning service. Accounts used for provisioning must not have MFA or require any manual intervention.\r\n\r\n\r\nRemediation Steps:\r\n\r\nOkta Customer Support advised customers to exclude the service account from the conditional access policy. Once the service account was excluded, the provisioning service began functioning as expected, allowing the customer to save the Office 365 app in Okta without encountering the HTTP 400 error.\r\n\r\nGuidance is provided in Okta’s Office 365 Provisioning documentation:\r\n\r\n<a href=https://help.okta.com/en-us/content/topics/apps/office365-deployment/provision-users.htm#1” target=\"_blank\">https://help.okta.com/en-us/content/topics/apps/office365-deployment/provision-users.htm#1</a>\r\n\r\nSteps for explicitly checking for MFA enforcement can be found here:\r\n\r\n<a href=”https://support.okta.com/help/s/article/how-to-check-for-mfa-enforcement-in-entra?language=en_U” target=\"_blank\">https://support.okta.com/help/s/article/how-to-check-for-mfa-enforcement-in-entra?language=en_US</a>","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0dkEAD"},"Id":"a1P4z00000CC0dkEAD","CreatedDate":"2024-10-28T14:59:41.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"Okta's Engineering team has become aware of an import and update issue affecting customers in OK14. During this time, customers in OK14 may experience imports and updates that progress very slowly. Okta's Engineering team is investigating and working to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0dpEAD"},"Id":"a1P4z00000CC0dpEAD","CreatedDate":"2024-10-28T15:32:39.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"Okta Engineering continues to investigate and work to mitigate import and update issues affecting customers in OK14. During this time, customers in OK14 may experience imports and updates that progress very slowly and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0duEAD"},"Id":"a1P4z00000CC0duEAD","CreatedDate":"2024-10-28T16:00:04.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"Okta Engineering has identified the potential cause of the issue and continues to work towards mitigating the disruption. Customers in OK14 may experience imports and updates that progress very slowly, and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0dzEAD"},"Id":"a1P4z00000CC0dzEAD","CreatedDate":"2024-10-28T16:27:59.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"Okta Engineering continues to work towards mitigating the disruption. Customers in OK14 may experience imports and updates that progress very slowly, and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0e4EAD"},"Id":"a1P4z00000CC0e4EAD","CreatedDate":"2024-10-28T16:46:08.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"Okta continues to monitor the current situation with the import and update delays in OK14. Our monitoring shows that import and update throughput is improving and delays are reducing. \r\n\r\nOur next update will be in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0e9EAD"},"Id":"a1P4z00000CC0e9EAD","CreatedDate":"2024-10-28T17:18:40.000+0000","IncidentId__c":"a9C4z000001BZdAEAW","UpdateLog__c":"An issue impacting import and update performance in OK14 has been addressed. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0fbEAD"},"Id":"a1P4z00000CC0fbEAD","CreatedDate":"2024-11-19T20:27:39.000+0000","IncidentId__c":"a9C4z000001BZecEAG","UpdateLog__c":"At 8:40am on November 19th PST, the OIN team became aware of an Import issue with the Paylocity OIN integration affecting customers on all cells of the Okta Workforce Identity Cloud environment. During this time customers may experience import roadblocks. Okta recommends not running imports from Paylocity during this investigation.\r\n\r\nOkta Engineering has contacted Paylocity and is working to resolve this as quickly as possible.\r\n\r\nWe’ll provide an update in 60 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0fgEAD"},"Id":"a1P4z00000CC0fgEAD","CreatedDate":"2024-11-19T21:22:56.000+0000","IncidentId__c":"a9C4z000001BZecEAG","UpdateLog__c":"Okta Engineering has received confirmation from Paylocity that this issue is resolved and is monitoring our backend logging for the Paylocity OIN integration. Our logging indicates an improvement in import success rates. At this time, customers should resume Paylocity imports.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0flEAD"},"Id":"a1P4z00000CC0flEAD","CreatedDate":"2024-11-19T21:36:56.000+0000","IncidentId__c":"a9C4z000001BZecEAG","UpdateLog__c":"The Paylocity OIN integration import issue for all Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor Paylocity OIN integration import performance.\r\n\r\nAdditional root cause information will be \r\navailable within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0hIEAT"},"Id":"a1P4z00000CC0hIEAT","CreatedDate":"2024-12-11T19:41:27.000+0000","IncidentId__c":"a9C4z000001BZg9EAG","UpdateLog__c":"Okta's Engineering Team has identified an issue affecting end-user and admin login and has taken remediation steps on affected cells. We are currently seeing an improvement in login success rates and will continue to monitor for full recovery.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0hNEAT"},"Id":"a1P4z00000CC0hNEAT","CreatedDate":"2024-12-11T19:50:30.000+0000","IncidentId__c":"a9C4z000001BZg9EAG","UpdateLog__c":"The login issue for all impacted Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor for any further errors.\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0hXEAT"},"Id":"a1P4z00000CC0hXEAT","CreatedDate":"2024-12-13T15:00:17.000+0000","IncidentId__c":"a9C4z000001BZgOEAW","UpdateLog__c":"Okta teams have become aware of disruption affecting customers in all cells. During this time, customer admins may be unable to access the Okta Help Center, and users may see HTTP 429 errors when attempting to log in. Okta teams are investigating and working to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0hcEAD"},"Id":"a1P4z00000CC0hcEAD","CreatedDate":"2024-12-13T15:33:58.000+0000","IncidentId__c":"a9C4z000001BZgOEAW","UpdateLog__c":"Okta Engineering has isolated the issue, and Okta teams have made DNS changes to mitigate the disruption. Customer admins should begin to have access to the Okta Help Center, and users should stop seeing HTTP 429 errors as DNS continues to propagate. We are seeing the error rates subside, and we will continue to monitor the situation. We’ll provide an update in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0hhEAD"},"Id":"a1P4z00000CC0hhEAD","CreatedDate":"2024-12-13T15:45:51.000+0000","IncidentId__c":"a9C4z000001BZgOEAW","UpdateLog__c":"An issue impacting user login has been resolved. Our monitoring shows a return to normal conditions, and we will continue to monitor for any further errors. Additional root cause information will be available within 5 business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0i6EAD"},"Id":"a1P4z00000CC0i6EAD","CreatedDate":"2024-12-18T23:59:01.000+0000","IncidentId__c":"a9C4z000001BZg9EAG","UpdateLog__c":"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 kind of incident.\r\n\r\nDetection and Impact:\r\nOn December 11th at 10:42AM PT, Okta internal monitoring alerted on-call responders regarding an issue across cells OK1 and EU1, and later on, limited impact in OK5, OK8, and OK16.\r\n\r\nDuring this time, some users were unable to load the Okta Sign In Widget, preventing authentication actions. Some admins were unable to open support cases unless they had an active session within the Okta Help Center. Existing sessions for end users and admins continued to operate normally. All other Okta products and services continued to function as designed.\r\n\r\nRoot Cause Summary:\r\nThe Okta engineering team was attempting to preemptively mitigate an identified risk in an upcoming version. While the change followed all processes for such changes, it was applied incorrectly ahead of the deployment causing the login page to reference an unavailable version of the Okta Sign in Widget in impacted production cells. For per-environment timelines, please review the specific timelines below.\r\n\r\nTimelines:\r\nOK1 10:32AM - 11:08AM PT 36 minutes [SIW Gen2]\r\n\r\nOK1 10:32AM - 11:15AM PT 43 minutes [SIW Gen3]\r\n\r\nEU1 10:40AM - 11:15AM PT 35 minutes [SIW Gen2]\r\n\r\nEU1 10:40AM - 11:18AM PT 38 minutes [SIW Gen3]\r\n\r\nOK8 11:01AM - 11:25AM PT 24 minutes [SIW Gen 2]\r\n\r\nOK8 11:01AM - 11:30AM PT 29 minutes [SIW Gen 3]\r\n\r\nOK16 10:59AM - 11:23AM PT 24 minutes [SIW Gen 2]\r\n\r\nOK5 10:47AM - 11:47AM PT 60 minutes [SIW Gen 2]\r\n\r\nRemediation Steps:\r\nUpon receiving automated alerts and support cases, Okta began diagnosing the incident and discovered the root cause at 10:58AM PT. At that time, the team started incrementally remediating the issue. The team rolled back the change across all impacted environments by 11:47AM PT.\r\n\r\nPreventative Actions:\r\nIn order to prevent similar incidents from happening again, Okta has immediately addressed the following:\r\n\r\nUpdated controls and enhanced approval flows for configuration changes\r\n\r\nEnhanced monitoring and alerting for content load errors for faster detection and response\r\n\r\nDuration (Minutes): 78","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0k2EAD"},"Id":"a1P4z00000CC0k2EAD","CreatedDate":"2025-01-16T02:42:55.000+0000","IncidentId__c":"a9C4z000001BZi5EAG","UpdateLog__c":"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. \r\n\r\nDetection and Impact: \r\n\r\nOn January 9, 2025 starting at approximately 10:42AM PT, Okta was alerted to an issue where Advanced Server Access (ASA) customers were unable to access the ASA UI console. All ASA UI actions were unavailable, including logins and administrative actions within the console. Any ASA actions via client API were unimpacted. \r\n\r\nRoot Cause Summary: \r\n\r\nOkta’s Engineering team determined the root cause of the issue was a recent update to the ASA dashboard which referenced a missing JavaScript asset. This resulted in all ASA UI access being temporarily unavailable. This did not impact client API access, server registration or other ASA resource actions. \r\n\r\nRemediation Steps & Preventative Actions:\r\n\r\nOkta identified the issue at 11:10AM PT and Okta engineering deployed the solution at 11:19AM PT, reverting to an earlier version and restoring access. \r\n\r\nOkta is adding additional automated test scenarios to prevent similar incidents from happening in the future. We will increase monitoring and implement additional sign-off during future service updates.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0loEAD"},"Id":"a1P4z00000CC0loEAD","CreatedDate":"2025-02-12T15:36:45.000+0000","IncidentId__c":"a9C4z000000TXJ3EAO","UpdateLog__c":"Okta is aware of an issue causing Flows and Connection tabs from showing in the Okta Workflows Console. The steps in the following KB can be used to resolve while Okta teams work to perform a permanent fix: https://support.okta.com/help/s/article/no-access-to-flows-or-connections-tabs-in-workflows-console?language=en_US","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0ltEAD"},"Id":"a1P4z00000CC0ltEAD","CreatedDate":"2025-02-12T15:41:36.000+0000","IncidentId__c":"a9C4z000000TXJ3EAO","UpdateLog__c":"Okta is aware of an issue causing Flows and Connection tabs from showing in the Okta Workflows Console. The steps in the following KB can be used to resolve while Okta teams work to perform a permanent fix: https://support.okta.com/help/s/article/no-access-to-flows-or-connections-tabs-in-workflows-console?language=en_US\r\n\r\nWe will provide another update in 30 minutes or less if more details become available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1P4z00000CC0lyEAD"},"Id":"a1P4z00000CC0lyEAD","CreatedDate":"2025-02-12T15:59:45.000+0000","IncidentId__c":"a9C4z000000TXJ3EAO","UpdateLog__c":"An issue impacting access to Workflows for admins in OK14 has been resolved. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2N2AQ"},"Id":"a1PKZ000000fz2N2AQ","CreatedDate":"2025-04-04T16:27:39.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"We're currently investigating an issue causing the degradation of OIG Access Requests.\r\nOur engineering team is actively working to identify and resolve the problem.\r\nWe will provide another update in 30 minutes or less if more details become available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2Z2AQ"},"Id":"a1PKZ000000fz2Z2AQ","CreatedDate":"2025-04-04T16:48:42.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"We're currently investigating an issue causing the degradation of OIG Access Requests. Our engineering team is actively working to identify and resolve the problem. We will provide another update in 30 minutes or less if more details become available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2e2AA"},"Id":"a1PKZ000000fz2e2AA","CreatedDate":"2025-04-04T17:05:16.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2j2AA"},"Id":"a1PKZ000000fz2j2AA","CreatedDate":"2025-04-04T17:06:08.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2o2AA"},"Id":"a1PKZ000000fz2o2AA","CreatedDate":"2025-04-04T17:24:31.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2t2AA"},"Id":"a1PKZ000000fz2t2AA","CreatedDate":"2025-04-04T17:50:37.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz2y2AA"},"Id":"a1PKZ000000fz2y2AA","CreatedDate":"2025-04-04T18:13:31.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"An issue impacting Okta Identity Governance (OIG) access requests for users in all US Production Cells has been resolved. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fz6h2AA"},"Id":"a1PKZ000000fz6h2AA","CreatedDate":"2025-04-11T21:37:34.000+0000","IncidentId__c":"a9CKZ000000sXtm2AE","UpdateLog__c":"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. \r\n\r\nDetection and Impact: \r\n\r\nOn Friday, April 4th at 7:59 am (PT), Okta’s monitoring systems alerted our Engineering team that some OIG users in US Commercial Cells were experiencing slow requests and request errors for governance requests via Okta Inbox. Retry attempts would eventually succeed. \r\n\r\nRoot Cause Summary:\r\n\r\nBased on our investigation, an increase in a specific query requiring significant resources resulted in extra database load. This resulted in increased query latency, workload connection errors, and inbound API call failures. \r\n\r\nRemediation Steps: \r\n\r\nUpon receiving alerts, Okta began diagnosing the issue and launched a series of scaling activities. The team identified the root cause of the issue and took action to remediate the situation. At approximately 9:42 am (PT) Okta saw a decrease in query delays in the affected cell. At 9:43 am (PT) service latency returned to normal operation. \r\n\r\nPreventative Actions:\r\n\r\nTo ensure this does not happen again, teams are remediating expensive database operations to prevent recurrence of this issue. Okta is looking into enhancing monitoring to identify expensive database operations faster. Additionally, runbooks are being updated to allow for faster remediation","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000fzf82AA"},"Id":"a1PKZ000000fzf82AA","CreatedDate":"2025-04-23T22:17:50.000+0000","IncidentId__c":"a9CKZ000000oLkk2AE","UpdateLog__c":"The 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.\r\n\r\n\r\nTiming:\r\n\r\nIncident start: April 14, 2025, at 1:40 PM PDT\r\n\r\nIncident resolved: April 15, 2025, at 5:54 PM PDT\r\n\r\nDetection:\r\n\r\nOkta Engineering noticed errors related to this feature on April 15, 2025. \r\n\r\nImpact:\r\n\r\nCustomers may have seen failures when attempting to set up Apple Business Manager (ABM) integrations.\r\n\r\nSummary:\r\n\r\nApple confirmed disruptions to ABM that were resolved on April 15, 2025, at 5:54 PM PDT.\r\n\r\nPreventive Actions:\r\n\r\nOkta has introduced additional logging to identify similar disruptions closer to their start.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g0N02AI"},"Id":"a1PKZ000000g0N02AI","CreatedDate":"2025-04-30T16:44:59.000+0000","IncidentId__c":"a9CKZ000000oLkp2AE","UpdateLog__c":"The 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.\r\n\r\n\r\nTiming:\r\n\r\nIncident start: April 23, 2025, at 1:55 PM PDT\r\n\r\nIncident resolved: April 23, 2025, at 2:55 PM PDT\r\n\r\n\r\nImpact:\r\n\r\nDuring the disruption period, customers and users in standard production and preview cells did not receive expected system-generated emails. This included emails for password resets, MFA when using email as a factor, account activation, and any other email notifications related to org or policy changes. These emails were delayed and only began to arrive once Okta’s third-party email provider recovered at approximately 2:55 PM PDT.\r\n\r\n\r\nRoot Cause:\r\n\r\nOkta’s third-party downstream email provider experienced a disruption that prevented emails from being sent during the disruption period.\r\n\r\nPreventive Actions:\r\n\r\nOkta has added additional monitoring and alerting to detect such issues more rapidly in the future, enabling us to validate the issue with our downstream providers more quickly and respond.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g4pS2AQ"},"Id":"a1PKZ000000g4pS2AQ","CreatedDate":"2025-06-11T18:16:21.000+0000","IncidentId__c":"a9CKZ000000sXyD2AU","UpdateLog__c":"Engineering has identified and resolved an issue where end users are unable to access Okta Personal vault due to a failed DB migration. \r\n\r\nEnd user data was unaffected.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g4qb2AA"},"Id":"a1PKZ000000g4qb2AA","CreatedDate":"2025-06-12T20:06:32.000+0000","IncidentId__c":"a9CKZ000000sXyI2AU","UpdateLog__c":"Okta monitoring shows push notifications on Android Okta Verify due to a third-party outage have recovered.\n\nAdditional root cause information will be available within 10 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g4tO2AQ"},"Id":"a1PKZ000000g4tO2AQ","CreatedDate":"2025-06-16T21:33:01.000+0000","IncidentId__c":"a9CKZ000000sXyD2AU","UpdateLog__c":"Out of an abundance of caution, an update was posted at 11:05 am PDT on June 11, 2025. However following additional investigation, it was determined that a broad service degradation / disruption notice was not applicable. Okta will continue to monitor closely and directly engage with any customers as needed.”","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5HC2AY"},"Id":"a1PKZ000000g5HC2AY","CreatedDate":"2025-06-18T22:34:40.000+0000","IncidentId__c":"a9CKZ000000oLp22AE","UpdateLog__c":"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.\r\n\r\nDetection and Impact: \r\n\r\nOn June 11th at 11:04 AM PT, Okta internal monitoring alerted on-call responders regarding a database issue across US Cells 4, 6, 7, 11, and 14.\r\n\r\nA subset of replica databases in the affected cells were deadlocking, resulting in slow query responses or timeouts.\r\n\r\nDuring this time, users and admins may have experienced request slowness and timeout errors. Auth rates and other user access was not impacted during this period. \r\n\r\n\r\nRoot Cause Summary:\r\n\r\nOkta had progressively rolled out a configuration change earlier in the day as part of normal scheduled operations. This change exposed an error case which was then observed only in specific environments. \r\n\r\nOkta determined that MySQL contained a bug which, when a new specific monitoring query was executed, resulted in deadlocking the replica database servers and blocking additional queries from being executed. \r\n \r\n\r\nRemediation Steps:\r\n\r\nUpon investigation, at 11:11 AM PT Okta identified the root cause of the issue and began to execute database recovery efforts, thus restoring functionality and availability to normal operating levels. \r\n\r\nImpact Durations: \r\n\r\nUS Cell 4 - 11:06 AM - 11:11 AM PT ~5 minutes \r\n\r\nUS Cell 6 - 11:04 AM - 11:06 AM PT ~2 minutes \r\n\r\nUS Cell 7 - 11:09 AM - 11:15 AM PT ~6 minutes \r\n\r\nUS Cell 11 - 11:09 AM - 11:14 AM PT ~5 minutes \r\n\r\nUS Cell 14 - 11:09 AM - 11:16 AM PT ~7 minutes \r\n\r\nUsers may have continued to experience intermittent errors and delays in search results in cells while all database replicas were recovered. By 12:07 PM PT all databases had returned to normal operations. \r\n\r\nPreventative Actions:\r\n\r\nIn order to prevent similar incidents from happening again, Okta is currently reviewing the following: \r\n\r\nReview sequencing of database configuration updates deployed across environments \r\n\r\nThese learnings work to prevent similar incidents from happening again.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5HH2AY"},"Id":"a1PKZ000000g5HH2AY","CreatedDate":"2025-06-18T22:40:09.000+0000","IncidentId__c":"a9CKZ000000oLp72AE","UpdateLog__c":"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.\n\nDetection and Impact: \n\nOn June 11th at 6:07 PM PT, Okta internal monitoring alerted responders regarding a database issue across cells US Cell 6 and APAC Cell 1.\n\nPrimary databases were deadlocking, resulting in the cell switching to [read only] (https://support.okta.com/help/s/article/What-is-Oktas-Readonly-Mode?language=en_US) mode. During this time, users in Cells US Cell 6 and APAC Cell 1 would have encountered read only mode during this period. \n\n \n\nRoot Cause Summary:\n\nOkta had progressively rolled out a configuration change earlier in the day as part of normal scheduled operations. This change exposed an error case which was then observed only in specific environments. \n\nOkta determined that MySQL contained a bug which, when a new specific monitoring query was executed, resulted in deadlocking the replica database servers and blocking additional queries from being executed. Okta managed the issue by executing database recovery efforts, thus restoring functionality and availability to normal operating levels. \n\nCleanup procedures for this issue, which entailed rollback of the previously executed configuration change, were executed later in the day in a staggered fashion. During this process, the database primaries for US Cell 6 and APAC Cell 1 unexpectedly experienced a similar deadlock issue. \n\n \n\nRemediation Steps:\n\nDuring this period US Cell 6 and APAC Cell 1 switched into Read Only mode. Okta engineers executed database failover and recovery operations to return the cell to normal operation. \n\nImpact Durations: \n\nUS Cell 6 - 6:06 PM PT - 6:18 PM - 12 minutes \n\nAPAC Cell 1 - 6:06 PM PT - 6:24 PM - 18 minutes \n\nAt 6:24 PM PT all servers had recovered and had returned to normal operations. \n\n \n\nPreventative Actions:\n\nIn order to prevent similar incidents from happening again, Okta is currently reviewing the following: \n\nReview of database rollback process utilized between replicas and primaries\n\nReview sequencing of database configuration updates deployed across environments. \n\nThese learnings work to prevent similar incidents from happening again.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5Nn2AI"},"Id":"a1PKZ000000g5Nn2AI","CreatedDate":"2025-08-18T15:52:41.000+0000","IncidentId__c":"a9CKZ000000sXz12AE","UpdateLog__c":"Okta Engineering is continuing to investigate service disruptions. During this time, users using certain ISP providers may experience connection timeouts when attempting to reach Okta domains. Customers can try connecting via a mobile hotspot or an alternative network provider, which may allow those users to reach Okta domains. We will provide another update in approximately 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5Ns2AI"},"Id":"a1PKZ000000g5Ns2AI","CreatedDate":"2025-08-18T16:32:08.000+0000","IncidentId__c":"a9CKZ000000sXz12AE","UpdateLog__c":"Okta Engineering is continuing to investigate service disruptions. During this time, users using certain ISP providers may experience connection timeouts when attempting to reach Okta domains. Customers can try connecting via a mobile hotspot or an alternative network provider, which may allow those users to reach Okta domains. We will provide another update in approximately 60 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5O32AI"},"Id":"a1PKZ000000g5O32AI","CreatedDate":"2025-08-18T17:33:34.000+0000","IncidentId__c":"a9CKZ000000sXz12AE","UpdateLog__c":"Our investigation has confirmed that the Okta platform is operating as expected. We are continuing to monitor an external issue where users on certain ISPs may experience connection timeouts when accessing some Okta domains.\r\n\r\nAffected users can try connecting via a mobile hotspot or an alternative network provider as a potential workaround. We are actively engaged with our external partners to help facilitate a resolution.\r\n\r\nWe will provide another update in approximately 60 minutes, or sooner if new information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000g5OP2AY"},"Id":"a1PKZ000000g5OP2AY","CreatedDate":"2025-08-18T18:33:00.000+0000","IncidentId__c":"a9CKZ000000sXz12AE","UpdateLog__c":"The ISP connectivity issue affecting some customers is confirmed to be resolved. Additional root cause information will be available within 5 business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000gGlD2AU"},"Id":"a1PKZ000000gGlD2AU","CreatedDate":"2025-08-25T20:37:40.000+0000","IncidentId__c":"a9CKZ000000sXz12AE","UpdateLog__c":"The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted users using Okta services.\r\n\r\n\r\nTiming:\r\n\r\nIncident start: August 18, 2025, at 4:06 AM PDT\r\n\r\nIncident resolved: August 18, 2025, at 11:29 AM PDT\r\n\r\n\r\nDetection:\r\n\r\nCustomers began reporting that their organization's page was unreachable for certain users.\r\n\r\n\r\nImpact:\r\n\r\nA subset of customers experienced an \"ERR_CONNECTION_TIMED_OUT\" error when attempting to access their Okta organizations, which prevented them from logging in.\r\n\r\n\r\nRoot Cause:\r\n\r\nA third-party Internet Service Provider experienced an issue that impaired network traffic from their infrastructure to certain other services, including those provided by Okta. This disruption primarily impacted connectivity for Google Fiber customers in the Texas region, though other providers and locations may have also been affected. The third-party provider later resolved this issue.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000srLJ2AY"},"Id":"a1PKZ000000srLJ2AY","CreatedDate":"2025-04-24T00:31:13.000+0000","IncidentId__c":"a9CKZ000000oLkp2AE","UpdateLog__c":"We have received confirmation that the errors have subsided. We will continue to monitor the situation until it's fully resolved.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000srLO2AY"},"Id":"a1PKZ000000srLO2AY","CreatedDate":"2025-04-24T04:30:35.000+0000","IncidentId__c":"a9CKZ000000oLkp2AE","UpdateLog__c":"The issue affecting our email delivery has been resolved. Additional root cause information will be available within 10 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000t3cq2AA"},"Id":"a1PKZ000000t3cq2AA","CreatedDate":"2025-06-11T19:15:07.000+0000","IncidentId__c":"a9CKZ000000oLp22AE","UpdateLog__c":"Services have been restored. We will continue to monitor the situation and we will provide another update within the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000t3cv2AA"},"Id":"a1PKZ000000t3cv2AA","CreatedDate":"2025-06-11T19:30:23.000+0000","IncidentId__c":"a9CKZ000000oLp22AE","UpdateLog__c":"The issue impacting multiple cells has been resolved. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000t9Mi2AI"},"Id":"a1PKZ000000t9Mi2AI","CreatedDate":"2025-06-25T20:07:32.000+0000","IncidentId__c":"a9CKZ000000sXyI2AU","UpdateLog__c":"The 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.\n\nTiming:\n\n\nIncident start: June 12, 2025, 10:50 AM PT\n\nIncident resolved: June 12, 2025, 12:15 PM PT\n\n\nDetection:\n\nOkta Engineering noticed errors related to this feature on June 12, 2025.\n\n\nImpact:\n\nDuring this outage, Android users attempting to authenticate via Push would not receive a push notification on their device and would be required to open Okta Verify to complete authentication.\n\n\nSummary:\n\nGoogle Cloud Services confirmed disruptions to their services (including those necessary for the delivery of Android push notifications) that were resolved on June 12, 2025, at 13:49 PT. More details, as provided by Google, can be found here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCdm2AE"},"Id":"a1PKZ000000tCdm2AE","CreatedDate":"2025-07-30T00:03:36.000+0000","IncidentId__c":"a9CKZ0000011DwJ2AU","UpdateLog__c":"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.\r\n\r\nDetection and Impact: \r\n\r\nOn July 22nd, Okta triggered incident processes investigating issues affecting automatic user activation from API and Directory Imports across all production cells. Users were erroneously left in a pending state despite the update appearing as completed. \r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nOkta Engineering determined that the root cause of the issue originated from an update deployed on 7:56 PM (PT) July 9th, which, due to a behavior change that mishandled user states, could result in some newly provisioned users being left in a pending state. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nOnce the source of the issue was identified, Okta engineering rolled back changes at 12:11 PM (PT) on July 22nd. These actions successfully addressed the issue and restored normal operations by 1:29 PM (PT). \r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nTo prevent future incidents, Okta is adding additional test cases and improving processes to better the resiliency of user auto provisioning processes. In addition, we are reviewing our internal processes to assimilate issues and expedite escalations to improve our time to resolve these types of issues.\r\n\r\nTotal Duration:\r\n\r\nTotal Duration (Minutes): 12 days 17 hrs 32min\r\n\r\nActual Time: 7/9/2025 7:56:04PM - 7/22/2025 1:29:03PM\r\n\r\nDuration (# of minutes):\r\n\r\nTotal Duration (Minutes): 17,280 mins","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmH2AU"},"Id":"a1PKZ000000tCmH2AU","CreatedDate":"2025-08-01T18:01:08.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team is still monitoring the fix applied to address the incident impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. Mitigation is progressing, and customers should be seeing fewer delays or timeouts. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmM2AU"},"Id":"a1PKZ000000tCmM2AU","CreatedDate":"2025-08-01T18:57:22.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team continues to monitor the fix applied to address the incident impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. Workflow services should be processing normally at this time. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmN2AU"},"Id":"a1PKZ000000tCmN2AU","CreatedDate":"2025-08-01T20:09:13.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team continues to observe steady recovery in the Workflow services that impacted US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. We'll provide an update in 60 minutes, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmR2AU"},"Id":"a1PKZ000000tCmR2AU","CreatedDate":"2025-08-01T21:21:19.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The team is continuing to monitor the fix implemented to resolve the recent Workflows incident. While we're seeing clear indications of recovery, we're proceeding with an abundance of caution to ensure full stability. Customer workflows should be seeing improvements, and we're working diligently to ensure everything flows smoothly. We'll share our next update in 120 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmW2AU"},"Id":"a1PKZ000000tCmW2AU","CreatedDate":"2025-08-01T23:22:38.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The initial impact has fully recovered on OK14, and we're transitioning from active response to a dedicated monitoring phase on the other cells. Our engineers are continuously tracking system performance to ensure full stability. While we expect services to remain stable, if you experience any Workflow-related errors, please contact our support team for assistance.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCmb2AE"},"Id":"a1PKZ000000tCmb2AE","CreatedDate":"2025-08-02T03:46:43.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflow issues for US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, APJ Cell 1, US Cell 11, and US Cell 14 have been addressed. Our monitoring shows a return to normal conditions. Our team is collaborating with our third-party vendor to identify the underlying root cause, and a Root Cause Analysis will be forthcoming.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tCv32AE"},"Id":"a1PKZ000000tCv32AE","CreatedDate":"2025-08-11T20:13:04.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"We sincerely apologize for any impact this incident has caused you, your business, and your customers. At Okta, trust and transparency are our top priorities. The facts regarding this incident are outlined below. We are committed to implementing improvements to the service to prevent future occurrences of this incident.\n\nDetection and Impact:\n \nOn Friday, August 1st, at 4:13 AM PT, Okta was alerted to an issue in which message brokers were quickly exhausting disk space and causing delayed workflow processing in Cells OK1, OK2, OK3, OK4, OK6, OK7, OK11, and OK14. \nStarting at approximately 5:00 AM PT, users may have experienced processing delays, API timeouts, or Workflow executions ending prematurely with internal server errors. Delayed Workflow executions that were rerouted to healthy infrastructure were processed successfully.\n\nRoot Cause Summary:\n\nBased on our investigation and findings, the root cause of this issue was a disk space leak caused by a duplicate session within services managed by a third-party operator introduced during a maintenance window. \n \nRemediation Steps:\n\nImmediately upon receiving alerts of service disruptions, Okta Engineering escalated the issues with our provider and worked to implement internal mitigations. While troubleshooting the issue, Okta brought up multiple additional message brokers and swapped them as needed to balance the various waves of requests. \nOkta's internal mitigations restored service to the affected cells by approximately 12:34 PM PT, with additional stabilization work continuing through the afternoon. Okta continued to work directly with our provider to mitigate the issue and confirmed complete service restoration throughout the weekend.\n \nPreventative Actions:\n\nOkta will continue working with our third-party service provider to enhance monitoring and communication, expedite detection, and improve processes for making infrastructure changes. Additionally, we are updating our operational procedures for scaling clusters and connections to improve service recovery times further.\n\nDuration (# of minutes): 454","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tIzs2AE"},"Id":"a1PKZ000000tIzs2AE","CreatedDate":"2025-08-20T23:29:00.000+0000","IncidentId__c":"a9CKZ0000011DxR2AU","UpdateLog__c":"The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted the Okta service.\r\n\r\nTiming:\r\n\r\nIncident start: August 7, at 06:02 PM PDT\r\n\r\nIncident resolved: August 8, at 02:00PM PT\r\n\r\nDetection:\r\n\r\nOkta Engineering was alerted to backend jobs queues increasing due to a slow third-party provider API response. \r\n\r\nImpact:\r\n\r\nCustomers may have seen slow job processing in Okta.\r\n\r\nSummary:\r\n\r\nJobs were queued due to job execution times increase while waiting for third-party provider API responses. Our third-Party provider has identified a configuration error and resolved this issue by provisioning additional resources to these APIs.\r\n\r\nPreventive Actions:\r\n\r\nOkta has introduced additional logging to identify similar disruptions closer to their start.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tWza2AE"},"Id":"a1PKZ000000tWza2AE","CreatedDate":"2025-09-22T13:59:22.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"Okta Engineering is actively working to identify the root cause of a Google Sheet connector issue that may cause customers to experience 404 errors when using certain workflow cards. As additional information becomes available, we will provide another update in approximately 60 minutes or sooner.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tWzf2AE"},"Id":"a1PKZ000000tWzf2AE","CreatedDate":"2025-09-22T14:58:55.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"The Workflows Automation and Extensibility team is continuing to work on the issue, and multiple mitigation efforts are underway. We will provide updates in the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tWzk2AE"},"Id":"a1PKZ000000tWzk2AE","CreatedDate":"2025-09-22T16:09:59.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"Our teams are working with our third-party provider to address the underlying issue. We have no estimated time for a full resolution, but we are committed to providing timely updates within the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX1H2AU"},"Id":"a1PKZ000000tX1H2AU","CreatedDate":"2025-09-22T17:08:09.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"We are working closely with our third-party provider to address the ongoing issue of our Google Sheets connector cards returning 404 errors when used with Apps Script. We are jointly developing a clear path to resolution and actively monitoring the progress. An update will be provided within the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX2t2AE"},"Id":"a1PKZ000000tX2t2AE","CreatedDate":"2025-09-22T18:04:15.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"We are fully engaged with our third-party provider as this service degradation continues due to an external dependency. You may continue to experience 404 errors until the root cause is addressed. We appreciate your patience and will share more on our progress in 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX3I2AU"},"Id":"a1PKZ000000tX3I2AU","CreatedDate":"2025-09-22T19:08:59.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"The service degradation affecting Google Sheets is still ongoing. The issue requires close collaboration with our third-party provider to ensure any changes we make do not interfere with their work and impact other services. We will provide our next update in 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX672AE"},"Id":"a1PKZ000000tX672AE","CreatedDate":"2025-09-22T20:29:16.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"A fix for the Google Sheets connection has been tested and confirmed. It resolves the previous 404 runtime errors without requiring customers to re-authenticate. The next steps include test deployment to verify its compatibility with existing connections. We will share another update within 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX6C2AU"},"Id":"a1PKZ000000tX6C2AU","CreatedDate":"2025-09-22T21:24:57.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"Our engineering team is continuing to test and monitor the fix in the Preview environment. Once we have confirmed its stability, we will fully deploy it to our production environment. We will share our next update in 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX6H2AU"},"Id":"a1PKZ000000tX6H2AU","CreatedDate":"2025-09-22T22:00:28.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"Our Engineering team has successfully deployed a fix to all impacted environments and is now actively monitoring its performance. We appreciate your continued patience and will provide a final update in 30 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tX6M2AU"},"Id":"a1PKZ000000tX6M2AU","CreatedDate":"2025-09-22T22:28:08.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"The issue that affected Google Sheets has been resolved, and services have been restored. Additional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tXhf2AE"},"Id":"a1PKZ000000tXhf2AE","CreatedDate":"2025-10-07T00:06:43.000+0000","IncidentId__c":"a9CKZ000000oLxh2AE","UpdateLog__c":"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 incident.\n\nDetection and Impact: \nOn September 22nd at 2:12 am PST, Okta was alerted to an issue where some customers executing flows with Google Sheets connectors saw 404 error messages. \n\nRoot Cause Summary:\nA change made by the third-party provider resulted in a 404 error message on the Google Sheets workflows connector.\n\nRemediation Steps:\nOkta began diagnosing the issue and engaging with the third party support team immediately upon receiving reports of the error. Following the investigation, the Okta team implemented a fix which resulted in the restoration of Google sheets connector functionality. \n \nPreventative Actions:\nOkta is reviewing and enhancing monitoring and alerting processes to minimize impacts to customers for similar issues in the future.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tXhk2AE"},"Id":"a1PKZ000000tXhk2AE","CreatedDate":"2025-10-09T22:54:09.000+0000","IncidentId__c":"a9CKZ000000oM1u2AE","UpdateLog__c":"We appreciate your patience while we addressed this issue. The service has shown stability since October 7th, and following an extended period of monitoring, we can now confirm that the issue is fully resolved. We are working with our provider on a thorough Root Cause Analysis (RCA), which we will post here.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tXhp2AE"},"Id":"a1PKZ000000tXhp2AE","CreatedDate":"2025-10-10T00:31:20.000+0000","IncidentId__c":"a9CKZ000000oM2J2AU","UpdateLog__c":"After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved and has not recurred. Additional root cause information will be available within five business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000taiE2AQ"},"Id":"a1PKZ000000taiE2AQ","CreatedDate":"2025-10-15T19:14:03.000+0000","IncidentId__c":"a9CKZ000000oMAj2AM","UpdateLog__c":"While our third-party provider is actively addressing the issue on their side, you may continue to experience intermittent errors and service unavailability. We are monitoring the situation closely and will send out another update immediately once we receive concrete steps or a timeline for the fix from our third-party provider.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamR2AQ"},"Id":"a1PKZ000000tamR2AQ","CreatedDate":"2025-10-15T23:08:27.000+0000","IncidentId__c":"a9CKZ000000oMAj2AM","UpdateLog__c":"Our third-party provider has confirmed that this is a system-wide issue on their side and has initiated a top-priority escalation to ensure a swift action plan and fix are developed to restore full functionality. We are actively working with our provider and will send a prompt update as soon as we receive more information.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamW2AQ"},"Id":"a1PKZ000000tamW2AQ","CreatedDate":"2025-10-16T00:51:12.000+0000","IncidentId__c":"a9CKZ000000oMAj2AM","UpdateLog__c":"Our third-party provider, Microsoft, has successfully deployed a critical hotfix resolving authentication issues with Okta Fast Pass on Windows 11, and service stability has been confirmed on our end. To fully implement the resolution, impacted customers are required to perform a system restart. While service is restored, we are now engaged in continuous, high-priority communication with the third-party provider to implement and validate a permanent, long-term solution. We will continue to closely monitor the situation and will post any additional information, including any future required user actions, as soon as it becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamb2AA"},"Id":"a1PKZ000000tamb2AA","CreatedDate":"2025-10-16T19:18:55.000+0000","IncidentId__c":"a9CKZ000000oMAj2AM","UpdateLog__c":"We sincerely apologize for the disruption this incident has caused. Our teams have validated that Microsoft's fix, along with rebooting your machine, will successfully resolve the issue and restore full functionality for impacted users. We will share the complete root cause analysis once it is available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamg2AA"},"Id":"a1PKZ000000tamg2AA","CreatedDate":"2025-10-17T21:49:37.000+0000","IncidentId__c":"a9CKZ000000oM2J2AU","UpdateLog__c":"We sincerely apologize for any impact this incident has caused 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 improving the service to prevent future occurrences of this incident.\n\nDetection and Impact: \nOn October 9th at 4:15 PM PT, Okta observability and metric systems alerted on-call teams regarding issues accessing resources in US Cell 14. Customers in this cell may have experienced errors connecting to Okta services. Customers using custom domains would experience intermittent errors and timeouts attempting to access Okta services during this time as well.\n\nRoot Cause Summary:\nThe root cause of this incident was a substantial increase in network activity that impacted the service's points, preventing customer requests from reaching the Okta service and resulting in a temporary service disruption.\n\nRemediation Steps:\nUpon investigation, the nature of the traffic increase was quickly identified, and mitigations to isolate the excess requests were deployed by our service provider. The team confirmed that US Cell 14 fully returned to normal operation by 4:24 PM PT.\n\nPreventative Actions:\nIn a coordinated effort, our service provider has implemented new mitigations on its edge. In parallel, Okta has proactively applied scaling operations to both our network and infrastructure service capacity while continuously improving our observability. We're dedicated to preventing future incidents by continuously improving our response by applying additional protections and expediting our overall response time.\n\nDuration (# of minutes): 09 minutes Actual Time: 04:15 PM - 04:24 PM PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000taml2AA"},"Id":"a1PKZ000000taml2AA","CreatedDate":"2025-10-20T08:44:13.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We're currently experiencing service degradation throughout Workflows across all cells. Due to an issue with an upstream provider, Cells OK1 to OK4 and OP1 are currently impacted. We're working with the vendor and will provide updates in the next 30 minutes.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamq2AA"},"Id":"a1PKZ000000tamq2AA","CreatedDate":"2025-10-20T09:22:10.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"Okta engineers have made service changes to Workflows to mitigate the issues. Flow executions continue to improve. There are other issues that we are still investigating and will attempt to mitigate further for OK1 to OK4 and OP1. We're working with the vendor and will provide updates in the next 30 minutes","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamr2AA"},"Id":"a1PKZ000000tamr2AA","CreatedDate":"2025-10-20T10:44:07.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. \r\nWorkflows processing has been restored across all Cells. Customers should review their flow executions during the outage as they may have to rerun flows that failed during that time. We will provide updates in the next 60 minutes.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tamv2AA"},"Id":"a1PKZ000000tamv2AA","CreatedDate":"2025-10-20T09:42:25.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. \r\nWorkflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tan02AA"},"Id":"a1PKZ000000tan02AA","CreatedDate":"2025-10-20T10:13:40.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are seeing significant improvements in our services in Cells OK1 to OK4 and OP1. \r\nWorkflows is also showing significant improvement across all Cells. We will provide updates in the next 30 minutes","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tan52AA"},"Id":"a1PKZ000000tan52AA","CreatedDate":"2025-10-20T11:51:00.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are still seeing significant improvements in our services in Cells OK1 through to OK4 and OP1. \r\nCustomers may still experience issues with viewing Syslog events in OK1. We will provide updates in the next 60 minutes.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanA2AQ"},"Id":"a1PKZ000000tanA2AQ","CreatedDate":"2025-10-20T12:48:12.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are continuing to monitor improvements in our services in Cells OK1 through to OK4 and OP1. \r\nCustomers may still experience issues with viewing Syslog events in OK1. We will provide an update at approximately 9:30 AM PDT.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanF2AQ"},"Id":"a1PKZ000000tanF2AQ","CreatedDate":"2025-10-20T16:41:33.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are maintaining our focused monitoring effort on Cells OK1 through to OK4 and OP1. Workflows services have recovered in all US Cells and we recommend reviewing existing workflows for consistency around third-party interactions. \nWe are aware that the experience for viewing Syslog events in OK1 has not yet resolved and we are continuing to remediate these issues. We will provide updates in the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanK2AQ"},"Id":"a1PKZ000000tanK2AQ","CreatedDate":"2025-10-20T18:14:32.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are actively working on persisting issues with Syslog delays in OK1. We will provide our next status updates in 120 minutes or earlier as soon as information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanP2AQ"},"Id":"a1PKZ000000tanP2AQ","CreatedDate":"2025-10-20T19:00:21.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"We are seeing sustained recovery and improved processing speeds in Cell OK1 on Syslog events. which is helping to work through the existing backlog. We’re continuing to monitor the situation closely to ensure this improvement is sustained. We will provide next update in 180 minutes, or sooner if the backlog is fully processed.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanU2AQ"},"Id":"a1PKZ000000tanU2AQ","CreatedDate":"2025-10-20T21:09:22.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"Stability in Cell OK1 continues to show consistent improvement. We are still processing the remaining system logs and will provide our next update in 120 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanZ2AQ"},"Id":"a1PKZ000000tanZ2AQ","CreatedDate":"2025-10-20T23:17:31.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"Okta continues to mitigate and resolve event processing delays in OK1. We have deployed additional resources to improve processing of events to reduce these delays. We are observing improved processing times and will continue to monitor and will update in 120 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tane2AA"},"Id":"a1PKZ000000tane2AA","CreatedDate":"2025-10-21T01:00:07.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"Following the deployment of additional capacity and resources, we've seen steady acceleration in processing rates. We will continue to track this progress and provide another update in the next 120 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tanj2AA"},"Id":"a1PKZ000000tanj2AA","CreatedDate":"2025-10-21T02:19:46.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"The issue impacting Syslog processing delays in OK1 and the previous Workflow issues have been resolved and the services have been restored. Additional root cause information will be available within 5 business days.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tb042AA"},"Id":"a1PKZ000000tb042AA","CreatedDate":"2025-10-23T02:52:10.000+0000","IncidentId__c":"a9CKZ000000oM1z2AE","UpdateLog__c":"Incident start: September 15, 2025\nIncident resolved: September 25, 2025\n\nDetection:\nOkta was alerted to the issue after customers reported that groups managed by Google Workspace were being unexpectedly removed from Okta during the import process.\n\nImpact:\nCustomers utilizing the Google Workspace integration may have experienced the following during this period:\nDuring scheduled or manual imports, groups (which still existed in Google Workspace) were unexpectedly removed from Okta.\nThe unintended removal of groups may have resulted in a loss of application access for users who were members of the affected groups.\n\nRoot Cause:\nThe root cause was an issue within the Google Workspace Directory API, which Okta services rely on for group imports. The API intermittently returned incomplete lists of groups without correctly indicating that the data was partial. This led Okta services to interpret the incomplete data as the complete list of groups. As a result, any groups not included in the incomplete API response were processed as if they had been intentionally deleted in Google Workspace, leading to their removal within Okta as part of the import. Google acknowledged this API issue and deployed a resolution on or around September 25, 2025.\n\nRemediation Steps:\nOkta advised customers to pause all Google group imports until the third-party provider resolved the underlying issue.\n\nPreventive Actions:\nOkta Engineering implemented a proactive measure to automatically halt Google group imports when a large number of deletions is detected. This safeguard was put in place to avoid processing incomplete data and further unintended group removals. Further, Okta teams worked with Google as they worked to identify and resolve the underlying API issue.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tb092AA"},"Id":"a1PKZ000000tb092AA","CreatedDate":"2025-10-23T02:55:44.000+0000","IncidentId__c":"a9CKZ000000oMAj2AM","UpdateLog__c":"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. \r\n\r\nTiming:\r\nImpact started approximately on October 14, 2025\r\nImpact resolved approximately on October 16, 2025, at 12:18 PM PDT\r\n\r\nDetection:\r\nCustomers began reporting authentication failures when using Okta FastPass on Windows devices after installing recent Microsoft security patches.\r\n\r\nImpact:\r\nEnd users on Windows 11 devices who had recently installed a Microsoft security update (KB5066835) were unable to complete their login when using Okta FastPass with phishing resistance enabled.\r\n\r\nRoot Cause:\r\nMicrosoft released a security update for Windows 11 that unexpectedly interfered with a local communication method on end-user devices. Okta Verify requires this communication method to perform its FastPass phishing-resistant authentication. This conflict prevented Okta services from validating the authentication attempt, resulting in login failures for affected end users.\r\n\r\nRemediation Steps:\r\nOn October 15, 2025, at 4:48 PM PDT, Microsoft resolved the issue and confirmed that end-users would need to reboot their computers to fully apply the fix.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tb0E2AQ"},"Id":"a1PKZ000000tb0E2AQ","CreatedDate":"2025-10-27T23:00:27.000+0000","IncidentId__c":"a9CKZ000000oM1u2AE","UpdateLog__c":"Timing:\nIncident start: September 22, 2025, at 2:25 PM PDT\nIncident resolved: October 3, 2025, at 5:00 PM PDT\n\nDetection:\nOn September 22, 2025, Okta customers began reporting intermittent errors with specific Google Sheets connector functions in Okta Workflows.\n\nImpact:\nOkta customers utilizing Okta Workflows could experience runtime errors for several Google Sheets connector cards, including Read Row, Read All Rows, Clear Row, and New Row. These actions failed intermittently, returning errors such as:\n- 500 - Invalid Input: Invalid input for 'list'. Expected a list.\n- ScriptError 400\n- Invalid input for \"keys\".\n\nRoot Cause:\nThe intermittent failures stemmed from a remediation step taken for a separate, preceding disruption (I-9545) involving the Google Sheets connector. Following that incident, Okta teams implemented a configuration change to the connector based on feedback from Google. While this change resolved the initial issue, it inadvertently introduced a new, intermittent condition. This change caused some customer requests to be incorrectly routed to a stale, cached version of the connector’s implementation within Google infrastructure. This cached version of the implementation did not contain more recent updates, which led to the intermittent failures experienced by customers.\n\nRemediation Steps:\nOkta Engineering worked with Google to investigate the new behavior. Once the root cause was identified, Okta Engineering developed and tested an updated configuration for the Google Sheets connector.\nThis fix was then deployed progressively across all preview and production environments, with service stability and error-rate monitoring confirmed at each stage. This culminated in a complete resolution of preview and commercial environments on October 3, 2025.\n\nPreventive Actions:\nOkta has updated its internal operational procedures for this connector to prevent recurrence. Runbooks have been revised to include this scenario and prioritize alternative recovery steps to ensure greater service resilience.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tb0J2AQ"},"Id":"a1PKZ000000tb0J2AQ","CreatedDate":"2025-10-29T00:10:04.000+0000","IncidentId__c":"a9CKZ000000oMAo2AM","UpdateLog__c":"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. \n\nDetection and Impact: \n\nOkta’s cloud service provider reported errors starting at 11:48 PM PT per their post-incident assessment. Below is the Okta timeline for the impact on our services. \n \nOkta Workflows: \nOn October 19th at 11:55 PM PT Okta began receiving alerts regarding Workflows issues occurring in US FL1. \nDuring the incident, customers in this cell experienced errors accessing the Workflows UI. Most workflows continued executing normally during this incident, except for those that contained Workflows Table cards, which included create, update, import, or export functionality. Due to latency issues, organizations invoking API endpoint flows encountered timeouts waiting for flows to complete. \nActual Impact Time: Sunday 11:55 PM PT - Monday 2:02 AM PT\n\nOkta Syslog Event Processing/Log Streaming Delays:\nOn October 20th at 12:23 AM PT, Okta began receiving alerts that systems related to our system log processing were experiencing delays and errors. Okta immediately began to investigate the issue. \nDuring the incident, customers in OK1, OK2, OK3, and OK4 experienced delays in event logs and reports. Additionally, the incident impacted Stream and Webhook events, resulting in increased event processing times.\nOK2, OK3, OK4 Actual Impact Time: Sunday 11:48 PM PT - Monday 3:36 AM PT \nOK1 Actual Impact Time: Sunday 11:48 PM PT - Monday 6:46 PM PT \n\nOkta SMS MFA Processing errors: \nSome customers may have also seen SMS delivery and retry failures due to errors in downstream third-party telephony providers. \nUsers were able to access the UI and Admins, and were able to log in. Actual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT\nActual Impact Time: Sunday 11:48 PM PT - Monday 3:21 AM PT\n\n\nRoot Cause Summary:\n\nOkta’s cloud service provider experienced system issues that impacted the Okta service. \n\nRemediation Steps:\n\nOkta Workflows: After reviewing internal alerting and investigating the issue, at 2:02 AM PT, Okta took mitigating actions to bypass the impacted cloud provider services, and Workflows began stabilizing. Okta continued to monitor until approximately 11:49 AM PT by which time functionality had normalized. \n\nOkta Syslog Event Processing/Log Streaming Delays: \nFollowing a review of internal alerts, Okta began to analyze and address impacted services. \nAt 2:12 AM PT, OK2, OK3, and OK4 were restored to full operation, and Okta Engineering verified the appropriate resolution of the incident. Events began processing and fully recovered in these environments at 3:36 AM PT.\nWhile all other cells had recovered, OK1 continued to experience longer system event processing delays. Once the cloud service system was stabilized, Okta was able to scale up the processing. All system log events for OK1 events were processed by 6:46 PM PT.\n\n\nPreventative Actions:\n\nOkta is working closely with the cloud service provider to investigate additional mitigations and improve response to these types of incidents. \nIn addition, Okta is looking for opportunities to improve processes to identify and mitigate issues related to cloud service provider issues faster and more efficiently.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tdsD2AQ"},"Id":"a1PKZ000000tdsD2AQ","CreatedDate":"2025-10-29T19:16:58.000+0000","IncidentId__c":"a9CKZ000000oMJ92AM","UpdateLog__c":"We have confirmed that a third-party provider issue is causing intermittent timeouts when authenticating to the Microsoft O365 portal via Okta Verify. This is impacting a subset of customers. Our provider is actively addressing the issue, and we are closely monitoring their progress on the fix. We will provide the next update in 30 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tdsI2AQ"},"Id":"a1PKZ000000tdsI2AQ","CreatedDate":"2025-10-29T19:54:44.000+0000","IncidentId__c":"a9CKZ000000oMJ92AM","UpdateLog__c":"We appreciate your continued patience as we work through this service degradation. \nOur provider has successfully deployed a fix, and our team is now actively monitoring the environment and performance to confirm full stability. We understand the impact this has on your work, and we are committed to keeping you informed. We will provide our next scheduled status update in 120 minutes, or sooner if we achieve a significant update or confirm a complete fix.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tdsN2AQ"},"Id":"a1PKZ000000tdsN2AQ","CreatedDate":"2025-10-29T23:22:14.000+0000","IncidentId__c":"a9CKZ000000oMJ92AM","UpdateLog__c":"Remediation work by our third-party provider is ongoing, and Okta is observing consistent recovery across affected cells. Our next scheduled update is within 90 minutes or earlier if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tdsS2AQ"},"Id":"a1PKZ000000tdsS2AQ","CreatedDate":"2025-10-30T01:47:16.000+0000","IncidentId__c":"a9CKZ000000oMJ92AM","UpdateLog__c":"After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved by our third-party provider. Additional root cause information will be available within five business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000te2p2AA"},"Id":"a1PKZ000000te2p2AA","CreatedDate":"2025-10-31T00:54:27.000+0000","IncidentId__c":"a9CKZ000000oM2E2AU","UpdateLog__c":"Timing:\nIncident start: September 24, 2025, at 09:00AM PDT\nIncident resolved: September 24, 2025, at 4:30 PM PDT\n\nDetection:\nOn September 24, 2025, Okta monitoring detected a spike in latency impacting the Google Dashboard. \n\nImpact:\nGoogle Workspace API latency issues led to Okta performance degradation in job processing, and all customers using the Google Workspace API may have experienced latency issues.\n\nRoot Cause:\nThe Google Workspace API experienced a latency spike, causing delays in Okta job processing. Okta's system terminated outbound requests that did not receive a response within five minutes. During the Google Workspace API latency spike, the maximum expected wait time exceeded ten minutes, leading to connection terminations before results were received. This increased delay caused Okta jobs to back up, impacting our customers. Additionally, Okta's automatic retry mechanism for socket timeouts further compounded these delays. Google acknowledged this API issue and deployed a resolution.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000thAD2AY"},"Id":"a1PKZ000000thAD2AY","CreatedDate":"2025-11-05T18:54:29.000+0000","IncidentId__c":"a9CKZ000000oMJ92AM","UpdateLog__c":"Timing:\nIncident start: October 29, 2025, at 7:15 AM PDT\nIncident resolved: October 29, 2025, at 4:05 PM PDT\n\nDetection:\nOkta monitoring detected errors when redirecting to Microsoft. Concurrently, customers began reporting intermittent timeouts when authenticating to Microsoft services and when using Okta Verify.\n\nImpact:\nA subset of customers experienced intermittent timeouts and SSO login failures when authenticating to Microsoft services (such as Microsoft 365). Further, customers may have seen timeouts in Azure webhooks and other redirects to Microsoft services.\n\nRoot Cause:\nMicrosoft Azure experienced connectivity issues with its Azure Front Door service across multiple regions. This resulted in latency, timeouts, and errors for client redirection, causing intermittent timeouts and authentication failures for Okta users attempting to authenticate to Microsoft services.\n\nMicrosoft provides additional details for this disruption under tracking ID: YKYN-BWZ: https://azure.status.microsoft/en-us/status/history/\n\nRemediation Steps:\nOkta monitored the disruption while Microsoft worked on a resolution. Okta monitoring showed error rates began to decrease at 11:35 AM PDT, and Microsoft confirmed that their services were fully restored at 4:05 PM PDT.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000thCx2AI"},"Id":"a1PKZ000000thCx2AI","CreatedDate":"2025-11-12T20:56:27.000+0000","IncidentId__c":"a9CKZ000000oMJE2A2","UpdateLog__c":"Our third-party vendor is making continuous progress on resolving the SMS delivery issues. Okta has also deployed additional safeguards on our platform to mitigate the impact. We will maintain active monitoring until we confirm the issue is fully resolved.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ000000tjwb2AA"},"Id":"a1PKZ000000tjwb2AA","CreatedDate":"2025-11-14T01:24:36.000+0000","IncidentId__c":"a9CKZ000000oMJE2A2","UpdateLog__c":"After monitoring for an extended period, we confirmed that the issue has not reoccurred. A root cause analysis (RCA) will be posted here within five business days. We sincerely apologize for the impact this had on you and your users.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015L2R2AU"},"Id":"a1PKZ0000015L2R2AU","CreatedDate":"2025-07-22T19:25:24.000+0000","IncidentId__c":"a9CKZ0000011DwJ2AU","UpdateLog__c":"Okta has reproduced the issue and is currently working on a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015L2W2AU"},"Id":"a1PKZ0000015L2W2AU","CreatedDate":"2025-07-22T19:54:41.000+0000","IncidentId__c":"a9CKZ0000011DwJ2AU","UpdateLog__c":"Okta has reproduced the auto-activation issue and is continuing to work toward a fix. We will provide another update in the next 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015L2b2AE"},"Id":"a1PKZ0000015L2b2AE","CreatedDate":"2025-07-22T20:37:27.000+0000","IncidentId__c":"a9CKZ0000011DwJ2AU","UpdateLog__c":"Okta has resolved the auto-activation issue and import functionality was fully restored at 1:37 PM PST. Additional root cause information will be available within 5 business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015LeC2AU"},"Id":"a1PKZ0000015LeC2AU","CreatedDate":"2025-08-01T15:49:14.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11. During this time, workflows may be delayed or timeout. The Workflows Automation and Extensibility team has applied some changes to mitigate the issue and is monitoring for improvements. We'll provide an update in 30 minutes, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015LeM2AU"},"Id":"a1PKZ0000015LeM2AU","CreatedDate":"2025-08-01T16:14:33.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11.\n\nDuring this time, real-time flows are delayed and may time out. Non-real-time flows are now running with normal latency. The Workflows Automation and Extensibility team is applying further mitigations to the issue and monitoring for improvements. We'll provide an update in 30 minutes, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PKZ0000015LeR2AU"},"Id":"a1PKZ0000015LeR2AU","CreatedDate":"2025-08-01T16:53:55.000+0000","IncidentId__c":"a9CKZ0000011Dws2AE","UpdateLog__c":"The Workflows Automation and Extensibility team is investigating and has determined that the incident is currently impacting Workflows in US Cell 1, US Cell 2, US Cell 3, US Cell 4, US Cell 6, US Cell 7, and US Cell 11.\r\nDuring this time, real-time flows are delayed and may time out. Non-real-time flows are now running with normal latency. The Workflows Automation and Extensibility team is continuing to apply further mitigations to the issue and monitoring for improvements. We'll provide an update in 1 hour, or sooner, as additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000002ymIL2AY"},"Id":"a1PWR000002ymIL2AY","CreatedDate":"2025-11-17T19:44:04.000+0000","IncidentId__c":"a9CWR00000011QI2AY","UpdateLog__c":"After monitoring for an extended period, we confirmed that the issue has not reoccurred. A root cause analysis (RCA) will be posted here within five business days. We sincerely apologize for the impact this had on you and your users.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000002zDwr2AE"},"Id":"a1PWR000002zDwr2AE","CreatedDate":"2025-11-19T22:17:33.000+0000","IncidentId__c":"a9CKZ000000oMJE2A2","UpdateLog__c":"Timing:\nIncident start: November 12, 2025, at 6:50 AM PST\nIncident resolved: November 12, 2025, at 12:50 PM PST\n\n\nDetection:\nOkta monitoring detected a significant decline in SMS deliverability rates, coinciding with customer reports of users not receiving SMS-based one-time passcodes (OTPs). Our third-party vendor subsequently updated their status page, confirming delivery delays to multiple networks in the United States.\n\n\nImpact:\nA subset of Okta customers experienced failures when attempting to receive SMS OTPs on their first attempt during the incident window. Although the initial delivery would fail, Okta offers the option to retry sending the SMS OTP, which is handled by a secondary provider. To leverage this secondary provider, end users were required to manually click the “Resend” button after the initial send failure. Users who performed this action were able to successfully receive their OTPs and authenticate.\n\n\nRoot Cause:\nOkta’s primary third-party telephony provider experienced a service outage within their United States SMS delivery infrastructure. This outage caused deliverability rates for SMS messages routed through this provider to drop below acceptable thresholds.\n\n\nRemediation Steps:\nOkta Engineering updated the telephony configuration to swap our primary provider with our secondary provider for messages sent to US numbers. This change, completed at 12:50 PM PST, routed all new SMS traffic away from the impacted provider, restoring deliverability for first-attempt SMS requests. This configuration remained in place until the third-party vendor confirmed the resolution of their infrastructure issues and testing confirmed that deliverability rates were restored.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000030hZV2AY"},"Id":"a1PWR0000030hZV2AY","CreatedDate":"2025-11-25T00:21:36.000+0000","IncidentId__c":"a9CWR00000011QI2AY","UpdateLog__c":"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.\n\nDetection and Impact: \nOn November 17th at 10:35 AM (PT), Okta received alerts regarding resource access errors in US Cell 14. During this time, customers in US Cell 14 experienced errors, connection timeouts, and slow responses while attempting to access resources. This incident was isolated to their cell, and normal processing levels were restored at 10:45 AM (PT).\n\nRoot Cause Summary:\nOkta determined the root cause was a substantial increase in request traffic volume, which resulted in errors accessing the cell.\n\nRemediation Steps:\nThe system automatically initiated service protection within 1 minute of a traffic increase, followed by additional resource scaling actions. These automated actions addressed the issue, and the team confirmed that response times and rates had fully returned to normal by 10:45 AM(PT). Incident response teams continued to review and analyze the incident, applying additional service protection configurations to improve service resiliency immediately after the service was confirmed to be stable.\n\nPreventative Actions:\nIn order to prevent similar incidents from recurring, Okta is working in collaboration with our service provider to explore opportunities for enhanced scalability and faster mitigation action thresholds where necessary. We are fully committed to improving our infrastructure to ensure the reliability of our services. Our priority remains the continuous optimization of our systems to safeguard against future events.\n \nDuration (# of minutes): 11 minutes \nActual Time: 10:34 AM - 10:45 AM PST","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000031vs92AA"},"Id":"a1PWR0000031vs92AA","CreatedDate":"2025-12-03T07:43:45.000+0000","IncidentId__c":"a9CWR00000012Cg2AI","UpdateLog__c":"The engineering team is seeing signs of recovery, and we will continue to monitor and post another update in 30 minutes.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000031vyb2AA"},"Id":"a1PWR0000031vyb2AA","CreatedDate":"2025-12-03T08:13:43.000+0000","IncidentId__c":"a9CWR00000012Cg2AI","UpdateLog__c":"The engineering team is seeing signs of recovery, and we are continuing to monitor and will post another update in 30 minutes.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000320Jx2AI"},"Id":"a1PWR00000320Jx2AI","CreatedDate":"2025-12-03T13:57:36.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. During this time, users may be experiencing intermittent issues within our system. Our team is continuing to actively investigate and mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000320a52AA"},"Id":"a1PWR00000320a52AA","CreatedDate":"2025-12-03T14:32:07.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"At 12/3/2025 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. During this time, users may be experiencing intermittent issues within our system. Our team is actively investigating this issue and to mitigate the issue. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000320ob2AA"},"Id":"a1PWR00000320ob2AA","CreatedDate":"2025-12-03T15:02:57.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"At 12/3/2025, 5:15 AM PT, the team became aware of an issue with connectivity to our Core Platform service affecting customers in US Cell 7. Users may continue to experience intermittent issues within our system. We are actively working on mitigation efforts and will provide an update in the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000321O52AI"},"Id":"a1PWR00000321O52AI","CreatedDate":"2025-12-03T15:50:47.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"Our service is seeing recovery following successful mitigation efforts with our provider. We continue to closely monitor system stability. Our next update will be in 30 minutes, or sooner if new information is available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000321Sv2AI"},"Id":"a1PWR00000321Sv2AI","CreatedDate":"2025-12-03T16:24:13.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"We are continuing to monitor the situation. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000321xZ2AQ"},"Id":"a1PWR00000321xZ2AQ","CreatedDate":"2025-12-03T16:58:30.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"An issue impacting the core authentication service for customers in Okta Cell US7 has been resolved. Additional root cause information will be available within five business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000329gb2AA"},"Id":"a1PWR00000329gb2AA","CreatedDate":"2025-12-04T09:08:31.000+0000","IncidentId__c":"a9CWR00000012HW2AY","UpdateLog__c":"The Okta Engineering has implemented mitigations and we are monitoring for recovery and will post another update in 30 minutes.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000032CJV2A2"},"Id":"a1PWR0000032CJV2A2","CreatedDate":"2025-12-04T09:25:04.000+0000","IncidentId__c":"a9CWR00000012HW2AY","UpdateLog__c":"Current mitigations are working and we are seeing recovery across all impacted cells. Customers should be able to successfully connect to Ldap at this point. If you experience further issues, please reach out via support and full RCA will be available within 5 business days.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000034uRh2AI"},"Id":"a1PWR0000034uRh2AI","CreatedDate":"2025-12-10T07:51:11.000+0000","IncidentId__c":"a9CWR00000012EI2AY","UpdateLog__c":"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.\n\n \nDetection and Impact: \n\nOn December 2nd, 2025, at 10:22 PM PT, Okta was alerted to a substantial increase in request traffic by Okta’s external monitoring as well as our Cloud Service Provider in US Cell 7 for custom domains. (Wave 1). \n\nLater, on December 3rd, 2025, at 4:48 AM PT, Okta was again alerted to a substantial increase in network traffic in US Cell 7 for custom domain supporting resources, and the traffic pattern was not detected by the Cloud Service Provider. (Wave 2).\n\nDuring these times, customers who utilize customized domains experienced outage errors or intermittent slowness when attempting to access the service.\n \n\nRoot Cause Summary:\n\nOkta determined the root cause was a substantial increase in request network traffic volume, which resulted in errors and slow response times accessing the cell.\n\n \nRemediation Steps:\n\nWave 1: \n\nAt 10:36 PM PT, Okta Engineering initiated response procedures based on the observed service impact. Per operating procedures, the Cloud Service Provider’s system initiated mitigating actions. At 11:04 PM PT, Okta Engineering observed that the network traffic load had been mitigated and returned to normal processing levels.\n \nWave 2: \n\nAt 5:20 AM PT, traffic for Enhanced DR customers with custom domains was redirected to the rescue cell. At 5:27 AM PT, Okta Engineering scaled out infrastructure resources in an attempt to minimize the impact during this time. \nAt 5:56 AM PT, Okta further scaled out the infrastructure, but saw only minimal recovery. The Cloud Service Provider applied similar restrictions, which partially mitigated the traffic flood. At 6:20 AM, Okta took additional measures to isolate the custom domain resource stack and began moving custom domains to this new stack in coordination with our support teams.\n\nUpon further examination of the issue by Okta and after gaining an understanding of the new network flows, at 7:04 AM PT, the Cloud Service Provider updated the mitigations and immediately observed a return to normal processing levels. \n \n\nPreventative Actions:\n\nTo prevent similar incidents from recurring, Okta Engineering is collaborating with our Cloud Service Provider to understand better and analyze their overall alert triggering logic and review the processes associated with this event. We have also implemented additional protections in conjunction with our Cloud Service Provider. \n\n\nDuration (# of minutes):\n\nWave 1:\nTotal Duration (Minutes): 42 minutes \nActual Time: 10:22 PM - 11:04 PM PT \n\nWave 2: \nTotal Duration (Minutes): 136 minutes \nActual Time: 4:48 AM - 7:04 AM PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000034uTJ2AY"},"Id":"a1PWR0000034uTJ2AY","CreatedDate":"2025-12-10T07:55:57.000+0000","IncidentId__c":"a9CWR00000012Cg2AI","UpdateLog__c":"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.\n\n\nDetection and Impact:\n\nOn December 2nd, 2025, at 10:22 PM PT, Okta was alerted to a substantial increase in request traffic by Okta’s external monitoring as well as our Cloud Service Provider in US Cell 7 for custom domains. (Wave 1).\n\nLater, on December 3rd, 2025, at 4:48 AM PT, Okta was again alerted to a substantial increase in network traffic in US Cell 7 for custom domain supporting resources, and the traffic pattern was not detected by the Cloud Service Provider. (Wave 2).\n\nDuring these times, customers who utilize customized domains experienced outage errors or intermittent slowness when attempting to access the service.\n\n\nRoot Cause Summary:\n\nOkta determined the root cause was a substantial increase in request network traffic volume, which resulted in errors and slow response times accessing the cell.\n\n\nRemediation Steps:\n\nWave 1:\n\nAt 10:36 PM PT, Okta Engineering initiated response procedures based on the observed service impact. Per operating procedures, the Cloud Service Provider’s system initiated mitigating actions. At 11:04 PM PT, Okta Engineering observed that the network traffic load had been mitigated and returned to normal processing levels.\n\nWave 2:\n\nAt 5:20 AM PT, traffic for Enhanced DR customers with custom domains was redirected to the rescue cell. At 5:27 AM PT, Okta Engineering scaled out infrastructure resources in an attempt to minimize the impact during this time.\nAt 5:56 AM PT, Okta further scaled out the infrastructure, but saw only minimal recovery. The Cloud Service Provider applied similar restrictions, which partially mitigated the traffic flood. At 6:20 AM, Okta took additional measures to isolate the custom domain resource stack and began moving custom domains to this new stack in coordination with our support teams.\n\nUpon further examination of the issue by Okta and after gaining an understanding of the new network flows, at 7:04 AM PT, the Cloud Service Provider updated the mitigations and immediately observed a return to normal processing levels.\n\n\nPreventative Actions:\n\nTo prevent similar incidents from recurring, Okta Engineering is collaborating with our Cloud Service Provider to understand better and analyze their overall alert triggering logic and review the processes associated with this event. We have also implemented additional protections in conjunction with our Cloud Service Provider.\n\n\nDuration (# of minutes):\n\nWave 1:\nTotal Duration (Minutes): 42 minutes\nActual Time: 10:22 PM - 11:04 PM PT\n\nWave 2:\nTotal Duration (Minutes): 136 minutes\nActual Time: 4:48 AM - 7:04 AM PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000034uZl2AI"},"Id":"a1PWR0000034uZl2AI","CreatedDate":"2025-12-10T09:23:09.000+0000","IncidentId__c":"a9CWR00000015s62AA","UpdateLog__c":"Okta Engineering has implemented a mitigation for the issue affecting custom domain routers on Cell OK9. \r\n\r\nWe are currently observing improvements in connection stability and a reduction in error rates. We will continue to monitor the service closely to ensure full resolution.\r\n\r\nUsers accessing their Okta tenant via custom domains should see a return to normal performance. However, some customers may experience residual intermittent latency or errors while the system fully stabilises.\r\n\r\nWe will provide another update within the next 30 minutes or upon full resolution.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000034ubN2AQ"},"Id":"a1PWR0000034ubN2AQ","CreatedDate":"2025-12-10T10:01:57.000+0000","IncidentId__c":"a9CWR00000015s62AA","UpdateLog__c":"Okta Engineering has resolved the issue affecting custom domain connectivity on Cell OK9. Following the mitigation of the connection issues, we have confirmed that service performance has fully stabilised and all systems are operational.\n\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036CG52AM"},"Id":"a1PWR0000036CG52AM","CreatedDate":"2025-12-12T16:32:03.000+0000","IncidentId__c":"a9CWR00000012HW2AY","UpdateLog__c":"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 incident.\n\n\nDetection and Impact: \nOn December 3rd, at 11:51 pm PST, Okta received an alert concerning an error affecting LDAP services across multiple production cells.\n\n\nRoot Cause Summary:\nOkta has determined that this issue was related to recent changes initiated by our Cloud Service Provider as a part of resiliency improvements.\n\n\nRemediation Steps:\nOkta began diagnosing the issue immediately upon receiving reports and determined that the issue was related to the vendor’s recent changes, which were implemented to improve our resiliency as a result of previous incidents. While engaging with the Cloud Service Provider’s support team, we were able to fully restore normal functionality. \n\n\nPreventative Actions:\nOkta is reviewing and enhancing its monitoring and alerting processes to minimize the impact on customers for similar issues in the future.\n\n\nDuration (# of minutes): 87 minutes","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036iRF2AY"},"Id":"a1PWR0000036iRF2AY","CreatedDate":"2025-12-14T16:40:26.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036iSr2AI"},"Id":"a1PWR0000036iSr2AI","CreatedDate":"2025-12-14T16:42:05.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"The next update will be posted in the next 60 minutes.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036ihN2AQ"},"Id":"a1PWR0000036ihN2AQ","CreatedDate":"2025-12-14T17:50:59.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"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.\nThe next update will be provided within the next 60 minutes or sooner, if additional information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036isf2AA"},"Id":"a1PWR0000036isf2AA","CreatedDate":"2025-12-14T18:48:02.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"We have identified a potential root cause of this issue, and are currently investigating next steps towards resolution. \r\n\r\nWe will provide the next update in 60 minutes, unless new information becomes available.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000036j0j2AA"},"Id":"a1PWR0000036j0j2AA","CreatedDate":"2025-12-14T19:39:47.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"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. \r\n\r\nAdditional root cause information will be available within 5 Business days.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR00000383YT2AY"},"Id":"a1PWR00000383YT2AY","CreatedDate":"2025-12-18T02:29:01.000+0000","IncidentId__c":"a9CWR00000015s62AA","UpdateLog__c":"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.\r\n\r\n\r\nDetection and Impact: \r\nOn December 9th at 11:42 PM PT, Okta's monitoring systems alerted on-call teams to potential intermittent connectivity issues in custom domain EMEA Cell OK9. A subset of users attempting to access EMEA Cell OK9 custom domain organizations from specific geo locations, particularly France, experienced intermittent connectivity issues, including timeouts, latency, and/or 500 response errors when accessing Okta services. Users and clients accessing the custom domain resources that were not routed through these Point of Presence (PoP) network locations would not be impacted. Service was fully restored by 1:24 AM PT on December 10th.\r\n\r\n\r\nRoot Cause Summary:\r\nThe temporary disruption of network resources at certain Points of Presence stemmed from overly restrictive traffic limits that were distributed globally. These changes were implemented as a critical component of our broader, ongoing strategy to upgrade network infrastructure. The overly protective logic incorrectly caused the system to profile traffic across all global locations simultaneously. This resulted in the observed connectivity issues in European regions, particularly in France, during their local morning traffic ramp-up.\r\n \r\n\r\nRemediation Steps:\r\nUpon discovery, Okta swiftly determined the cause and worked with our Cloud Service Provider on implementing mitigation measures and rolling back changes. These steps successfully stabilized connectivity, restoring normal operations by 1:24 AM PT.\r\n\r\n \r\nPreventative Actions:\r\nWe continue to closely collaborate with our Cloud service provider to comprehensively review and enhance our edge configurations, with the focused goal of establishing a more resilient and reliable infrastructure service capacity. Our unwavering priority remains the continuous optimization of our systems to safeguard against future events.\r\n\r\n \r\nDuration (# of minutes):\r\nTotal Duration (Minutes): 102 minutes\r\nActual Time: 11:42 PM PT - 01:24 AM PT (12/10)","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR0000039Fir2AE"},"Id":"a1PWR0000039Fir2AE","CreatedDate":"2025-12-23T14:49:54.000+0000","IncidentId__c":"a9CWR00000016Ze2AI","UpdateLog__c":"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.\n\nDetection and Impact:\nOn 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.\n\nRoot Cause Summary:\nOkta 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.\n\nRemediation Steps:\nUpon 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.\n\nPreventative Actions:\nOkta 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.\n\nDuration (# of minutes):1140","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003ApvZ2AS"},"Id":"a1PWR000003ApvZ2AS","CreatedDate":"2026-01-03T01:52:45.000+0000","IncidentId__c":"a9CWR00000017982AA","UpdateLog__c":"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.\n\nDetection and Impact:\nOn December 26, 2025, at 3:27 AM PST, Okta engineering was alerted to increased errors in US Cell 6. \nDuring 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. \n\nRoot Cause Summary:\nOkta has determined that the issue was caused by an outage with our cloud service provider. All instances fully recovered by 5:43 AM PT. \n\nRemediation Steps:\nUpon 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.\n\nPreventative Actions:\nOkta 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. \n\nTotal Duration: 2 hours and 16 minutes\nStart Time: December 26, 2025, 03:27 AM PT\nEnd Time: December 26, 2025, 05:43 AM PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003GVsX2AW"},"Id":"a1PWR000003GVsX2AW","CreatedDate":"2026-01-20T16:04:45.000+0000","IncidentId__c":"a9CWR0000001Gty2AE","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003GXMT2A4"},"Id":"a1PWR000003GXMT2A4","CreatedDate":"2026-01-20T16:35:42.000+0000","IncidentId__c":"a9CWR0000001Gty2AE","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003GZ6X2AW"},"Id":"a1PWR000003GZ6X2AW","CreatedDate":"2026-01-20T17:10:30.000+0000","IncidentId__c":"a9CWR0000001Gty2AE","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003GZcn2AG"},"Id":"a1PWR000003GZcn2AG","CreatedDate":"2026-01-20T17:21:31.000+0000","IncidentId__c":"a9CWR0000001Gty2AE","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003Ie6v2AC"},"Id":"a1PWR000003Ie6v2AC","CreatedDate":"2026-01-22T21:46:01.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003IgQT2A0"},"Id":"a1PWR000003IgQT2A0","CreatedDate":"2026-01-22T23:24:23.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003IhJJ2A0"},"Id":"a1PWR000003IhJJ2A0","CreatedDate":"2026-01-23T00:46:08.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003Inuz2AC"},"Id":"a1PWR000003Inuz2AC","CreatedDate":"2026-01-23T03:55:46.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003IoUT2A0"},"Id":"a1PWR000003IoUT2A0","CreatedDate":"2026-01-23T06:46:01.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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.","CurrencyIsoCode":"AUD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003L5qz2AC"},"Id":"a1PWR000003L5qz2AC","CreatedDate":"2026-01-26T18:31:46.000+0000","IncidentId__c":"a9CWR0000001Gty2AE","UpdateLog__c":"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.\n\n\nTiming:\n\nIncident start: January 19, 2026, at 10:10 AM PST\nIncident resolved: January 20, 2026, at 11:49 AM PST\n\nDetection:\n\nOkta teams were notified via customer cases and an increase in Google Workspace import errors.\n\nImpact:\n\nAny 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=[...]”\n\nRoot Cause:\n\nGoogle 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.\n\n\nGoogle provides additional details for this disruption: https://www.google.com/appsstatus/dashboard/incidents/9q5n4sfDnxYzHj8FxEua\n\nRemediation Steps:\n\nOkta teams soon identified that a provider-side disruption was the cause of the incident and opened a formal support case to track the resolution.\n\n\nThe 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.\n\n\nOkta teams monitored the recovery in real-time and confirmed successful import signals across multiple impacted customers before standing down.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003MSf32AG"},"Id":"a1PWR000003MSf32AG","CreatedDate":"2026-01-28T19:24:03.000+0000","IncidentId__c":"a9CWR0000001SlS2AU","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003MTT32AO"},"Id":"a1PWR000003MTT32AO","CreatedDate":"2026-01-28T19:36:35.000+0000","IncidentId__c":"a9CWR0000001SlS2AU","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003NeuH2AS"},"Id":"a1PWR000003NeuH2AS","CreatedDate":"2026-01-30T22:34:22.000+0000","IncidentId__c":"a9CWR0000001HBi2AM","UpdateLog__c":"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\n\n\nTiming:\n\n\nIncident start: January 22, 2026, at 10:55 AM PST\n\n\nIncident resolved: January 22, 202,6 at 7:50 PM PST\n\n\nDetection:\n\n\nThe issue was initially identified through customer reports that they were not receiving expected email notifications.\nOkta Engineering confirmed the service disruption after internal monitoring indicated a high volume of deferred email delivery attempts to specific third-party domains.\n\n\nImpact:\n\n\nCustomers 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.\n\n\nOkta services remained healthy and attempted to resend deferred messages.\n\n\nRoot Cause:\n\n\nMicrosoft reports that it experienced a service issue within its North American data centers during a planned maintenance activity.\n\n\nAs 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.\n\n\nRemediation Steps:\n\n\nTo 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.\n\nOkta 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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003Qfdh2AC"},"Id":"a1PWR000003Qfdh2AC","CreatedDate":"2026-02-04T12:37:08.000+0000","IncidentId__c":"a9CWR0000001b5a2AA","UpdateLog__c":"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.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003QfsD2AS"},"Id":"a1PWR000003QfsD2AS","CreatedDate":"2026-02-04T12:50:37.000+0000","IncidentId__c":"a9CWR0000001b5a2AA","UpdateLog__c":"This incident has been resolved. Internal monitoring and customer reports confirm that the LDAPi system in OK9 has fully recovered and is operating normally.\nWe 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.","CurrencyIsoCode":"GBP"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003RziP2AS"},"Id":"a1PWR000003RziP2AS","CreatedDate":"2026-02-05T01:26:37.000+0000","IncidentId__c":"a9CWR0000001SlS2AU","UpdateLog__c":"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.\n\n\nDetection and Impact: \n\nOn January 29th, 2026, at 8:28 AM PT, Okta internal monitoring alerted our team of intermittent connectivity issues accessing Okta Cell 9 (EMEA). \n\nDuring 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.\n \nRoot Cause Summary:\n\nThe 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.\n\nRemediation Steps:\n\nImmediately 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.\n \nPreventative Actions:\n\nTo 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. \n\nDuration (# of minutes): 186","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003Vc8x2AC"},"Id":"a1PWR000003Vc8x2AC","CreatedDate":"2026-02-11T18:45:50.000+0000","IncidentId__c":"a9CWR0000001b5a2AA","UpdateLog__c":"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.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nThe 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. \r\n\r\n \r\n\r\nRemediation Steps:\r\n\r\nOnce 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.\r\n\r\n \r\n\r\nPreventative Actions:\r\n\r\nTo 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.\r\n\r\n \r\n\r\nDuration (# of minutes):\r\nTotal Duration (Minutes): 122 minutes \r\nActual Time: 02:24 AM PT - 04:26 AM PT","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003VmBV2A0"},"Id":"a1PWR000003VmBV2A0","CreatedDate":"2026-02-11T18:40:59.000+0000","IncidentId__c":"a9CWR0000001SlS2AU","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003sEkD2AU"},"Id":"a1PWR000003sEkD2AU","CreatedDate":"2026-03-13T18:48:40.000+0000","IncidentId__c":"a9CWR0000001dSM2AY","UpdateLog__c":"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.","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003wxcH2AQ"},"Id":"a1PWR000003wxcH2AQ","CreatedDate":"2026-03-20T20:35:05.000+0000","IncidentId__c":"a9CWR0000001dSM2AY","UpdateLog__c":"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.\n\nDetection and Impact\n\nOn 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.\n\nThis 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.\n\n \n\nRoot Cause Summary\n\nThe 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.\n\nRemediation Steps\n\nUpon 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.\n\nPreventative Actions\n\nOkta 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.\n\n\nStart Time: 03/13/2026 10:17 AM PT\nEnd Time: 03/13/2026 11:21 AM PT\n\nDuration (# of minutes): 64","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v66.0/sobjects/IncidentUpdate__c/a1PWR000003yVGv2AM"},"Id":"a1PWR000003yVGv2AM","CreatedDate":"2026-03-24T23:32:24.000+0000","IncidentId__c":"a9CWR0000001dgs2AA","UpdateLog__c":"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.\n\nDetection and Impact:\nOkta internal monitoring alerted our engineering team to disruptions to the Okta status page and the commercial support portal.\nOkta Engineering identified a service disruption with our third-party provider and confirmed the impact.\n\nDuring 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).\n\nRoot Cause Summary:\nOkta’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.\n\nRemediation Steps:\nOkta 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.\nServices were fully restored after the third-party provider successfully deployed a fix-forward release to the impacted infrastructure, which restored login access.\n\nPreventive Actions:\nAs 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.\n\nTiming:\nIncident start: March 16, 2026, at 08:58 PM PDT\nIncident resolved: March 16, 2026, at 11:34 PM PDT\n\nDuration (# of minutes): 156 minutes","CurrencyIsoCode":"USD"}]
a9bd3885-93ae-46ab-700b-dd29e613c19d