Customers experiencing any issues related to API Access Management should contact Support. On March 22nd, Okta stated that it "detected an attempt to compromise the account . Okta implemented mitigation steps and the errors subsided at approximately 12:06pm PST. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000007eNdTUAU"},"Id":"a1P0Z000007eNdTUAU","CreatedDate":"2018-05-17T19:24:28.000+0000","IncidentId__c":"a9C0Z000000TNgDUAW","UpdateLog__c":"Okta is actively working to mitigate the issues impacting authentication and user interactive errors in US Cell 6. Our monitoring shows a return to normal conditions with SMS MFA. Cloudflare Inc. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005XaYwUAK"},"Id":"a1P0Z000005XaYwUAK","CreatedDate":"2018-10-25T03:43:48.000+0000","IncidentId__c":"a9C0Z0000008PViUAM","UpdateLog__c":"Resolved: An issue impacting compatibility with Office 365 user provisioning has been resolved. It was determined 366 Okta customers were potentially impacted in that incident, though Okta later said it . ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRdMEAU"},"Id":"a1P4z000009mRdMEAU","CreatedDate":"2022-11-05T00:40:46.000+0000","IncidentId__c":"a9C4z000000YzhlEAC","UpdateLog__c":"An issue impacting Okta email delivery for end users in all cells continues to be mitigated. Generally, customers would have seen a ~35% error rate attempt to load the login page. \r\n\r\n\r\nAt 2:39pm Okta initiated a rollback of the maintenance operation in US Cell 10 and at 2:41p PST error rates started to decrease. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRfIEAU"},"Id":"a1P4z000009mRfIEAU","CreatedDate":"2022-11-09T20:38:06.000+0000","IncidentId__c":"a9C4z000000YzhvEAC","UpdateLog__c":"Okta continues to monitor the current issue with our partners regarding the SMS delivery delays using US-based phone numbers. US Cell-5 recovered at 10:56 AM PDT and US Cell-10 recovered at 10:52 AM PDT.\r\n\r\nAdditional root cause information will be available within 2 Business days. Users attempting to authenticate with Office 365 are receiving a \"Throttled\" message. We are actively working to mitigate job processing delays and will continue to provide updates as they are available. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000005V3qMUAS"},"Id":"a1P1Y000005V3qMUAS","CreatedDate":"2019-02-06T01:40:53.000+0000","IncidentId__c":"a9C1Y000000GpKsUAK","UpdateLog__c":"A fix has been identified where office 365 users are seeing provisioning errors. Furthermore, while Okta does perform end to end testing for its O365 application, there was insufficient coverage to adequately test Group Push provisioning to O365.\r\n\r\nRemediation Steps:\r\n\r\nAt 1:50 PM PST, Okta began deploying a fix to address the inability to successfully perform Group Push in the O365 application. Advanced Server Access team restarted the service and it helped restore database connectivity. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zJUvUAM"},"Id":"a1P1Y000007zJUvUAM","CreatedDate":"2019-11-22T16:15:09.000+0000","IncidentId__c":"a9C1Y0000004E4JUAU","UpdateLog__c":"Root Cause Analysis: On Nov 19th at approximately 12:30 PM PDT, customers reported that when opening the Okta Mobile application for Android, end users were intermittently logged out of their account and encountered the following message:\r\n\r\nDetected possible malicious activity when establishing a secure connection to Okta.\r\n\r\nUpon investigation, Okta determined that the issue was caused by an update to the preferred authentication algorithm used in TLS by Okta Mobiles error tracking provider. The highest concentration of unsuccessful attempts was observed between 9:20am PST to 9:30am PST.\r\n\r\nAt approximately 9:35am PST, our service provider mitigated the internet connectivity issue by redirecting international traffic to Australia through an alternate provider and by 11:00am PST the service was operating as expected.\r\n\r\nGiven the lack of information regarding the root cause and scope of the service provider issue and how that might impact access of Australian users to our Disaster Recovery cell in Singapore, Okta elected not to reroute traffic to the Disaster Recovery cell \r\n\r\nOkta is working closely with the provider to investigate improved mitigations to improve response to these types of incidences. Okta Engineerings analysis shows that 0.9% of users who installed Okta Verify for Android version 7.9.1 were impacted; this represents 0.01% of users using Okta Verify for Android.\r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nThe incident's root cause is a regression from a third-party library update included in the Okta Verify 7.9.1 update. 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 February 3, 2023 at 10:11am (PT) Okta was alerted to a decrease in inbound connections to the Okta service in US Cell 1, 2, 3, and 4. In the event that you need assistance in implementing the resolution guide, please contact customer support for assistance. By 8:09 AM PST, normal service performance was fully restored.\r\n\r\nOkta is implementing additional monitoring, optimization, and mitigation strategies to prevent similar issues in the future. We will provide an update in 30 minutes or sooner if additional information becomes available. The procedural error targeted the security patching to a high usage cache cluster. A fix has been identified and we are working to return the service to normal as quickly as possible. Users of browsers other than Chrome, and users of Chrome earlier than version 77, were not impacted. Our next update will be in the next 30 min. Okta says there was no unauthorized access to the Okta service or customer data, and products related to Auth0 which it acquired in 2021 are not impacted. We will focus on improving customer communications in the case of vendor supplied ICA chain updates in future certificates updates to help prevent similar issues, as well as a recurrence of this issue. On February 7 at 9:20 AM the issue was mitigated and Oktas systems showed a return to normal SMS delivery. \r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, Okta is including additional runbook improvements and adding additional capacity to the affected infrastructure component. We continue to add more capacity to resolve the backlog as quickly as possible. Okta's silence quickly drew speculation and criticism from high-profile names in the security industry, ordinary people on social media, its competitors, and even Lapsus$, which was pushing back . Additional root cause information will be provided within 48 hours. \r\n\r\nOkta confirmed the issue was with its downstream primary provider by reviewing information posted on the providers status page.\r\n\r\nRoot Cause Summary:\r\nThe primary SMS provider experienced connection instability issues with one of its downstream providers. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zKsoUAE"},"Id":"a1P1Y000007zKsoUAE","CreatedDate":"2020-04-16T00:41:22.000+0000","IncidentId__c":"a9C1Y0000004EI1UAM","UpdateLog__c":"Okta has observed an issue with the new 5.0.2 version of Okta Verify for iOS. Some office 365 users are seeing provisioning errors \"An error occurred while assigning this app\" when assigning users to the application. Our monitoring shows a return to normal conditions with Okta email deliverability. The Workflows team continues to monitor the Workflows service. We are continuing to work on full mitigation. Investigation revealed that this issue impacted custom URL domain users on US Cell 10. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000007eJUoUAM"},"Id":"a1P0Z000007eJUoUAM","CreatedDate":"2018-04-24T15:17:52.000+0000","IncidentId__c":"a9C0Z000000TNeqUAG","UpdateLog__c":"An issue impacting authentication for a subset of end users in US Cell 2 is being investigated. \r\n\r\n \r\n\r\nDuring the duration of the incident, customers within APAC Cell 1 and US Cell 5 would have been unable to access the workflow designer tool and background workflow processes were held in queue for delayed processing. Engineering is working to identify the list of customers still impacted and is investing a way to proactively address the issue for these customers. The dashboard queries data from secondary read-only databases which were impacted by a replication error. Starting at 6:08am (PT) some Okta Agents were identified as disconnected. We are also actively monitoring the systems. Additional information is in https://status.okta.com/#incident/a9C4z000000wkAXEAY","Status__c":"Resolved","Start_Date__c":"2022-02-03","End_Date__c":"2022-02-03","Last_Updated__c":"2022-02-08T14:35:42.000+0000","LastModifiedDate":"2022-02-08T14:35:42.000+0000","Category__c":"Service Disruption","Is_Mis_Red__c":false,"Size__c":"Small","Impacted_Cells__c":"okta-emea.com:1;okta.com:1;okta.com:2;okta.com:3;okta.com:4;okta.com:5;okta.com:6;okta.com:7;oktapreview.com:1;oktapreview.com:2;okta.com:8;okta.com:9;okta.com:10;okta.com:11;okta.com:12;okta.com:15;oktapreview.com:3;okta.com:14;okta-gov.com:1;okta.com:16","Impacted_Audience__c":"End user","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"MFA","Start_Time__c":"2022-02-03T17:32:00.000+0000","CreatedDate":"2022-02-03T17:33:46.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000wkADEAY"},"Id":"a9C4z000000wkADEAY","Duration__c":1501,"Log__c":"Resolved: An issue impacting Authentication for certain embedded browser usecases for all endusers in US-Cell 1 and US-Cell 9 was addressed. Approximately 7% to 10% of requests were impacted. Work is on-going to fully restore the feature for all remaining customer tenants. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000005qK7eUAE"},"Id":"a1P1Y000005qK7eUAE","CreatedDate":"2019-09-10T06:20:40.000+0000","IncidentId__c":"a9C1Y000000fxj2UAA","UpdateLog__c":"ROOT CAUSE: On September 5th, at approximately 12:27 PM PDT Okta detected an issue in the Developer tenant's activation email which impacted developer org creation in US Preview 1 and US Cell 7. At 4:25PM (PT), Okta rolled back the app configuration in an attempt to restore the system to its prior state. We are performing Zone isolation on the impacted regions. Outlined below are the facts regarding this incident. There was no impact to authentication for provisioned users.\r\n\r\nUpon investigation, Okta determined that the protocol leveraged by Okta for provisioning users and making configuration changes to Office 365 was no longer compatible with a new Office 365 version that was being gradually rolled out which resulted in the intermittent errors.\r\n\r\nOn February 17th at 3:45 pm (PST), Okta began to deploy a fix on a cell by cell basis. The success rate began to gradually improve from 8:07am, and by 8:25am approximately 80% of requests were successfully returned. We will provide an update in 30 minutes or sooner if additional information becomes available. By 6:08 pm PST, the cell had returned to normal performance levels.\r\n\r\nOkta has completed work to up-size our Redis caching clusters in US Cell 6 and will deploy the same mitigating changes across all remaining cells. At approximately 3:35PM, the service was restored and operating as expected.\r\n\r\nPreventive Actions:\r\n\r\nOkta is working closely with the provider to investigate mitigations and improve response to these types of incidences. During this time, customers may have received Http 500 errors, and Directory and IWA agents may have experienced intermittent connections. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000007sutAEAQ"},"Id":"a1P4z000007sutAEAQ","CreatedDate":"2022-08-29T10:26:10.000+0000","IncidentId__c":"a9C4z0000012OU8EAM","UpdateLog__c":"An issue impacting authentication for all newly created users in US Cell-6 has been mitigated. Outlined below are the facts regarding this incident. A delay in event hook delivery has been identified and is being addressed. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRe0EAE"},"Id":"a1P4z000009mRe0EAE","CreatedDate":"2022-11-06T20:06:18.000+0000","IncidentId__c":"a9C4z000000YzhlEAC","UpdateLog__c":"Okta is continuing to work on resolving the issue with email delivery to Yahoo end-users.\r\nImpacted domains include: yahoo.com (yahoo.co.uk, etc. Work is on-going to fully restore the feature for all remaining customer tenants. This caused SMS delivery delays and failures for the subscribers of their service.\r\n\r\nPreventive Actions:\r\nThe root cause of the issue occurred within the telecommunication infrastructure rather than with one of our downstream telecommunications providers. After deploying the fix, we are still seeing a number of issues. Customers experienced test card timeouts, errors in starting flow executions, and could not enable/disable okta event hook workflows. January 20, 2022, at 23:46 | Okta Security investigated the alert and escalated it to a security incident. By 10:22am PDT, Administrator dashboards displayed all current data. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. \r\n\r\n \r\n\r\nOktas monitoring has determined that there are three categories of impact: \r\n\r\n \r\n\r\nCategory 1: Inbound connections to Okta and errors from the Okta service starting at 9:56AM\r\n\r\nUS Cell 6: up to 34% failure rate, ending at 10:36AM \r\n\r\nUS Cell 10: up to 7% failure rate, ending at 10:39AM \r\n\r\nUS Cell 11: up to 24% failure rate, ending at 10:39AM \r\n\r\n \r\n\r\nCategory 2 (US Cell 6 and US Cell 10): Cells were in Read Only Mode starting at 9:56AM\r\n\r\nUS Cell 6: ending at 11:27AM\r\n\r\nUS Cell 10: ending at 11:37AM\r\n\r\nCategory 2 (US Cell 11): Increased error rates due to internal networking infrastructure errors starting at 9:56AM\r\n\r\nUS Cell 11: up to 12% failure rate, ending at 11:05AM\r\n\r\n \r\n\r\nCategory 3 : Job processing impacts starting at 9:56AM\r\n\r\nUS Cell 6: ending at 12:12PM \r\n\r\nUS Cell 10: ending at 12:08PM \r\n\r\nUS Cell 11: ending at 12:13PM \r\n\r\n \r\n\r\nRoot Cause Summary:\r\n\r\nOktas cloud service provider experienced a loss of power incident which resulted in a partial outage in a single availability zone within a region causing inbound and outbound connection errors that impacted the Okta service. These instructions have not changed since their release on November 15 and no additional action or changes are required following this issue\r\n\r\nWe request that customers needing assistance implementing the resolution contact Okta Support. Okta Engineering is actively working on a fix and will release new versions of Okta Mobile and Okta Verify as soon as they are ready. They can work around this issue by entering the verification code displayed on Okta Verify. ","Status__c":"Resolved","Start_Date__c":"2023-05-11","End_Date__c":"2023-05-11","Last_Updated__c":"2023-05-16T19:10:53.000+0000","LastModifiedDate":"2023-05-16T19:10:53.000+0000","Category__c":"Service Degradation","Is_Mis_Red__c":false,"Size__c":"Large","Incident_Title__c":"Workflows service degradation 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","Impacted_Audience__c":"Admin;API Products","Service_Feature__c":"Core Service","Okta_Sub_Service__c":"Workflows","Start_Time__c":"2023-05-11T19:50:00.000+0000","CreatedDate":"2023-05-11T19:56:37.000+0000","CurrencyIsoCode":"USD"},{"attributes":{"type":"Incident__c","url":"/services/data/v57.0/sobjects/Incident__c/a9C4z000000TXD9EAO"},"Id":"a9C4z000000TXD9EAO","Duration__c":24,"Log__c":"At 6:00 AM PDT on May 11, 2023, some Okta users experienced an increase in error rates, slow response times and may receive HTTP 429 Too many requests response code in US-Cell 2. We have deployed a fix across all cells. Additionally, customers using Oktas Angular, React and Vue integration libraries and OAuth 2.0 in Preview cells were also impacted by this issue. Microsoft is continuing to work towards full recovery from this outage and further information is available from Microsoft via https://status.azure.com/en-us/status","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000009QRAbUAO"},"Id":"a1P1Y000009QRAbUAO","CreatedDate":"2020-09-29T05:02:13.000+0000","IncidentId__c":"a9C1Y0000008Pa9UAE","UpdateLog__c":"O365 Provisioning is starting to recover but Okta is still seeing intermittent provisioning failures. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005Xb1FUAS"},"Id":"a1P0Z000005Xb1FUAS","CreatedDate":"2018-11-14T19:13:55.000+0000","IncidentId__c":"a9C0Z0000008PW7UAM","UpdateLog__c":"Resolved: Okta received reports of delays and failures in the delivery of SMS for multi-factor authentication. We've identified a workaround on the customer side to resolve the network issue. Okta is responding to a major security incident for the second time this year. As a workaround, customers can utilize portal.microsoft.com to access the Microsoft Office 365 Portal. I think you've heard a lot of it in some of the other conversations this . This fix was deployed to US Cell 1 at 8:49pm PST and then to all cells. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKsREAX"},"Id":"a1P4z00000BAKsREAX","CreatedDate":"2022-02-03T17:41:03.000+0000","IncidentId__c":"a9C4z000000wkAIEAY","UpdateLog__c":"An issue impacting SMS as a factor for US users has been identified, our monitoring is showing recovery. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zHk3UAE"},"Id":"a1P1Y000007zHk3UAE","CreatedDate":"2019-10-01T01:11:23.000+0000","IncidentId__c":"a9C1Y0000004DyLUAU","UpdateLog__c":"Our team is continuing to work on the workaround to resolve this issue. \r\n\r\n\r\nDetection and Impact: \r\n\r\nOn May 18th, 2023 at 1:55 PM (PT), Okta Technical Operations teams began receiving alerts that some Okta users in the OP1 Preview cell experienced an increase in error rates, slow response times and some may have received HTTP 429 Too many requests response code.\r\n\r\nIt was further observed that the increase in error rates occurred in two discrete time periods during this incident. . For those users with a secondary MFA factor enrolled, a backup factor can be used.\r\nNext update in 3 hours. 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 11 at 6:00 am PDT, Okta Technical Operations teams were alerted to an issue where some Okta users experienced an increase in error rates, slow response times and may have received HTTP 429 Too many requests response code in US-Cell 2, due to an issue with one of our databases. \r\n\r\nRemediation Steps:\r\nAt 7:43PM PDT, Okta began to address the impact by removing the affected router from the Custom Domain Target Group. Delays and increased error rates were observed within SysLog event processing and Event Hooks (WebHooks). Okta services impacted due to the Microsoft outage include: Provisioning to Azure AD and some SSO. Additionally, Okta plans to implement a connection-pooling proxy in front of the primary ASA database cluster to prevent future occurrences of this issue. Were reverting the update to remediate the problem","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P0Z000005XZDOUA4"},"Id":"a1P0Z000005XZDOUA4","CreatedDate":"2018-09-05T19:16:27.000+0000","IncidentId__c":"a9C0Z0000008PU1UAM","UpdateLog__c":"We are actively working with Microsoft who has reported this is related to mitigation activities from yesterday's service disruption (MO147606):\r\n\r\n\r\n\"We identified and reverted an update that was causing multiple services to be throttled. \r\n\r\n- Improve our communication processes to ensure that Okta is providing greater visibility on our \r\n\r\n- Trust site into what is being done to identify and rectify the issue.\r\n\r\n- Improve Support Case Handling & Resourcing during critical events","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRbBEAU"},"Id":"a1P4z000009mRbBEAU","CreatedDate":"2022-11-01T20:30:58.000+0000","IncidentId__c":"a9C4z000000YzhREAS","UpdateLog__c":"An issue impacting Multifactor Authentication for end users in all cells has been identified and is being investigated. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRu3EAE"},"Id":"a1P4z000009mRu3EAE","CreatedDate":"2022-12-23T18:58:08.000+0000","IncidentId__c":"a9C4z000000Yzj3EAC","UpdateLog__c":"We sincerely apologize for any impact this incident may have caused to you, your business, or your customers. You can find the knowledge article at support.okta.com. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zKbTUAU"},"Id":"a1P1Y000007zKbTUAU","CreatedDate":"2020-02-27T20:10:49.000+0000","IncidentId__c":"a9C1Y0000004EBtUAM","UpdateLog__c":"Okta has reproduced the issue and is working towards a resolution. We will provide an update within the next 30 minutes. It applies to anything from your corporate website going down, to the loss of a database server, or even security incidents such as a user workstation compromised by malware. Okta confirmed with our downstream telecommunications providers that this was a network issue with multiple US carriers which had started at 10:55AM PST and resolved by 12:05PM PST. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKvGEAX"},"Id":"a1P4z00000BAKvGEAX","CreatedDate":"2022-02-18T02:17:10.000+0000","IncidentId__c":"a9C4z000000wkBBEAY","UpdateLog__c":"Resolved: An issue with Microsoft O365 Push Groups failing after Production Release version 2022.02.1 in all production cells has been resolved. \r\n\r\n \r\n\r\nWhile recovering the service, Okta had to restore internal services impacted by the outage which resulted in extended read only mode and web request errors. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKwxEAH"},"Id":"a1P4z00000BAKwxEAH","CreatedDate":"2022-04-05T16:47:26.000+0000","IncidentId__c":"a9C4z000000wkCJEAY","UpdateLog__c":"Resolved: Investigation of the the LDAP connection service has been completed and service has been restored on all cells. However, because of the issue, Cell 5 experienced a spike in access requests (429s) which resulted in some users encountering access violations until 11:07AM(PT), at which time traffic access returned to normal rates. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000009QRk0UAG"},"Id":"a1P1Y000009QRk0UAG","CreatedDate":"2021-02-24T05:47:30.000+0000","IncidentId__c":"a9C1Y0000008PhPUAU","UpdateLog__c":"Root Cause Analysis: \r\nAt 12:04pm PST on February 20th, Okta monitoring alerted that static assets were intermittently unavailable in US Cell 5. Stating that the "impact of the incident was significantly less than the maximum potential impact" the company had previously shared last month, Okta said the intrusion impacted only two customer tenants, down from 366 as was initially assumed. Our next update will be in an hour or sooner if additional information becomes available. \r\n\r\nPreventative Actions\r\n\r\nTo ensure this does not happen again, Okta has applied configuration updates to mitigate the issue which resulted in high database CPU. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P1Y000007zJinUAE"},"Id":"a1P1Y000007zJinUAE","CreatedDate":"2019-12-04T21:21:42.000+0000","IncidentId__c":"a9C1Y0000004E65UAE","UpdateLog__c":"Okta has identified the cause of the Workday import triggering users to be placed in No Password state in US Cell 3. Our monitoring shows recovery and the next update will be in 2 hours or sooner if additional information becomes available. \r\n\r\nThis caused SMS delivery delays and failures for the subscribers of their service. We are actively monitoring systems. Okta Verify on Android, and iOS 13 & 14, remain unimpacted.\r\n\r\nWe will provide the next update tomorrow (11/28/2020) or as soon as we have approval from Apple. Additional root cause information will be provided within 48 business hours. Investigation revealed one of Oktas cloud service providers was experiencing a regional outage for a data streaming service. See below. We are committed to implementing improvements to the service to reduce the likelihood of any future occurrences of this kind.\r\n\r\n \r\nDetection and Impact: \r\n\r\nOn November 4th at 1:00 pm (PT), Okta was alerted to email deliverability issues related to third party email service providers. We have deployed a fix across all cells. Additional root cause information will provided within 2 business days. On September 29 at approximately 2:40 am PDT, service was fully restored. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z000009mRhOEAU"},"Id":"a1P4z000009mRhOEAU","CreatedDate":"2022-11-15T22:30:00.000+0000","IncidentId__c":"a9C4z000000Yzi5EAC","UpdateLog__c":"An issue impacting Microsoft O365 Federated Single Sign-On for all end users in all cells has been identified. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000G0UpTUAV"},"Id":"a1P2A00000G0UpTUAV","CreatedDate":"2018-03-07T20:45:51.000+0000","IncidentId__c":"a9C2A000000PBikUAG","UpdateLog__c":"Okta continues to address issues with the API Access Management feature. \r\nAt approximately 8:09AM (PT), the service was restored and operating as expected. Additional root cause information will be provided here as soon as it is available. As Okta maintains a restrictive firewall policy that defaults to denying access unless expressly allowed by a rule, the rule replacement further restricted inbound traffic to hosts and caused traffic to be blocked. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKtAEAX"},"Id":"a1P4z00000BAKtAEAX","CreatedDate":"2022-02-06T06:23:37.000+0000","IncidentId__c":"a9C4z000000wkAXEAY","UpdateLog__c":"Okta continues to monitor intermittent errors and retries with SMS third-party SMS providers to US-based phone numbers. Root cause analysis will be completed within the next 2 business days. Engineering is working to identify the list of customers still impacted and is investing a way to proactively address the issue for these customers. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P4z00000BAKlzEAH"},"Id":"a1P4z00000BAKlzEAH","CreatedDate":"2021-10-27T19:40:46.000+0000","IncidentId__c":"a9C4z000000wk5IEAQ","UpdateLog__c":"Our monitoring shows a return to normal conditions with MFA for customers that utilize SMS with AT&T. ","CurrencyIsoCode":"USD"},{"attributes":{"type":"IncidentUpdate__c","url":"/services/data/v57.0/sobjects/IncidentUpdate__c/a1P2A00000Fj03vUAB"},"Id":"a1P2A00000Fj03vUAB","CreatedDate":"2017-05-15T13:52:05.000+0000","IncidentId__c":"a9C2A000000blruUAA","UpdateLog__c":"Okta is continuing to investigate the cause of the slow interactive response times in US Cell 2.