http://status.okta.com/services/xml/OktaTrustRSS 2025-05-09T15:10:47.164Z Okta Status 2025-04-30T16:47:04.000Z https://www.salesforce.com/a9CKZ000000oLkp2AE Okta Engineering became aware of an issue with a downstream email provider. Customers may experience errors with MFA Emails, password reset, and user activation. 2025-04-23T22:17:50.000Z https://www.salesforce.com/a9CKZ000000oLkk2AE Okta Engineering became aware of an issue with the Apple Business Manager integration. Customers may experience errors while setting up the integration. As of 5:54 PM PT Apple has informed us resolution of the issue 2025-04-11T21:39:39.000Z https://www.salesforce.com/a9CKZ000000sXtm2AE 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. 2025-02-24T19:21:23.000Z https://www.salesforce.com/a9C4z000001BZi5EAG 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. Root cause information: We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On January 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. Root Cause Summary: Okta’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. Remediation Steps & Preventative Actions: Okta 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. Okta 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. 2025-02-21T18:20:09.000Z https://www.salesforce.com/a9C4z000000TXJ3EAO 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. 2025-01-24T07:04:02.000Z https://www.salesforce.com/a9C4z000000TXIxEAO 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. During 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. Root cause information: 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. Detection and Impact On 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. Root Cause Summary Based 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. Remediation Steps Immediately 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. Preventative Actions Okta 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. 2025-01-23T00:32:56.000Z https://www.salesforce.com/a9C4z000001BZiUEAW 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. Root cause information: We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact: On January 14th at 9:22AM PT Okta internal monitoring alerts indicated errors in loading custom domains in OK Cell 8. During this time customers who utilize customized domains in OK Cell 8 experienced errors accessing the service. Root Cause Summary: In 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. Remediation Steps: At 9:24AM PT, Okta Engineering quickly identified the issue and resolved it by placing healthy servers in service. Preventative Actions: Okta 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. 2024-12-20T22:59:27.000Z https://www.salesforce.com/a9C4z000001BZgOEAW 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. 2024-12-18T23:59:23.000Z https://www.salesforce.com/a9C4z000001BZg9EAG 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. 2024-11-23T00:25:52.000Z https://www.salesforce.com/a9C4z000000TXInEAO 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. 2024-11-19T21:37:23.000Z https://www.salesforce.com/a9C4z000001BZecEAG 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. Okta Engineering is investigating and working to resolve this as quickly as possible. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. 2024-11-04T23:26:04.000Z https://www.salesforce.com/a9C4z000001BZdAEAW 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. 2024-10-29T16:09:25.000Z https://www.salesforce.com/a9C4z000000TXIYEA4 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. 2024-10-21T17:25:10.000Z https://www.salesforce.com/a9C4z000001BZcREAW 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. The 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. 2024-10-10T20:50:37.000Z https://www.salesforce.com/a9C4z000001BZcHEAW 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. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. 2024-10-09T16:16:33.000Z https://www.salesforce.com/a9C4z000000TXIiEAO 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. 2024-10-09T13:13:55.000Z https://www.salesforce.com/a9C4z000001BZbnEAG 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. 2024-10-09T13:12:46.000Z https://www.salesforce.com/a9C4z000001BZc7EAG 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. 2024-10-09T13:11:56.000Z https://www.salesforce.com/a9C4z000001BZcCEAW 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. 2024-08-21T05:49:14.000Z https://www.salesforce.com/a9C4z000000TXIdEAO 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. Additional root cause information will be available within 5 Business days. 2024-08-15T23:00:23.000Z https://www.salesforce.com/a9C4z000001BZakEAG 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. We'll provide an update in 30 minutes or sooner if additional information becomes available. 3: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. We'll provide an update in 30 minutes or sooner if additional information becomes available. 3:32pm PDT: The issue impacting FL1 has been addressed. Okta’s monitoring shows recovery to normal conditions. Additional root cause information will be available within 5 business days. 2024-07-19T18:42:53.000Z https://www.salesforce.com/a9C4z000000TXIEEA4 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. 2024-07-19T18:42:25.000Z https://www.salesforce.com/a9C4z000001BZYoEAO 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. 2024-07-19T18:42:02.000Z https://www.salesforce.com/a9C4z000000TXIOEA4 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. To 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. 2024-07-19T18:41:42.000Z https://www.salesforce.com/a9C4z000000TXITEA4 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 2024-06-19T00:05:53.000Z https://www.salesforce.com/a9C4z000000TXIJEA4 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. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C0Z0000004E5ZUAU Resolved: On June 6th, beginning at 5:12am PDT, Okta experienced elevated CPU processing on application servers across all cells triggering automated alerts. Given the quantity of servers with increased CPU processing, customer impact was a possibility and hence the determination was made to post proactively to the [https://trust.okta.com](https://trust.okta.com) page. The increase in processing levels however was sustainable by the infrastructure and thus customer impact through the duration of the incident remained negligible. The increase in CPU processing levels ended at 5:59am PDT when an operational script, related to edge service protection, was terminated. The script has been updated to avoid a recurrence of the increase to CPU processing levels. <br><br> Event Root Cause Analysis details can be found [here]( https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Alert-06-06-2018). 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y000000GpKsUAK Okta is currently experiencing an issue where errors have been reported with O365 provisioning. The incident is now resolved - Resolved: The issue impacting office 365 users experiencing provisioning errors has been fixed in EU1, OP1, OK1, OK2, OK3, and OK5. Service has been restored to normal. Resolved: On Feb 5th at approximately 4:10pm PDT, Okta began receiving sporadic reports from customers in US Cell 1 and EMEA Cell 1 who were experiencing errors while attempting to provision users to Office 365 or modifying Office365 configuration settings. User authentication was not impacted at any point. The root cause was traced to a serialization bug that affected a portion of Office365 application tenants. In particular, those where federation was auto configured using the Okta Admin UI prior to 2016, or manually configured by running the Okta provided Azure AD powershell cmdlets. Once the root cause was identified, Okta deployed a fix starting at 5:17pm PDT on Feb 5. At 7:42pm PDT, the fix was completely rolled out to all production cells, and functionality was fully restored. Testing and monitoring are being augmented to prevent future occurrences. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C2A000000Kz0CUAS Between 7:13am - 7:43am PDT and 8:22am - 9:30am PDT, Okta observed a noticeable increase in the volume of SMS retries across all Cells except US Cell 3. An increase in the volume of SMS retries indicates delays in SMS message delivery for customers. As such, customers leveraging SMS for Multifactor Authentication or Account Recovery may not have received the SMS message and would have been prompted to retry. Upon retry, automated fail-over to Okta's other SMS vendor occurred and SMS responses were successfully delivered which minimized impact. All other authentication factors, such as Okta Verify, Voice call, Duo, Yubikey, Google Authenticator, or Security Question were not affected. <br><br> Review the root cause analysis [here]( https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-SMS-Service-Degradation-10-19-2017) for this event for greater details about the issues and the changes being enacted to mitigate risks to user flows when new features are released. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y0000004EBtUAM Okta is currently investigating an issue preventing some customers from proceeding past the API enablement step when configuring AWS in Okta. We are actively investigating and will update this message with more information as soon as we have it. Root Cause Analysis: On February 27th at approximately 8:15 am PST, Okta received a customer report of an error in US Cell 1 when attempting to add an additional AWS account. Upon investigation, Okta found that customers in all cells would experience errors if attempting to add child AWS accounts or modify existing AWS integration configurations. In order to prevent further issues to customer configurations, Okta immediately made all AWS app instance configurations read-only. This change was rolled out to all cells by 1:41 pm PST until the root cause of the authentication issues could be identified and resolved. Further investigation determined that the errors were the result of a recent upgrade to the AWS SDK which conflicted with Okta's existing logic for resolving STS endpoints. In the majority of configurations, Okta's logic would previously default to the Global STS endpoint, however after the upgrade the same resolution process began always returning the lexicographically first endpoint, which was the STS endpoint for the Asia Pacific region (Hong Kong). Because the Version 1 STS tokens that Okta generates are only valid in regions which are enabled by default, and Asia Pacific is not enabled by default, Okta's subsequent AssumeRole calls to that region were failing. Though the SDK upgrade was tested in some environments, the affected configuration workflow had not been incorporated into any automated or manual end-to-end testing flows; this service interruption highlighted a gap in our regression test plan within the AWS application integration. Once Okta determined the cause of the errors, a fix was implemented to route all STS calls to the global endpoint. This fix was deployed to US Cell 1 at 8:49 pm PST and then to all cells. By February 28 at 9:01 pm PST, the update was completed and service was fully restored. Okta is currently working to update how endpoints and regions are passed to the AWS SDK to increase efficiency and reduce latency. As part of our on-going focus on reliability, Okta is also actively working to identify and audit test cases where application integrations and core infrastructure rely on common elements to prevent issues like this from occurring in the future. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y0000004E4JUAU Okta is investigating an issue with installations of Okta Mobile on Android. We will provide more information once available. Resolved: Okta has addressed an issue on Okta Mobile for Android for the vast majority of Okta end users. When opening the Okta Mobile for Android application, end users may be logged out of their account and encounter the following message: “Detected possible malicious activity when establishing a secure connection to Okta”. Okta Mobile Android users on Android 6.0 or higher must update the Okta Mobile application to the latest version through the Google Play Store. Okta continues to investigate a solution for users running versions of Android below 6.0 as well as those relying on downloading the Okta Mobile APK from their Okta tenant. We apologize for the inconvenience. Additional root cause information will be provided within 48 business hours. 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: “Detected possible malicious activity when establishing a secure connection to Okta”. Upon investigation, Okta determined that the issue was caused by an update to the preferred authentication algorithm used in TLS by Okta Mobile’s error tracking provider. The new preferred authentication algorithm chosen by the provider became ECDSA, which was not allowed by the Okta Mobile Android application. Upon detecting a change in the encryption algorithm in use, Okta Mobile on Android is designed to present the aforementioned warning message. On Nov 19th at approximately 8:45 PM PDT, Okta released Android Okta Mobile version 4.3.2, for Android versions 6.0 and above, and notified Org administrators through the Admin Console banner that users should update their Okta Mobile application to address the issue. Users running an older version of Android are encouraged to update their device to 6.0 or later and install the latest version of Okta Mobile. Okta is implementing additional monitoring and alerting to detect such issues earlier in the future. Additionally, the latest Android Okta Mobile version has expanded the set of authentication algorithms allowed and newer versions will include an improved design to prevent issues like this in the future. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C0Z000000TNelUAG On April 23, at 9:04am PDT, Okta initiated steps to rate limit the Events API endpoint across all preview and production cells so that a fix could be applied. While the fix was in progress, customer integrations attempting to reach the /api/v1/events endpoint would have received a 429 error response. By 2:43pm PDT, the fix had been fully applied across all cells. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y0000004E2wUAE 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. Office 365 policies are denying access to users. Resolved: Okta has successfully deployed and verified a fix across all Cells. The identified issue impacted a subset of the users in all cells using legacy protocol sign-on with Office 365 or service accounts. Additional root cause information will provided within 48 hours. Root Cause Analysis: On Nov 6th at approximately 9:30 AM PDT, Okta received reports from certain customers across multiple cells that some users were not able to log into the Okta Service via Office 365 clients using legacy protocols such as the Outlook Desktop App, and some service accounts used for automation. Only end users using Outlook clients with an Exchange ActiveSync profile and without an enrolled second factor that are members of tenants with a configured MFA Enrollment Policy were impacted. The pursuant investigation determined that a bug fix, applied in the 2019.10.2 weekly update, to address a gap in multi-factor enrollment during authentication, was the root cause. The fix was incorrectly scoped to include legacy Office 365 protocols. At approximately 10:44 AM PDT, Okta reverted the change in US Cell 4 and confirmed that issue was resolved. The change was then subsequently reverted in all production. At approximately 11:35 AM, service was fully restored for all customers in all cells. Additional testing and alerting to prevent and detect such issues will be implemented to prevent future occurrences. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y000000GpKxUAK Okta is currently experiencing an issue with Office 365 provisioning. We are actively investigating and will update this message with more information as soon as we have it. <br><br> Resolved: On Feb 7th at approximately 4:30PM PDT, Okta began receiving reports from customers in US Cell 4 who were experiencing errors while attempting to provision users to Office 365 or while modifying Office 365 configuration settings. User authentication was not impacted at any point. <br><br> The root cause was traced to an inability in some cases to read domain federation settings from Microsoft Office 365. This bug caused a failure to successfully provision users and save Office 365 app settings. Okta also determined that this issue was present in all cells, but only affected a subset of customers. <br><br> Once the root cause was identified, Okta deployed a fix starting at 4:49pm PDT on Feb 7. at approximately 5:30pm PDT, the fix was successfully rolled out to all production cells, and functionality was fully restored. <br><br> Additional monitoring to detect and mitigate this scenario has been rolled out for all environments. Testing will be augmented to prevent future occurrences. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C2A0000004CSnUAM Okta is currently investigating an issue with Provisioning Setup and IDP-Initiated Single Sign-On functionality for the following Office 365 Apps: Yammer, CRM and Teams. SP-Initiated Single-Sign-On is not affected. Please contact support if you are having difficulty setting up provisioning and we will assist with implementation of an applicable workaround as we investigate further. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y000000fxgDUAQ 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. RESOLVED: An issue impacting syslog accessibility in all Okta Cells has been identified and fixed. Service has been restored to normal. ROOT CAUSE ANALYSIS: On On July 11th, at approximately 10:47 AM PDT Okta detected System Logs access failures across all cells. Upon investigation, Okta determined that the issue was caused by an expired Certificate Revocation List (CRL), which had been updated in the certificate keystore repository, but had not been synced across System Logs storage infrastructure. This resulted in certificate validation failures when users attempted to access System Logs. At 11:06 AM PDT, Okta updated the CRL across all cells. Errors started clearing as the change was applied and caches were progressively refreshed. At approximately 11:28 AM PDT, all errors had been cleared. Okta is implementing additional monitoring and alerting to further enhance detection of similar CRL errors in the future. We are also implementing additional process changes and tooling to prevent similar CRL-related certificate validation errors in the future. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y000000fxWSUAY Okta is currently experiencing an issue with Cloud Desktop Single Sign-On when using Google Chrome, where attempting to sign-in results in an HTTP 400 response. <br><br>We have validated a fix and are in the process of deploying a hot fix to all cells to address this issue. <br><br>Cloud Desktop Single Sign-On is still available on Apple Safari and Internet Explorer.<br><br>Issue has been resolved in US Cell 4, US Cell 5, EMEA Cell 1, and US Cell 7. <br><br> Resolved:An issue impacting Cloud Desktop Single Sign-On for users of Google Chrome has been resolved. During the event, End-Users may have experienced HTTP 400 responses, when attempting to login using Google Chrome. Additional root cause information will be provided within 48 business hours. <br><br> Root Cause: On May 31st, at approximately 12:24 PM PDT Okta received reports from some customers receiving a '400 Bad Request' response while attempting to login with Agentless Desktop SSO using Chrome browsers. <br><br> Upon investigation, Okta determined that the issue impacted customers with either incorrect Chrome settings or network configuration (see https://help.okta.com/en/prod/Content/Topics/Directory/Configuring_Agentless_SSO.htm). Okta also determined that the issue had been exposed by the release of a software performance optimization which did not account for this possible browser mis-configuration; prior to the optimization, this mis-configuration would have resulted in users being redirected to the default login page. <br><br> Given the impact and poor user experience, starting on May 31st at 2:30 PM PDT, Okta deployed a change that reverted behavior to the pre-optimization one. The deployment completed to all cells at approximately 5:30PM PDT. <br><br> Okta is implementing additional testing and monitoring to detect this condition in the future. 2024-06-17T20:37:42.000Z https://www.salesforce.com/a9C1Y0000004E5RUAU Okta is currently experiencing an issue with Advanced Server Access. Administrators may have trouble accessing the dashboard, and users may experience errors with SSO or while attempting to authenticate to servers. We are actively investigating and will update this message with more information as soon as we have it. Resolved: An issue impacting Okta Advanced Server Access has been resolved. During the event, Administrators may have experienced errors accessing the ASA dashboard. Additionally, users may have experienced authentication errors. Okta applied several changes to mitigate the issue and continues to monitor and investigate. Additional root cause information will be provided within 48 business hours. Root Cause Analysis: On Saturday, November 23rd at approximately 1:05 PM PDT, Okta detected database resource contention within our Advanced Server Access production environment, resulting in timeout errors for users who were accessing the Advanced Server Access dashboard or were attempting to authenticate to servers. After investigating the issue, at approximately 3:30 PM PDT, Okta took actions to mitigate the resource contention issue by blocking customer API requests for adding groups to projects and synchronizing data to servers. Most Advanced Server Access functionality was restored through this action. Upon further investigation, Okta identified an additional inefficiency in our synchronous logic, and made a change to asynchronous background job processing. Following our investigation and mitigation actions, Okta re-enabled the API for synchronizing data to servers at approximately 6:47 PM PDT. Okta also re-enabled the API for adding groups to projects, fully restoring all services at this time. Okta's has implemented changes to mitigate the impact of similar issues in the future, and is continuing its full Root Cause Analysis of the incident,. We expect to be able to provide further details and future preventative actions by December 4, 2019. Additional RCA details will be posted here once this is investigation is complete. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000oLkeEAE Microsoft 365 Service reporting Azure authentication down per [status.office.com](http://status.office.com). Microsoft is actively investigating and we will update this message with more information as soon as we have it. Resolved: Microsoft has reported that Azure AD service is restored. All Okta Services related to Microsoft Office 365 and Azure are working as expected with the exception of some connections to Azure Active Directory Graph API for Okta Provisioning service which we expect to be slower to recover. We will continue to monitor residual effects for a limited number of customers. We are working with the service provider to investigate the root cause of this service disruption and will post the RCA to [status.okta.com](http://status.okta.com.com) within 48 hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000009whzEAA Our upstream provider, AWS, is currently experiencing an issue which is affecting AWS SAML Login. During this time, Okta end users may experience issues signing into AWS OIN app. (See AWS Status) [https://health.aws.amazon.com/health/status] for more details. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wkCJEAY Resolved: Investigation of the the LDAP connection service has been completed and service has been restored on all cells. Additional root cause information will be provided in 48 hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXDdEAO An issue impacting SMS MFA for AT&T US destinations in all cells has been resolved. Additional root cause information will be available within 5 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C2A000000PBhNUAW On February 15th, Okta experienced a feature disruption to Office 365 provisioning functionality starting at 12:58pm PST. Okta Engineering's investigation found errors being returned in response to Okta's connection requests to the Microsoft Online Provisioning API. These errors caused all Office 365 provisioning sync tasks to fail. An escalation was raised to Microsoft, who was already aware of the issue, and by 6:05pm the issue was resolved and the expected response codes were being returned. Impacted customers were then advised by Okta to retry any failed provisioning tasks as they would successfully complete. Diagnostic logging for Office 365 requests and responses is being enhanced to provide greater granularity and expedite troubleshooting for this type of issue in the future. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YziPEAS Out of an abundance of caution, an update was posted on November 25, 2022, at 10:18 am PST. However, following additional investigation, it was determined that a broad SMS delivery service degradation notice was not applicable. The SMS service as the 2FA method worked as designed. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YzhvEAC Okta continues to monitor the current issue with our partners regarding the SMS delivery delays using US-based phone numbers. Our monitoring shows recovery in delivery with MFA for customers that utilize SMS. The failover mechanism has mitigated the impact. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXHQEA4 At 7:17 PM PDT, Okta completed the hotfix deployment to all cells. Customers have confirmed the issue impacting end-user authentications via VPN using an IE-embedded browser has been resolved. Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wkBBEAY Resolved: An issue with Microsoft O365 Push Groups failing after Production Release version 2022.02.1 in all production cells has been resolved. Additional root cause information will be provided by Wednesday 2/23. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000Yzj3EAC An issue impacting Advanced Server Access for all end users has been resolved. Advanced Server Access team restarted the service and it helped restore database connectivity. The service interruption started at 11:52AM PST and service was fully restored at 12:28PM PST. Additional root cause information will be available within 2 Business days. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000008PggUAE Jobs were reported to be delayed across all Okta Cells, except US Cell 5. Okta has fixed the root cause of the issue related to the jobs being delayed. All impacted services are now restored and fully functional. Remaining job backlogs are either completely caught up, or will return to normal operation in due course.  A Root Cause Analysis (RCA) will be made available within 2 business days.  ============================= Resolved - Jobs are delayed across all Okta Cells, except US Cell 5. Okta has identified a solution to resolve the use and is being validated in the Okta preview Cell. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000008Ph5UAE Resolved: An issue resulting in intermittent Azure Active Directory Graph API provisioning errors has been resolved. Root Cause Analysis (RCA) will be made available within 2 business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000008Pa9UAE Okta is currently experiencing an issue with the service. Okta is currently investigating an issue impacting Microsoft applications in all cells where SSO & provisioning are experiencing failures. Okta is working with the vendor to restore service. RESOLVED: Issues impacting O365 Single Sign-On and 0365 Provisioning have been resolved. Okta and Microsoft have resolved the remaining intermittent provisioning issues. Okta will continue to monitor the situation carefully. For customers using AAD graph API, residual errors may be observed when Okta tries to connect to Microsoft. To resolve these issues, administrators can go to provisioning tab for the application instances, click edit, test credential and save the app instances to resolve the issue. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000008PZGUA2 An issue with the Helpdesk Admin Role is preventing Admins from resetting password via temporary password. Reset password link is still functioning as a viable option. All cells except OK4 and OK6 are affected.We are actively investigating and will update this message with more information as soon as we have it. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000004EI1UAM Okta observed an issue with the new 5.0.2 version of Okta Verify for iOS. Some users were unable to verify their identity by acknowledging the push notification sent to their iPhone. They can work around this issue by entering the verification code displayed on Okta Verify. Resolved: Okta has released a fix to Okta Verify (OV version 5.0.5) for users who updated to 5.0.2 and are experiencing push notifications issues. Root Cause: On April 15th at approximately 2pm PDT, Okta began receiving reports that some users could not complete push-based Okta Verify MFA flows on iOS devices. Okta determined that this issue was unique to version 5.0.2 of Okta Verify for iOS which had begun a phased rollout earlier that same day. At 2:20pm PDT Okta suspended the rollout of Okta Verify 5.0.2 for iOS and continued to investigate the problem. Customers were advised to work around the issue by entering the verification code displayed on Okta Verify. After further investigation, Okta determined that push verify on Okta Verify 5.0.2 was unable to complete verification for users who had last enrolled with Okta Verify on their device prior to Okta Verify version 4.4. This was due to an incorrect handling of legacy encryption keys that were used in previous Okta Verify versions. Because of the complexity of the issue, Okta expedited a temporary build that would rollback the functionality for users affected as the full fix was worked on to support all upgrade paths. The build was approved and published at 11:00am PST on April 16th. Okta worked on a comprehensive fix, leveraging heuristics to determine the encryption method of the stored keys in order to resolve the issue for all users. This fix was submitted to the app store and expedited as Okta Verify 5.0.7 at 5:20pm PDT on April 16th, the build was approved and published at 9:20am PDT on April 17th. Okta is expanding migration testing scenarios across more versions to prevent future occurrences as well as incorporating additional monitoring to detect similar issues more quickly in the future. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000008PeuUAE While iOS 12 is not officially supported, Okta has identified an issue with Okta Verify version 6.0.1 that is impacting iOS 12 users. We are working to address this issue and will provide an update at 10AM PST. There is no impact to Okta Verify on Android. ==== Resolved: For iOS12 users experiencing crashing on Okta Verify 6.0.1, users may now downgrade to a previously functioning version by fully uninstalling the app and installing version 5.9.0. Detailed instructions for users can be found below: If you are on iOS 12 and Okta Verify 6.0.1, and it crashes regularly, there are two options to restore service. If you do not urgently need to use Okta Verify: 1) Wait to update to the Okta Verify 6.0.4 release. 2) This release should be ready as soon as Apple approves it (typically 1-3 business days). If you urgently need to use Okta Verify (may require support of your admin): 1) Uninstall Okta Verify 6.0.1. 2) Install the Okta Verify app again from the App Store. This time you should be able to install the 5.9.0 version of Okta Verify. 3) If you cannot get into the Okta end-user dashboard to re-enroll Okta Verify, reach out to your administrator and ask them to reset your Okta Verify MFA. 4) Once your admin resets MFA, you will be able to re-enroll from the Okta Verify 5.9.0 you installed from the App Store. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YzhREAS The fix for the issue impacting Multifactor Authentication has been deployed in all Production cells. Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000004E4EUAU Okta customers in all cells that leverage Zoom’s integration for provisioning are experiencing errors while updating users in Zoom. We are actively working with Zoom to identify the root cause and identify a solution. Resolved: An issue impacting user provisioning updates to the Zoom application within Okta has been resolved. During the event, user updates to the Zoom application may have encountered errors if the provisioned user already existed within Zoom. Okta worked with Zoom to identify the root cause of the issue and applied a hot-fix to all production cells to mitigate the provisioning errors while Zoom worked to deploy a permanent fix. Additional root cause information will be provided within 48 business hours. Root Cause Analysis: On Nov 19th at approximately 8:53AM PDT, customers reported Zoom provisioning errors when updating user’s profiles. Upon investigation, Okta determined that the issue was caused by a change in the behavior of an existing Zoom Provisioning API which was introduced on November 17. This change was implemented by Zoom to enable support for changing user's email addresses through the Profile Update request. The change inadvertently caused profile updates to fail, whenever the email has not been changed. On Nov 19th at approximately 8:17 PM PDT Okta released a work around to address the issue. This update was deployed to all production cells and service was fully restored. Okta is working closely with Zoom for a fix, as well as, understanding and mitigating the re-occurrence for this type of failure 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C0Z0000008PW7UAM We observed some delays or failures in the delivery of outbound SMS to the AT&T network in the US. SMS sent to other networks was unaffected. Most end users were able to succeed with a retry. We actively worked with our providers to resolve the issue and will provide an update when we have further information. Okta recommended affected AT&T mobile customers use an alternate second factor to work around the issue. Resolved: Okta received reports of delays and failures in the delivery of SMS for multi-factor authentication. Upon further investigation, it was determined that the issue was caused by an on-going AT&T cellular network incident. Okta worked with its service providers to raise the issue and worked with customers to workaround the the issue until service was fully restored by AT&T. Users who were not on the AT&T cellular network or that leveraged other authentication factors were not affected throughout the incident. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C0Z0000008PU1UAM Resolved: An issue impacting authentication and system responsiveness for a subset of end-users and administrators accessing Microsoft Office 365 has subsided. Further investigation of the issue found the errors were correlated with a service degradation reported by Microsoft. Microsoft reported this is related to mitigation activities form yesterday's service disruption (MO147606): "We identified and reverted an update that was causing multiple services to be throttled. We're conducting tests to ensure that impact has been resolved. Further updates can be found in the admin portal under EX147785 and MO147789." 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C0Z0000008PTrUAM Resolved: An issue impacting authentication and system responsiveness for a subset of end-users and administrators accessing Microsoft Office 365 has subsided. Further investigation of the issue found the errors were correlated with a service degradation reported by Microsoft (Incident MO147606). Further information is available from Microsoft via https://status.office365.com. ------------------------------- Root Cause Analysis: On Sept 4th, 2018, at approximately 6:00am PDT, Okta began receiving reports that end-users were experiencing delays and errors while attempting to authenticate to Office 365 and related services hosted by Microsoft. Upon further investigation the service disruption began at approximately 2:29am PDT and appeared to be localized to customers with Office 365 and related resources hosted within Microsoft’s South-Central US datacenter. The service disruption was reported as fully resolved by Microsoft on Sept 7th at 1:40am PDT. Throughout the duration of the incident, Okta-provided services continued to function normally. Microsoft reports a severe weather event, including lightning strikes, occurred near one of the South-Central US datacenters. This resulted in a power voltage increase which impacted cooling systems. Automated datacenter procedures designed to ensure data and hardware integrity went into effect and critical hardware entered a structured power down process. Please refer to your [Office 365 Service Health](https://portal.office.com/adminportal/home#/servicehealth) dashboard for further details regarding this incident and mitigating steps. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y0000004DyLUAU We are aware of slow dashboard load times on Google Chrome version 77. We are investigating this issue and will update this message with more information as soon as we have it. ========================== Resolved: The issue with Google Chrome version 77 (on both desktop and Android) which was due to a change introduced in Google Chrome version 77 is now resolved on all Cells. Additional root cause information will be provided within 48 business hours. ========================== Root Cause Analysis: On Sept 30th, at approximately 3:39PM PDT, customers reported experiencing longer than expected load times for application logos in the Okta end-user dashboard and catalog. Upon investigation, Okta determined users in all cells experienced the longer load times after updating their Chrome browser to version 77.0.3865.75 (Official Build) (64-bit). Users of browsers other than Chrome, and users of Chrome earlier than version 77, were not impacted. Okta discovered that Chrome version 77 caused a performance regression with some HTML Canvas operations when the hardware acceleration setting was available and enabled. This behavior is also discussed in the Chromium bug forum as Issue 1001845. At approximately 8:40PM PDT on Sept 30th, Okta started the phased deployment of a workaround, per-cell basis, which was completed on all cells by 10/1/2019 at 6:40 PM PDT. During the incident, users were advised to workaround the issue by disabling Hardware Acceleration. This workaround is no longer necessary and Hardware Acceleration in Chrome can be re-enabled. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wkFIEAY Resolved: Okta observed issues with the deliverability of SMS messages to Google Voice phone numbers from third-party providers. End users enrolled in SMS MFA with a Google Voice number may not receive SMS MFA codes. For those users with a secondary MFA factor enrolled, a backup factor can be used. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C2A000000KzXkUAK On February 1st, between 7:57am - 9:17am PST, Okta observed a noticeable increase in the volume of SMS errors returned by one of our SMS providers which impacted all cells. Okta automatically retries all failed or slow SMS requests with an alternate SMS provider. As a result of this issue, users leveraging SMS for Multifactor Authentication or Account Recovery may have experienced a slower than usual SMS delivery time. Users relying on voice based second factor authentication, an EA feature, might have experienced delivery failures during the incident. All other authentication factors, such as Okta Verify, Duo, Yubikey, Google Authenticator, or Security Question were not affected. <br><br> Review the root cause analysis [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-SMS-Voice-Factor-Feature-Degradation). 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000009wj7EAA Atlassian products experienced an issue affecting account login. During this time, Okta end users may be unable to sign into Atlassian products such as Jira and Confluence. [See Atlassian Status](https://status.atlassian.com/) Additional root cause information will be available within 5 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000Yzh7EAC We rolled out and published a new release version 7.9.2 for Okta Verify Application to fix the issue impacting the Okta Verify Application version 7.9.1 for Android devices. The end users will be able to download version 7.9.2 as the Google Play store makes it available. Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C1Y000000fxh6UAA An issue affecting GSuite's OAuth endpoints is preventing customers who use GSuite for authentication from accessing ASA's web interface or enrolled servers. Google has opened an incident to track this: https://status.cloud.google.com/incident/developers-console/19008 ============================ Resolved: On Aug 19th at approximately 12:30PM PDT, Okta noted an issue affecting GSuite's OAuth 2.0 endpoints preventing customers who use GSuite for authentication from accessing ASA's web interface or enrolled servers, Google imports, and SSO login to GSuite apps. Google is reporting the issue is resolved for OAuth 2.0. Okta will continue to track the status of this incident and explore possible workarounds. ============================ Root Cause Analysis: On August 19th, at approximately 10:50 AM PDT Okta detected an increased number of failed Google OAuth 2.0 authentication requests and import failures. In addition to that, customers using GSuite as their main IdP could not authenticate via Advanced Server Access (ASA) to access their infrastructure. Upon investigation, Okta determined that Google had experienced a [global outage](https://status.cloud.google.com/incident/developers-console/19008) of their OAuth 2.0 endpoints. This prevented external services (ASA, Okta) from authenticating user sessions against Google as an IdP, and no workarounds were provided. At approximately 12:30 PM PDT the issue with Google OAuth 2.0 endpoints was fully resolved and service was restored. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000000oGBEAY Okta has observed disruptions in SMS deliverability to Canada in all cells. Okta continues to monitor the current situation with our telephony services regarding the SMS OTP delivery disruptions. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wk4KEAQ Okta have experienced a SAML Single Sign On issue with the AWS app. We have resolved the issue across all cells. Additional root cause information will be provided within 48 business hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YzjSEAS A connection issue to Okta services impacting all cells, stemming from an infrastructure provider was first observed at approximately 1:03 PM Pacific time. The issue has been resolved as of 2:16 PM Pacific time. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wk2nEAA Beginning at approximately 5:27AM PDT, customers leveraging SMS as a factor may have experienced intermittent delivery delays to U.S based numbers upon first attempt. At 7:22am Okta promoted our secondary SMS delivery provider to function as our primary provider. An RCA will be provided following full investigation. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000g0WqEAI Okta is currently experiencing an issue with O365 user provisioning. We are actively investigating and will update this message with more information as soon as we have it. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C0Z0000004EA5UAM Okta received reports from customers who were unable to reach our service. This appeared to be related to a broader Internet Service Provider connectivity issue with Comcast, as reported extensively on Twitter. We actively monitored the situation and confirmed all services were operational. --------- Resolved: On June 29th, beginning at 9:43am, Okta began receiving reports from some customers who were unable to access Okta. Upon immediate investigation, it was determined that Okta's services were operating normally. The root cause was a network disruption, in some geographic locations, with a major internet provider. Given the breadth of the 3rd party internet disruption, Okta proactively posted to https://trust.okta.com to inform customers that we are aware of the situation and that they may be impacted. Okta is continuing to closely monitor and ensure that Okta's services remain unaffected. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000000oG1EAI At 6:30AM PDT on November 2, 2023, our engineering team became aware of the Workday application SSO and Provisioning issue. Customers may experience issues accessing the Workday application via the Okta End-user Dashboard. We will resolve this incident once we have received confirmation the issue has been resolved from Workday. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wkAXEAY Resolved: An issue impacting SMS as a factor with third-party SMS providers to US-based phone numbers in all cells was addressed. Additional root cause information will be provided in 48 hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wk8HEAQ Okta has identified the issue with the NetSuite Import and successfully deployed a fix to resolve it. Additional root cause information will be provided within 48 business hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wk8CEAQ Okta has recovered the network connectivity issues to US West 2 and the issue has been resolved. Additional root cause information will be provided within 48 business hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YzhlEAC An issue impacting Okta email delivery to Yahoo and Microsoft provided emails has been addressed. Our monitoring shows a return to normal conditions with Okta email deliverability. Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXFtEAO An issue impacting SMS MFA in all cells has been resolved. Additional root cause information will be available within 5 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXGcEAO At 3:12 PDT on June 14th Okta became aware of a connectivity issue affecting customers on multiple cells in the Okta Workforce Identity Cloud environment resulting in loss of access to syslog, logs api, delegated authentication flows, imports, and LDAP interface requests. Engineering took the necessary steps to restore connectivity to all cells. The service was restored at 3:59 PDT Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wk3CEAQ Okta is currently investigating increased error rates in US Cells 5, 7, 12, and 14, and Preview 3. We will update this message with more information as soon as we have it. Resolved: We have mitigated all observed errors and issues in the US-West region affecting US cells 5, 7, 12, 14, EU 9, and Preview 3. Error rates have completely subsided and the service has returned to normal status, queued events are progressing and should complete in the next few hours. Additional root cause information will provided within 2 business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXDnEAO An issue impacting SMS MFA to US Cellular Network accounts in the United States has been resolved. Additional root cause information will be available within 5 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000YzkkEAC Okta became aware of IdP-initiated login (login via Okta Dashboard) in Microsoft O365 app issue affecting customers in all cells. During this time customers may receive Http 404 errors upon IdP-initiated logins. While Okta works to resolve this, customers are encouraged to leverage SP-initiated login (login via Microsoft Online: https://www.office.com) which will function as expected. We are investigating the incident and taking corrective actions. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C2A000000bmK1UAI An issue impacting IDP-Initiated Office 365 Office Portal SSO for a subset of end-users in all cells was investigated with Microsoft. Customers may have seen page load failures for portal.microsoftonline.com. As a workaround, customers were able to utilize any of the app-specific chiclets to access O365, then navigate to the O365 Portal from that location. Resolved: On March 30 at 4:22AM PDT, Okta experienced an issue impacting IDP-Initiated Office 365 Portal SSO for a subset of end-users, specifically those with IPV4 addresses. Users attempting to use the Office 365 Portal chiclet during the incident experienced page load failures. SP-Initiated SSO to the Office 365 Portal, as well as all other Okta Microsoft chiclets, continued to work normally throughout the incident. After it was determined that the issue appeared to be on the application vendor side, Okta immediately reported the matter and worked with Microsoft on potential workarounds and resolution. By 9:45 AM PDT, the problem had been resolved. Root cause analysis and next steps are provided in Microsoft incident MO133118 via the Microsoft Admin Center. Okta will be enhancing monitoring to detect similar Office 365 Portal issues faster in the future to be able to report them Microsoft as early as possible. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000Yzi5EAC On November 15, Okta provided a self-service KB guide to fully resolve the authentication issues for Microsoft Office 365 applications. This is the final fix for this issue. The guide can be found in the knowledge article at support.okta.com (https://support.okta.com/help/s/article/Okta-federation-issue-workaround?language=en_US). These instructions have not changed since their release on November 15 and no additional action or changes are required following this issue We request that customers needing assistance implementing the resolution contact Okta Support. Okta will continue to partner for any identified impacted customers and to support them resolving their Microsoft Office 365 application configuration. Additional root cause information will be available within 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000TXHaEAO At 5:47AM PDT the engineering team confirmed the errors had subsided. The issue impacting users not being able SSO to AWS CLI Application when using MFA in all Cells has been resolved. Additional root cause information will be available within 5 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000009wiOEAQ An issue impacting SMS MFA for US customers in all cells has been resolved. Our monitoring shows a return to normal conditions with the SMS OTP delivery delays. Okta continues to monitor the situation with our telephony services regarding the SMS OTP activity. Additional root cause information will be available within 5 Business days. We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000000oGpEAI 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. We will resolve this incident once we have received confirmation the issue has been resolved from Workday. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000wkAIEAY An issue impacting SMS as a factor for US users was initially closed as third-party SMS providers had dismissed the status of their incidents. Additional information is in https://status.okta.com/#incident/a9C4z000000wkAXEAY 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z000000oLmVEAU Resolved: The issue involving the RingCentral OIN Application has been resolved. We are continuing to monitor. An RCA will be provided within 48 business hours. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000012OTZEA2 Resolved: An issue impacting network connectivity in US Cell-6, US Cell-10 and US Cell-11 was addressed. Okta continues to monitor the slowness of System Log service delay in US Cell-6. Additional root cause information will be provided in 2 Business days. 2024-06-17T18:24:36.000Z https://www.salesforce.com/a9C4z0000012OTjEAM Resolved: An issue impacting Okta Workflows in US Cell-5, APAC Cell-8, and US Cell-10 was addressed. Additional root cause information will be provided within 2 Business days. 2024-05-31T14:16:22.000Z https://www.salesforce.com/a9C4z000000TXI9EAO 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. 2024-05-15T01:56:38.000Z https://www.salesforce.com/a9C4z000001BZVpEAO 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. 2024-05-09T00:32:34.000Z https://www.salesforce.com/a9C4z000000TXI4EAO 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. 2024-04-12T22:34:29.000Z https://www.salesforce.com/a9C4z000000TXHzEAO 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. Okta 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. 2024-04-12T22:28:44.000Z https://www.salesforce.com/a9C4z000000L1d1EAC 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). 2024-04-10T06:29:23.000Z https://www.salesforce.com/a9C4z000000TXHuEAO 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. Our engineering team is performing corrective actions to mitigate the issues related to this degradation. We'll provide an update in 30 minutes or sooner if additional information becomes available. 2024-04-03T22:57:47.000Z https://www.salesforce.com/a9C4z0000000oGuEAI 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. Additional root cause information will be available within 5 Business days. 2024-03-28T20:52:58.000Z https://www.salesforce.com/a9C4z000000TXHpEAO An issue impacting the degradation of service in US-Cell 1 has been addressed. Additional root cause information will be available within 5 Business days. 2024-03-26T21:46:44.000Z https://www.salesforce.com/a9C4z0000000oGkEAI 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. Additional root cause information will be available within 5 Business days. 2024-03-26T20:37:36.000Z https://www.salesforce.com/a9C4z0000000oGfEAI 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. Our engineering team continues to work on Scheduled flow latency and will work with impacted customers. For more information on the differences between flows, please visit: https://help.okta.com/wf/en-us/content/topics/workflows/learn/about-low-latency.htm Additional root cause information will be available within 5 Business days. 2024-03-13T23:10:14.000Z https://www.salesforce.com/a9C4z000000TXHfEAO 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. We'll provide an update in 30 minutes or sooner if additional information becomes available. 2023-12-21T19:01:47.000Z https://www.salesforce.com/a9C4z0000000oGGEAY An issue impacting accessing Okta service in US-Cell 2 has been addressed. Our engineering team has performed corrective actions to mitigate the incident from reoccurring. From 8:18 AM PST through 8:34 AM PST customers may have experienced issues accessing the Okta service or may have received an HTTP 504 (Gateway Timeout) status code response from Okta. Additional root cause information will be available within 5 Business days. 2023-11-22T21:09:21.000Z https://www.salesforce.com/a9C4z0000000oG6EAI The workflow execution latency issues for a subset of Okta US Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor the FL1 service performance. Additional root cause information will be available within 5 Business days. 2023-11-09T01:58:51.000Z https://www.salesforce.com/a9C4z0000000oFwEAI Our engineering team became aware of an increased in error rates in US-Cell 7. The following impact timelines associated with the response status code are stated below. Customers who may have experienced the event were impacted for approximately 2 minutes or less. 7:39AM - 7:41AM PDT - HTTP 504 (Gateway Timeout) Our engineering team has performed corrective actions and continues to monitor the health of US-Cell 7. 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?language=en_US). 2023-11-07T20:34:53.000Z https://www.salesforce.com/a9C4z0000000oFrEAI An issue impacting accessing Okta service in US-Cell 7 has been addressed. Our engineering team has performed corrective actions to mitigate the incident from reoccurring. 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?language=en_US). 2023-11-02T22:11:37.000Z https://www.salesforce.com/a9C4z000000TXHVEA4 The issue impacting the User and Group Search function for customers on US-Cell 14 cell of the Production environment has been addressed. Our monitoring shows a return to normal conditions for the past 6 hours. 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). 2023-10-19T22:42:30.000Z https://www.salesforce.com/a9C4z0000009wktEAA From 00:35 PDT until 03:35 PDT on October 7, 2023, Okta’s Engineering team observed internet connectivity issues affecting some US customers in all commercial cells. During this window, customers in these cells may have experienced an inability to reach the Okta platform. The issue is now resolved and all systems are operating normally. 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). 2023-10-19T22:39:44.000Z https://www.salesforce.com/a9C4z0000009wkeEAA From 05:17 PDT until 05:42 PDT on October 12, 2023, Okta’s Engineering team observed Internet connectivity issues affecting some US customers in all commercial cells. During this window, customers in these cells may have experienced an inability to reach the Okta platform. The issue is now resolved and all systems are operating normally. 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). 2023-10-04T18:45:57.000Z https://www.salesforce.com/a9C4z0000009wjlEAA At 4:30 PM PDT on Sep 27, 2023, the issue impacting the Flow History component affecting customers on US Cell 1, 2, 3, 4, 6, 7, and 11 has been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor the Flow History performance. Additional root cause information will be available within 5 Business days. 2023-09-27T06:41:56.000Z https://www.salesforce.com/a9C4z0000009wjgEAA At 11:30 PM PDT on Sep 26, 2023, the issue impacting the Flow History component affecting customers on US Cell 1, 2, 3, 4, 6, 7, and 11 has been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor the Flow History performance. 2023-09-14T03:04:50.000Z https://www.salesforce.com/a9C4z0000009wiiEAA At approximately 5:26 AM PDT on Sep 7, 2023, our engineering team became aware of a service disruption affecting customers in EMEA Cell 1. During this time customers may experience general slowness, and timeouts, and may receive an HTTP 500 response code. Our engineering team performed corrective actions to address the issue in EMEA Cell 1. At around 5:50 AM PDT, our monitoring shows a return to normal conditions. Additional root cause information will be available within 5 Business days. 2023-08-17T17:38:42.000Z https://www.salesforce.com/a9C4z0000009whVEAQ At 7:15 AM PDT on August 15, 2023. Okta became aware of increased traffic in the US Cell 1, resulting in concurrency rate limits to the cell. During this time, customers may have received HTTP 429 "Too Many Requests" and HTTP 504 "Gateway Timeout" response codes. Our monitoring shows a return to normal since 7:30 AM PDT. 2023-08-16T18:32:19.000Z https://www.salesforce.com/a9C4z0000009whLEAQ At 1:08 PM PDT on August 11, 2023. Okta became aware of increased traffic in the US Cell 1, resulting in concurrency rate limits to the cell. During this time, customers may have received HTTP 429 "Too Many Requests" and HTTP 504 "Gateway Timeout" response codes. Our monitoring shows a return to normal since 2:08 PM PDT. Additional root cause information will be available within 2 Business days. 2023-08-04T18:42:32.000Z https://www.salesforce.com/a9C4z0000009wgwEAA At 6:15 PM PDT, the issue impacting the Workflows History component affecting customers on US Cells 1, 2, 3, 4, 6, 7, and 11 has been addressed. Our monitoring shows a return to normal conditions and we will continue to monitor the Workflows History performance. Additional root cause information will be available within 2 Business days. 2023-06-30T17:40:59.000Z https://www.salesforce.com/a9C4z000000TXGwEAO At 8:23 AM pacific on June 30th 2023, OK6 experienced issues and went into Read Only mode at 8:27 AM pacific. Authentication, SSO and other read operations continued to work while in Read Only mode. Okta recovered write operations by 8:41 AM pacific. Okta Engineering is monitoring and performing recovery of the cell to mitigate the issue. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. 2023-06-15T21:04:34.000Z https://www.salesforce.com/a9C4z000000Yzp1EAC The Okta team became aware of a recurrence of a previous issue affecting customers accessing Okta Dashboard in Okta Preview Cell-1 (OP1). Our engineering team reapplied the changes at 10:01 PM PDT which resolved the issue. Engineering has validated the service is restored and is taking mitigation steps to ensure the issue will not happen again. Additional root cause information will be available within 2 Business days. 2023-06-09T17:20:48.000Z https://www.salesforce.com/a9C4z000000YzowEAC At 1:28PM on June, 6th, 2023 PDT, Okta became aware of an issue impacting customers on US-Cell 2. During this time US-Cell 2 went into Read Only mode as a result customers may have experienced HTTP 50x response codes, Delegated authentication issues and latencies in accessing Okta. Our engineering took necessary steps to restore the service. The service was restored at 1:39PM PDT. Additional root cause information will be available within 2 Business days. 2023-06-08T23:33:06.000Z https://www.salesforce.com/a9C4z000000TXGSEA4 An issue impacting accessing Okta Dashboard for end users in Okta Preview Cell-1 has been resolved. Additional root cause information will be available within 2 Business days. 2023-05-23T16:58:38.000Z https://www.salesforce.com/a9C4z000000TXDiEAO At 2:23 PM PDT on May 18, 2023 PDT. Okta became aware of an increase in traffic in the Preview cell (OP1), resulting in concurrency rate limits to the cell. During this time, customers may have received HTTP 429 response code “Too Many Requests.” Our monitoring shows a return to normal since 2:57 PM PDT. Additional root cause information will be available within 2 Business days. 2023-05-16T19:10:53.000Z https://www.salesforce.com/a9C4z000000TXDEEA4 Okta is experiencing service degradation in Workflows FL1. Workflows may experience slowness, and some functionality may be unavailable. We’ll provide an update in 30 minutes or sooner if additional information becomes available. 2023-05-15T19:43:47.000Z https://www.salesforce.com/a9C4z000000TXD9EAO 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. The US-Cell 2 went into Read Only mode for 20 mins from 6:00AM PDT - 6:21AM PDT due to an issue with one of our databases. Okta performed emergency maintenance to mitigate the situation. As of 6:23 am PDT the service returned to normal operation. Additional root cause information will be available within 2 Business days. 2023-04-13T21:13:52.000Z https://www.salesforce.com/a9C4z000000TXBDEA4 An issue impacting the Workflows service in EU cells has been mitigated. The Workflows team continues to monitor the Workflows service. Additional root cause information will be available within 2 Business days. 2023-03-12T18:07:02.000Z https://www.salesforce.com/a9C4z000000YznoEAC At 8:55 AM PST on March 12, 2023, Okta observed that some request patterns returned HTTP 403 Forbidden in US East Cells 1, 2, 3 and 4. This issue has been resolved. The service was fully restored at 9:55 AM PST on March 12, 2023. Additional root cause information will be available within 5 Business days. 2023-03-08T03:22:59.000Z https://www.salesforce.com/a9C4z000000YznUEAS At 3:39 AM PST on March 3, 2023, Our operations team became aware of replication errors causing Workflows issues impacting historical data within flow execution on EU Cell-1 and 2. During this time Workflows may run with unsynchronized data and admin may see errors upon running a subset of Workflows. We are working to bridge the replication gap and take corrective actions. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. 2023-02-13T19:47:03.000Z https://www.salesforce.com/a9C4z000000YzlJEAS At 10:10 AM PST on February 2, 2023, Okta became aware that Directories (Active Directory and LDAP) Agent connectivity issues affecting Directory Agent’s health. This issue has been resolved. Okta took corrective action to resolve the service interruption. The service was fully restored at 10:51 AM PST. Additional root cause information will be available within 5 Business days. 2023-02-10T20:40:45.000Z https://www.salesforce.com/a9C4z000000YzlOEAS At 8:59 PM PST February 1, 2023, Okta acknowledges that Custom Domain-configured tenants experienced issues with their login page portal. This issue has been resolved. Okta took corrective action to resolve the service interruption. The service was fully restored at 11:15 AM PST on February 2, 2023. Additional root cause information will be available within 5 Business days. 2023-02-08T20:46:59.000Z https://www.salesforce.com/a9C4z000000YzlTEAS At 10:10 AM PST February 3, 2023, Okta observed that some request patterns returned HTTP 403 Forbidden in US East Cells 1, 2, 3 and 4. This issue has been resolved. The service was fully restored at 10:39 AM PST February 3, 2023. 2023-02-07T08:48:45.000Z https://www.salesforce.com/a9C4z000000YzlEEAS At 6:08 AM PST on February 2, 2023, Okta became aware of network connectivity issues affecting customers in US Cell7. During this time, customers may have received Http 500 errors, and Directory and IWA agents may have experienced intermittent connections. The service was fully restored at 6:27AM PST. 2022-10-27T00:19:03.000Z https://www.salesforce.com/a9C4z000000YzhMEAS Okta continues to monitor an issue that impacted US Cell-3 connectivity. Our monitoring shows a return to normal conditions. Additional root cause information will be available within 5 Business days in customer support. 2022-08-31T13:57:05.000Z https://www.salesforce.com/a9C4z0000012OU8EAM Resolved: An issue impacting authentication for all newly created users in US Cell-6 has been addressed. 2022-08-15T15:43:06.000Z https://www.salesforce.com/a9C4z0000012OU3EAM Resolved: Okta noticed a small subset of customers reporting an intermittent network connectivity issue with their Active Directory Agents in US Cell-1, Cell-3, US Cell-6, US Cell-7, US Cell-11, US Cell-12 and US Cell-14. We've identified a workaround on the customer side to resolve the network issue. Additional root cause information will be provided in 2 Business days. 2022-03-04T18:11:39.000Z https://www.salesforce.com/a9C1Y0000004EBeUAM Okta is currently experiencing an issue with the service in Okta Preview Cell 1, US Cell 6 and US Cell 7. The user import job is delayed. We are actively investigating and will update this message with more information as soon as we have it. Resolved: Okta has addressed the delayed user import jobs issue on Okta Preview 1, US Cell 6, and US Cell 7. We will continue to monitor and additional root cause information will be provided within 48 hours. Root Cause Analysis:On February 25th at approximately ‪1:05pm PST, Okta’s monitoring provided alerts that some import user jobs on Okta Preview 1, US Cell 6, and US Cell 7 were experiencing longer than normal wait times. Upon investigation, Okta determined that a new feature, “Schedule User Imports”, which allows imports to be scheduled for specific times was enabled for customers as part of the 2020.02.0 Monthly Production release*.* As part of release, existing scheduled interval imports were ported to the new day and time based feature which inadvertently caused a significant number of jobs to be run at a higher frequency. The increased volume of jobs resulted in increased wait times on some servers. At approximately ‪2:45pm PST, Okta began to roll back the feature and terminate non-admin initiated jobs that were scheduled to execute on the impacted job servers. Jobs that were terminated would get triggered again on the next scheduled import. By ‪3:15pm PST, normal service was restored. Okta is re-evaluating design approaches to provide enhanced import scheduling capability, while ensuring reliability and performance at scale. Okta is also investigating enhancements to the alerting mechanism to improve diagnosis for this type of alert. 2022-03-04T18:11:39.000Z https://www.salesforce.com/a9C4z000000wk5cEAA Okta is experiencing an issue where admins may be experiencing errors in utilizing Workflow designer Engineering is currently investigating the issue. We will provide an update within the next 30 minutes. 2022-03-04T18:11:15.000Z https://www.salesforce.com/a9C0Z000000TNfAUAW Resolved: Okta experienced a service degradation in US Cell 6 between 7:03pm and 7:45pm PDT due to a hardware failure and failover to secondary database infrastructure. Administrative functions like user creation, modification, and deletion may have experienced a period of [Read-Only mode] (https://support.okta.com/help/Documentation/Knowledge_Article/Read-only-Mode) during this time as corrective actions were taken. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-05062018). 2022-03-04T18:11:15.000Z https://www.salesforce.com/a9C2A0000004CSTUA2 Okta is currently experiencing an issue in US Cell 6. Administrators will not be able to see up to date user / group information within their Okta tenant. No authentication impact for existing users. Our TechOps and Engineering teams are actively investigating this issue. 2022-03-04T18:10:22.000Z https://www.salesforce.com/a9C2A000000Kz15UAC Okta experienced a service disruption in US Cell 4, between 12:34pm - 12:56pm PST following a temporary surge in the volume of requests and failure to correctly redistribute load. The increase in request volume was traced to an inefficient legacy API endpoint. Requests initiated by end users, excluding O365, and API integrations would have experienced intermittent 500 error responses. The mean error rate was 4% and peaked at 7% at approximately 12:50pm PST. The issue was resolved by blocking the legacy API endpoint traffic, and subsequently a code fix has been deployed for the problematic endpoint. Additional investigation is in progress to ensure proper load redistribution going forward. <br><br> Review the root cause analysis [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-11-06-2017). 2022-03-04T18:10:22.000Z https://www.salesforce.com/a9C1Y0000004E7hUAE Okta had detected an issue causing increased error rates and response times for requests to OK4. The incident has been resolved. We implemented mitigating steps to return the service to normal as quickly as possible. Resolved: An issue causing increased errors and response times for end-users and administrators in OK4 was resolved. During this event, End-Users and Admins may have encountered errors. Additional root cause information will provided within 48 hours. Root Cause Analysis: Full RCA details for this event can be found [here](https://status.okta.com/#incident/a9C1Y0000004E7hUAE). 2022-03-04T18:09:25.000Z https://www.salesforce.com/a9C2A000000Kz0WUAS Okta experienced a service disruption between 6:00am - 6:18am PDT following a hardware failure impacting a read replica database in US Cell 2 that was being used to shed load off of the primary. During this window, system response times increased and a subset of US Cell 2 requests that queried this database encountered timeouts or failures. The error rates in US Cell 2 averaged around 4% and peaked just below 10% for one minute at 6:15am. These errors intermittently caused the Okta home page to load incompletely and in some cases SSO to timeout for SWA apps when clicked by an end user. There was no impact to customers accessing Okta via APIs, or to end users signing into O365 or other SAML apps. Configuration changes are being implemented to prevent similar app request failures following this type of DB failure. <br><br> Review the root cause analysis [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-10-25-2017). 2022-03-04T18:09:25.000Z https://www.salesforce.com/a9C0Z000000TNeqUAG Resolved: On April 24th, at 7:53am PDT, Okta experienced a broad service disruption to US Cell 2. End users in US Cell 2 attempting to reach Okta received HTTP 500 errors, and customer integrations attempting to reach Okta API endpoints in US Cell 2 encountered elevated response times and errors. Operational mitigation steps commenced immediately at 7:53am. The greatest frequency of errors was a 14 minute period between 7:53am and 8:07am. The success rate began to gradually improve from 8:07am, and by 8:25am approximately 80% of requests were successfully returned. The cell was fully restored by 8:48am. <br><br> Root cause was traced to a combination of a procedural error and an automation bug while security patching infrastructure within US Cell 2. The procedural error targeted the security patching to a high usage cache cluster. The automation used to apply the patch disrupted the cluster’s ability to failover across nodes. <br><br> To prevent recurrence of this type of issue in the future, Engineering has immediately implemented additional safeguards to review and confirm operational patching procedures. Additionally, Engineering has prioritized a deep technical assessment to strengthen the patching automation for cache clusters. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-04242018). 2022-03-04T18:08:49.000Z https://www.salesforce.com/a9C2A000000KyxrUAC Following the release 2017.38, Okta experienced a feature disruption whereby a small subset of customers experienced javascript errors when signing-in to Skype for Business and Oracle Right Now. The errors occurred in oktapreview, US Cell1 and EU Cell1. Following the first customer reports at 6:17AM PDT, a work around was provided to customers by reverting them to the previous generation Okta sign-in experience. A fix was deployed across all impacted cells between 10:09AM and 11:40AM. The root cause found to be a JavaScript incompatibility between a new version of Okta's client side sign-in code (aka widget) and the embedded browsers that run in the impacted applications on Windows devices. <br><br> Review the root cause analysis [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Root-Cause-Analysis-Javascript-error-launching-Skype-for-Business-or-Oracle-09-26-2017) for this event for greater details about the issues and the changes being enacted to mitigate risks to user flows when new features are released. 2022-03-04T18:08:49.000Z https://www.salesforce.com/a9C2A000000KzYJUA0 On, February 2nd at 9:18am PST, Okta experienced an issue impacting Office 365 authentication in US Cell 1. Some end users attempting to authenticate to Office 365 received the following error: "Sorry, but we’re having trouble signing you in. AADSTS50008: Unable to verify token signature. The signing key identifier does not match any valid registered keys." The issue was found to be related to a recently deployed optimization intended to improve performance for Office 365 authentication flows. The change unexpectedly caused SAML assertion validation failures for approximately 5% of customers with Office 365. Only customers in US Cell 1 who created new Office 365 application instances using WS-Federation prior to a 2015 signing cert key pair upgrade were affected. The issue was resolved by reverting the optimization, which began at 9:52am and was completed at 10:25am. Longer term remediation includes broadening test coverage for various signing cert key pairs. 2022-03-04T18:06:43.000Z https://www.salesforce.com/a9C1Y0000008PfEUAU Okta has experienced an issue with the service. Increase in error rates accessing EU1 cell. ======= Resolved: Okta has mitigated an issue regarding increased error rates and latency in EU1. Additional root cause information will be provided on Monday, December 14th 2020. 2022-02-08T14:33:45.000Z https://www.salesforce.com/a9C4z000000wkADEAY Resolved: An issue impacting Authentication for certain embedded browser usecases for all endusers in US-Cell 1 and US-Cell 9 was addressed. Additional root cause information will be provided in 48 hours. 2021-10-27T22:17:38.000Z https://www.salesforce.com/a9C4z000000wk5IEAQ Okta is currently experiencing an issue with third-party SMS provider issue with ATT service. We are actively investigating and will update this message with more information as soon as we have it. For those users with a secondary MFA factor enrolled, a backup factor can be used. 2021-08-28T07:06:52.000Z https://www.salesforce.com/a9C4z000000wk32EAA Resolved: We observed intermittent issues in OK12 for customers utilizing Custom URL Domain functionality. As of 8:15pm, the system appears to be recovering. Additional root cause information will be provided in 2 business days. 2021-06-25T16:20:43.000Z https://www.salesforce.com/a9C4z000000oLnJEAU Resolved: An issue impacting access to ORGs has been resolved. An RCA will be provided within 48 business hours. 2021-06-15T21:42:48.000Z https://www.salesforce.com/a9C4z000000oLmzEAE Resolved: An issue impacting workflows dashboard access and flow execution has been resolved. An RCA will be provided within 48 business hours. 2021-05-25T23:29:21.000Z https://www.salesforce.com/a9C4z000000oLmQEAU End users authenticating to the Okta service may have experienced intermittent errors and increased latency between 11:04 and 11:47 am PDT. Okta will provide an RCA within the next 48 hours. 2021-05-15T14:23:43.000Z https://www.salesforce.com/a9C4z000000oLm1EAE Okta experienced a service disruption in OK6 starting at approximately 10:44 am PDT. Users would have experienced intermittent access, slowness and failures. As of 11:45 am PDT, OKTA services were fully restored. Okta will be providing a Root Cause Analysis within the next 48 hours. 2021-04-05T13:10:56.000Z https://www.salesforce.com/a9C4z000000oLkyEAE Resolved: Microsoft has reported that Microsoft DNS service is restored.  Okta Services related to Microsoft Office 365 and Azure are working as expected.  We are working with the service provider to understand the root cause of this service disruption and will post the RCA to status.okta.com within 48 hours. 2021-03-09T19:02:35.000Z https://www.salesforce.com/a9C4z000000oLkPEAU Okta is currently experiencing intermittent issues with external network connectivity in the OK8 (APAC) region. Depending on location, users may not be able to access our service. We are actively investigating and will update this message with more information. _________ Resolved: Okta experienced a service disruption in the OK8 cell (APAC) where customers may have experienced intermittent network connectivity due to a service provider issue. Service has returned to normal as of 11:30 AM PST. We are working with the service provider to investigate the root cause of this service disruption and will post the RCA to https://status.okta.com within 48 hours. 2021-02-05T23:13:38.000Z https://www.salesforce.com/a9C1Y0000008PgbUAE Okta has resolved the Office 365 login issue. The issue was limited to users with thick clients and using certain Edge browser versions. The issue impacted all cells, except US Cell 5. Root Cause Analysis (RCA) will be made available within 2 business days. ============================================ Customers have reported issues logging to Office365. The issue is limited to thick clients and certain browser versions. This may impact all cells, except OK5. We  are actively investigating and will provide additional updates shortly. 2020-12-01T06:11:20.000Z https://www.salesforce.com/a9C1Y0000008PepUAE We are investigating delays in event processing impacting System Log, Search API, and webhooks. Workflows Events associated with the Okta connector are also delayed. We will provide an update by 12pm PST. ==== Resolved: The processing delays have also been resolved for OP1 and System Logs are up-to-date. Additional root cause information will be provided on Monday, Nov 30th. 2020-10-29T21:30:38.000Z https://www.salesforce.com/a9C1Y0000008Pd8UAE Okta is currently investigating an issue with Advanced Server Access. Customers attempting to authenticate using ASA may experience increased latency or failures. We will provide additional updates shortly. === Service is fully restored for Advanced Server Access. Additional root cause information will be provided within 48 business hours. 2020-08-27T17:02:59.000Z https://www.salesforce.com/a9C1Y0000008PYSUA2 Okta is currently experiencing an issue with the service. Okta is currently investigating an issue impacting US Cells 1 - 4. More detail to be provided shortly. We are actively investigating and will update this message with more information as soon as we have it. Resolved: Okta has successfully restored all services in US Cell 1 - 4. Okta will continue to monitor the situation carefully. Additional root cause information will be provided within 48 hours. 2020-08-19T21:20:59.000Z https://www.salesforce.com/a9C1Y0000004EW8UAM Okta experienced an issue whereby end users, admins, and systems making API calls experienced 502 errors when attempting to connect to ORGs located in Oktapreview:1. User, API, and Admin traffic functionality has been restored and it is suggested that those with systems making API calls verify those systems have reconnected successfully. 2020-03-13T02:09:53.000Z https://www.salesforce.com/a9C1Y0000004E65UAE Okta is currently experiencing an issue with the service in US Cell 3. User Imports from Workday are resulting in users in No Password state. We are actively investigating and will update this message with more information as soon as we have it. Resolved: Okta has resolved the issue where Workday imports for some Orgs changed users to a No Password state resulting in those users being unable to authenticate. Root Cause Analysis will be provided here within 2 business days. Complete Root Cause Analysis may be found [Here.](https://status.okta.com/#incident/a9C1Y0000004E65UAE) 2020-01-27T20:18:33.000Z https://www.salesforce.com/a9C1Y0000004E8uUAE Okta is currently experiencing an issue with the service in US Cell 1. AD Agent and IWA agent states may not be correctly reflected. We are actively investigating and will update this message with more information as soon as we have it. Resolved: Okta has resolved an issue in US Cell 1 impacting AD/LDAP Agent state reporting. All on-line AD/LDAP Agents are now correctly reporting ACTIVE status. Additionally, some customers where all AD/LDAP Agents were marked NOT_CONNECTED should now see successful imports. Additional root cause information will be provided within 48 hours. Root Cause Analysis: On January 22nd at approximately ‪11:39am PST‬ Okta’s monitoring systems detected internal server errors in US Cell 1. The errors resulted in some customers' AD and LDAP agents being reported as NOT_CONNECTED to Okta Admins, even though the agents were functioning normally. Additionally, customers where all AD Agents were marked offline and who had Desktop Single Sign-On (IWA) configured using automatic fail-over may have experienced IWA failures. Okta implemented mitigation steps and the errors subsided at approximately ‪12:06pm PST‬. Okta subsequently corrected agent status for all customers by approximately ‪5:00pm PST‬. Upon investigation, Okta determined that a mistake was made when updating references to the database system during the execution of a planned routine database maintenance, This misconfiguration caused a very small number of requests to return an HTTP 500 error code and also resulted in the outdated agent status information. Okta has updated run-books and is improving the automation of maintenance verification procedures to prevent future occurrences. Okta is also investigating detection of agent status check job failures to prevent incorrect status indication to administrators. 2019-12-19T02:29:21.000Z https://www.salesforce.com/a9C1Y0000004E73UAE 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. Resolved: Okta has resolved the issue. All systems are operational issue has been mitigated. Okta will provide an RCA within 2 Business Days. Root Cause Analysis: On December 16, 2019 at approximately 6:22 AM PST, Okta detected a degradation in application performance in US Cell 4. As a result, customers may have experienced: - Longer than normal response times - A small percentage (0.25%) experienced sporadic read-only errors - Admin users may have intermittently seen the read-only banner Upon investigation, Okta determined that the root cause was unusual database activity required to process a significant number of group rules and assignments. Although our throttling and rate limiting mechanisms engaged, a portion of requests saw additional latency due to the increased utilization of our database tier while the load was being redistributed. At approximately 6:48 AM PST, Okta began to redistribute requests across the cell’s database cluster to reduce load and contention on the impacted database. By 8:09 AM PST, normal service performance was fully restored. Okta is implementing additional monitoring, optimization, and mitigation strategies to prevent similar issues in the future. Okta is also investigating asynchronous processing for group rules and performance improvements for group deletions to prevent system slowdown. 2019-12-16T08:19:31.000Z https://www.salesforce.com/a9C1Y0000004E6jUAE Okta experienced an issue with Agentless Desktop SSO for a subset of ORGs. We are actively investigating and will update this message with more information as soon as we have it. Resolved: Okta has resolved an issue where a subset of customers were unable to authenticate successfully via Agentless Desktop SSO in US Cell 1, US Cell 11, and EMEA Cell 1. Impacted customers may be required to clear their DNS cache to fully restore end user normalcy. Root Cause Analysis will be provided here within 2 business days. Root Cause Analysis: On December 10th, 2019 at approximately 9:30 AM PST, Okta began investigating reports by customers of problems authenticating via Agent-less Desktop SSO in US Cell 1, US Cell 11, and EU Cell 1. Okta determined that during the implementation of new load-balancers on December 4th 2019 at 3:15pm PST, DNS entries for Kerberos endpoints were not updated correctly for the impacted cells. As a result, Agent-less Desktop SSO traffic was still directed to the previous load balancers which were no longer working as intended, resulting in requests that timed out and user browser sessions being redirected to Okta login screens. While affected users were able to login, they had to type in their credentials instead of being logged in automatically. At approximately 10:48 AM, Okta updated the affected entries to reference the new load-balancers and service was restored. Some clients may have had to refresh DNS caches to restore service more quickly. Okta is working to implement additional monitoring and automation of changes to DNS records to prevent similar issues during future updates. 2019-12-08T03:03:48.000Z https://www.salesforce.com/a9C1Y0000004E5WUAU Okta is currently experiencing an issue with job processing for a subset of customers in US Cell 7. We are actively investigating and will update this message with more information as soon as we have it. Resolved: An issue impacting job processing for a subset of customers within US Cell 7 has been resolved. The remaining queued jobs are processing at full capacity and we will continue to monitor. Root Cause Analysis is underway and we will post full RCA details here within 48 hours. Root Cause Analysis: On December 2nd at approximately 7:45AM (PST), Okta detected a slowdown with processing import jobs on US Cell 7 and subsequently determined that there was an unusual and significant increase in asynchronous job workload which resulted in a backup of job processing. Okta increased system resources to expedite the processing of pending jobs. This mitigated the issue and normal functionality was fully restored by ‪10:16 AM. Okta is working optimize the current implementation of group application assignments to batch and de-duplicate assignments. Okta is also adding monitoring and controls to detect and mitigate similar issues in the future 2019-09-10T06:20:27.000Z https://www.salesforce.com/a9C1Y000000fxj2UAA Okta is currently experiencing an issue with new Developer tenant activation e-mails. In some use-cases, the activation link is present, but not visible within the activation email. We are actively investigating and will update this message with more information as soon as we have it. RESOLVED: Okta has successfully deployed and verified the fix for the issue with new Developer tenant activation e-mail in US Cell 7. Additional root cause information will provided within 48 hours. 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. Upon investigation, Okta determined that a software change to the Developer Tenant Email Template caused the generated emails to have noticeable styling issues and, in some clients, this caused one-time temporary passwords to become unreadable. At approximately 1:49 PM PDT Okta verified a fix and began deploying the change as a patch to the impacted cells. At approximately 2:13 PM PDT the fix was fully deployed and generated emails were sent with visible temporary passwords. Additional testing and monitoring to detect and mitigate this scenario will be rolled out for affected environments to prevent future occurrences. 2019-05-24T13:59:22.000Z https://www.salesforce.com/a9C1Y000000fxVtUAI Okta is currently experiencing an issue in US Preview Cell 1. Users attempting to authenticate under certain CORS use-cases are experiencing HTTP 400 errors <BR><BR> RESOLVED: Okta has identified and resolved an issue resulting in HTTP 400 errors when users were attempting to authenticate under certain CORS use-cases with tenants in US Preview Cell 1. Additional root cause information will provided within 48 hours. <BR><BR> ROOT CAUSE: On May 15th at approximately 1:42PM PDT, customers in US Preview Cell 2 experienced elevated errors when making HTTP OPTIONS-based requests, predominately against the "/oauth2/v1/userinfo" and "/api/v1/sessions/*****" endpoints. At 3:09PM PDT, Okta began to detect similar errors in US Preview Cell 1. <BR><BR> The elevated error rate was determined to be due to a bug within a new framework used to determine request timeout configurations, and specifically impacted the HTTP OPTIONS method. The new timeout framework was disabled to mitigate the issue, and the service was fully restored at approximately 4:35PM PDT for US Preview Cell 1, and at 4:43PM PDT for US Preview Cell 2. <BR><BR> Following this incident, this bug in the new timeout framework has been addressed. Okta will be adding additional test procedures to detect this issue prior to re-enabling the framework. 2018-12-17T07:39:46.000Z https://www.salesforce.com/a9C1Y000000GpJuUAK Okta is currently experiencing an issue with CORS authentication in Okta Preview Cells; customers using OIDC applications or API AM might be impacted. Okta is actively working on resolving the issue. <br><br> Root Cause Analysis: On December 12th, an issue was introduced in Okta Preview cells which impacted the use of the Auth SDKs. Specifically, customers using version 2.0 or higher of Okta’s JavaScript SDK AuthJS (@okta/okta-auth-js) to leverage OAuth 2.0 may have experienced authentication failures starting at approximately 2:21pm PST. Additionally, customers using Okta’s Angular, React and Vue integration libraries and OAuth 2.0 in Preview cells were also impacted by this issue. The degree of impact varied depending on each customers’ implementation and client-side caching. <br><br> The root cause was traced to an unexpected side effect from a fix applied to our CORS/TrustedOrigins framework. The issue was fully resolved on Dec 13th by 6:26am PST in US Preview Cell 1 and by 6:38am PST in EU Preview Cell 2. To prevent a similar re-occurrence, the test automation framework gap has been updated and existing test suites are being enhanced to identify such errors in the future.. 2018-10-29T08:50:00.000Z https://www.salesforce.com/a9C0Z0000008PViUAM On Oct 23rd at approximately 9:15pm PDT, Okta began receiving reports from customers who were experiencing errors while attempting to provision users to Office 365 services hosted by Microsoft. User authentication was not affected. ========== Resolved: On Oct 24th at 9:49am PDT, Okta Engineering identified an incompatibility with the latest release of Office 365 in a subset of Office 365 tenants. The incompatibility interrupted completion of the user provisioning process. A fix was identified and rolled out to production cells, and user provisioning functionality was fully restored at approximately 8:19pm PDT. <br><br> Okta is evaluating this incompatibility condition to ensure such occurrences are monitored and detected in the future. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-10232018-Office-365-Provisioning-Failuers). 2018-10-18T04:46:11.000Z https://www.salesforce.com/a9C0Z0000008PVOUA2 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. Resolved: On October 15th, beginning at 3:58 PM PDT, Okta experienced a service disruption in US Cell 6. The service disruption occurred during two distinct windows. Between 3:58 PM PDT and 4:05 PM PDT, approximately 15% of incoming end user requests to US Cell 6 experienced latency or errors. Between 4:28 PM PDT and 4:33 PM PDT, approximately 9% of end-user requests to US Cell 6 experienced latency or errors. The service disruption was resolved and the service was returned to normal at 4:33pm PDT. The root cause of the service disruptions was traced to a significant and abnormal increase in requests that activated Okta's rate limiting framework but eventually resulted in higher than normal CPU utilization within our infrastructure. Starting at 3:57, Okta's monitoring services detected the increase in abnormal traffic, and automated service protections were employed to mitigate the impact, however, additional actions were needed to reroute and isolate the offending traffic. Following the service disruption, Okta reviewed the incident response and has identified and plans to implement additional automated and manual incident response process improvements and infrastructure changes to further minimize impact or prevent similar incidents in the future. 2018-09-20T03:44:40.000Z https://www.salesforce.com/a9C0Z0000008PUVUA2 Resolved: On September 17th, at 4:40pm PDT, an issue began surfacing which impacted end users and admins attempting to authenticate to Microsoft Office 365 in US Cell 1. The root cause was a manual error which occurred during normal preparation steps for the deployment of the weekly release. Specifically, the preparation step which applies new app version information into a pre-production environment for final release validation resulted in a new app version definition of Office 365 to be applied to US Cell 1. Because the Office 365 app version definition was then ahead of the US Cell 1 production environment, some authentication requests received HTTP 500 error responses. At the highest level of impact, 42% of browser initiated, and 7% of thick client (non-browser) initiated, authentication requests to O365 in US Cell 1 received a HTTP 500 error response. There was no impact to those with active sessions. Once identified, a strategy to safely roll-back the updated app version definition was confirmed and initiated. By 6:14pm PDT, the issue was resolved for a subset of customers and by 6:55pm PDT the issue was fully resolved. To prevent a future reoccurrence, actions are being taken in multiple phases. Immediately, a procedural change was implemented to accelerate internal escalation and recovery procedures for similar situations. Within the next few weeks, improvements will be made to the management of alerts enabling faster error identification, and to automation tooling to automatically prevent the application of incompatible app version definitions. 2018-09-12T23:03:00.000Z https://www.salesforce.com/a9C0Z0000008PTwUAM Resolved: Okta experienced an issue when users attempted to navigated to their *.oktapreview.com tenant within Google Chrome or Firefox. When populating credentials, users may have experienced the following warning: "Deceptive site ahead". Okta worked with Google to implement mitigating steps to resolve the issue. _____ Root Cause Analysis: On September 5th, 2018 at approximately 1:12pm PDT, an issue impacting Preview cells (Preview Cell 1, Preview Cell 2). Customer's end users and administrators using Chrome or Firefox browsers with Safe Browsing enabled may have been prompted with an anti-phishing warning message while attempting to login into oktapreview subdomains. Similar login requests via other browsers, and all requests to other end-user and API endpoints were not impacted. The root cause was traced to a false-positive determination by the [Google Safe Browsing](https://safebrowsing.google.com/) unsafe site detection service integrated into Chrome and Firefox, which reported any *.oktapreview.com/login was a likely phishing page. The issue was fully resolved by 7:23pm PDT following collaboration with Google’s anti-phishing team. To prevent a future recurrence, actions are underway to engage with top browser and associated service providers to partner on safeguards such as whitelists and early warning notifications. 2018-07-09T05:50:19.000Z https://www.salesforce.com/a9C0Z0000004EAAUA2 An issue impacting search functionality in US Preview Cell 1 has been resolved. A root cause analysis will be posted here within 2 business days. =============== Resolved: On July 5th, beginning at 10:55am PDT, Okta experienced a service degradation in US Preview Cell 1. The issue impacted customers who have enabled Early Access to User Search and are leveraging the /api/v1/users?search endpoint. The root cause was traced to an inconsistency in the deployment and validation choreography between our test and preview environments for the Search micro-service. This inconsistency prevented an incompatible configuration setting from being detected in the test environment, causing the Search endpoint to fail and return 503 error responses. The issue was resolved by reverting the change which caused the regression, allowing the Search micro-service to recover by 11:21am PDT. The inconsistency in the Search micro service's deployment and validation choreography has been resolved. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Degradation-07-05-2018). 2018-06-06T23:38:38.000Z https://www.salesforce.com/a9C0Z0000004E5UUAU An issue impacting network connectivity to US Cell 6 was experienced and has now been resolved. Root cause analysis will be posted here within 48 hours. ================================= Resolved: On May 31st, beginning at 12:13am PDT, Okta experienced a broad service disruption to US Cell 6. The disruption triggered Okta's automated monitoring, alerting the Engineering team who determined that both the application and its underlying cloud computing infrastructure was unreachable. This pointed to a multi-availability zone outage in Okta's cloud infrastructure and network provider. This was confirmed by our provider, and the decision was made to fail over to the cell's Disaster Recovery (DR) instance and the process was initiated. However before the DR failover process completed, network connectivity was restored and within approximately 5 minutes, automated system recovery processes had returned the cell to normal performance levels; ending the disruption at 12:46am PDT. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-05312018). 2018-05-22T20:45:00.000Z https://www.salesforce.com/a9C0Z000000TNhVUAW Resolved: 1:40pm PDT. The issue impacting e-mail delivery to 'support@okta.com' and 'developer@okta.com' has been resolved. ======================= Customer Advisory: Okta is currently experiencing issues with receiving customer e-mails to 'support@okta.com' and 'developer@okta.com'. This does not impact the Okta service availability or any e-mails sent from your Okta tenant. If you need assistance with a new or existing Okta customer support incident, please call Okta at (800) 219-0964. Additional international support numbers may be found at [Okta Support] (https://support.okta.com/help). 2018-05-22T02:03:34.000Z https://www.salesforce.com/a9C0Z000000TNgDUAW An issue impacting authentication and user interactive sessions in US Cell 6 is being investigated. End-Users and Admins may experience HTTP 500/503 errors while attempting to login. We are actively working to mitigate the issue and return the service to normal as quickly as possible -------------------------- Resolved: On May 17th, beginning at 11:28am PDT, Okta experienced a service disruption in US Cell 6. End-User and Administrators attempting to authenticate to their Okta tenant may have experienced HTTP 5xx errors. Through the duration of the incident, approximately 30% of US Cell 6 users attempting primary or multi-factor authentication encountered errors and would have needed to retry. Other requests, and End-Users and Administrators who already had an active session did not experience any impact. The issue surfaced when the cell's session token management cluster became overwhelmed by a sudden increase in the number of active sessions. Automated monitoring failed to effectively alert before the cluster was nearing its maximum capacity. The issue was resolved by 12:19pm PDT after operational actions were taken to manage the session count while capacity was added to the cluster. Immediately following the incident, Okta corrected the monitoring gap to prevent a future recurrence. Architectural design work is being initiated to better manage session counts and their expiry. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-05182018). 2018-03-10T00:16:29.000Z https://www.salesforce.com/a9C2A000000PBikUAG Okta is currently experiencing an issue with the API Access Management feature in our US Preview Cell. End-users attempting to access endpoints for this feature may receive an HTTP 500 error. Okta is currently working to resolve the issue and we will post an update shortly. 2018-03-09T23:40:34.000Z https://www.salesforce.com/a9C2A000000PBipUAG Okta is currently experiencing an issue in US Cell 6 whereby users attempting to login to Okta are experiencing slowness, timeouts, or HTTP 500 errors when attempting to login or navigate their Okta tenant. 2018-02-28T06:38:35.000Z https://www.salesforce.com/a9C2A000000PBiBUAW On February 25th, Okta experienced an issue in US Preview cell beginning at 9:00am PST which resulted in approximately 2.3% of interactive requests for end-users and administrators receiving HTTP 500 or 504 errors. Okta Engineering's investigation found that an outbound internet gateway high availability solution for one of the three availability zones in the US Preview cell had failed. Following a manual fail-over, the issue was mitigated by 9:33am for all services except Syslog v2 which was fully restored by 9:57am PST. To mitigate future impact, improvements are planned for the high availability infrastructure which manages outbound internet traffic. 2017-09-18T15:15:10.000Z https://www.salesforce.com/a9C2A000000KyvbUAC Following the September 12 evening deployment of the 2017.36 weekly release, customers in all Cells began reporting that some of their users were locked out of Okta. Upon investigation, the enablement of a new password policy soft lock feature (for customers with the Universal Directory SKU) was identified as the root cause. <br><br> The password policy soft lock feature enables access to Okta to be restricted when users' corresponding Windows accounts are locked, or when users exceed a specified threshold for failed login attempts to Okta. Customer feedback following the release revealed that the feature led to greater than expected end user impact. The feature was immediately disabled for customers that reported the issue initially and at 10:40am PDT the feature was disabled for the rest of the customers that had the feature enabled as part of the 2017.36 release on September 12. <br><br> Review the root cause analysis [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Feature-Disruption-09-13-2017) for this event for greater details about the issues and the changes being enacted to mitigate risks to user flows when new features are released. 2017-09-07T19:23:46.000Z https://www.salesforce.com/a9C2A000000Kyv2UAC At approximately 8:35am PDT, Okta began experiencing delays in SMS message delivery to customers across US Cells. Customers leveraging SMS for Multifactor Authentication or Account Recovery may not have received the SMS message and were prompted to retry. Upon retry, automated fail-over to Okta’s secondary SMS vendor would have occurred. However SMS delays were experienced by both vendors, and as a result, messages for a subset of customers may not have been received. SMS delays had fully dissipated by 10:45am PDT. All other secondary authentication factors, such as Okta Verify, Voice call, Duo, Yubikey, Google Authenticator, or Security Question were not affected. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-SMS-Delivery-Delays-08-31-2017). 2017-09-07T02:09:52.000Z https://www.salesforce.com/a9C2A000000bmDeUAI Okta experienced an issue in US Cell 2 beginning at 4:55am PDT which increased database utilization beyond normal levels. An average of 10% of incoming requests to US Cell 2 experienced intermittent latency through to 8:05am, with peaks up to 40% of requests between 4:55am and 6:30am PDT and between 7:55am and 8:05am PDT. The impact of the issue was mitigated via an operational configuration change to further distribute incoming requests. Okta also implemented query optimizations and additional capacity to spread traffic and minimize database utilization. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Okta-Performance-Issue-08-03-2017-08-04-2017). 2017-09-07T02:08:57.000Z https://www.salesforce.com/a9C2A000000bmESUAY Okta experienced an issue in US Cell 2 beginning at 5:30am PDT which, like the Aug 4th incident, increased database utilization beyond normal levels. An average of 20% of incoming requests to US Cell 2 experienced intermittent latency through to 6:00am, with a peak of 25% of requests. The window of impact was reduced by leveraging the operational configuration changes made the day before to further distribute incoming requests. Okta also deployed query optimizations and additional capacity to spread traffic and minimize database utilization. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Okta-Performance-Issue-08-03-2017-08-04-2017). 2017-08-23T16:21:54.000Z https://www.salesforce.com/a9C2A000000bmJDUAY Okta experienced an issue which caused the Okta home page in US Cell 5 to be inaccessible for a small number of users beginning at 4am PDT. The root cause was traced to an operational procedural error which prevented the correct set of static files and artifacts from being accessible via Okta's CDN (Content Delivery Network) to a subset of users. Approximately 1% of end users in US Cell 5 who attempted to reach the Okta home page via a browser may have received a 404 error; all other customers in US Cell 5 who either accessed Okta via other methods (e.g. API, SAML, WSFED), or whose browser cache was available, were not impacted. <br><br> The issue was resolved by 10:30am PDT by making the missing files accessible to the CDN servers. Operational procedures are being remedied to prevent a future re-occurrence, and alerting thresholds are being lowered for improved internal notification. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-August-21-2017-US-Cell-5-Service-Degradation). 2017-08-21T23:32:18.000Z https://www.salesforce.com/a9C2A000000bmHvUAI Beginning at 3:22pm PDT, Okta was alerted to minor latency spikes on a disk volume within US Cell 2. The latency spikes minimally impacted system responsiveness. Upon investigation, customer impact was negligible. 2017-07-15T18:46:18.000Z https://www.salesforce.com/a9C2A000000bmBsUAI Okta experienced a database utilization spike at 6:05am PDT. A subset of the application servers in US Cell 2 did not recover properly which resulted in reduced throughput capacity until the issue was resolved at 6:30am. The reduced throughput caused slowness for approximately 40% of requests while corrective actions were being taken. Customers may also have experienced intermittent AD real-time sync errors during this period. Office365 requests remained unaffected for the duration of the incident. <br><br> Okta has determined the root cause for the application servers not recovering properly to be a database driver bug. Application server configuration settings have been adjusted to mitigate future re-occurrence while we test and deploy an upgraded database driver to address the root cause. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Performance-Issue-07-11-2017). 2017-06-29T23:00:22.000Z https://www.salesforce.com/a9C2A000000bmApUAI Okta Experienced a minor service disruption in US Cell 4 where a small number of customer tenants experienced intermittent deprovisioning of some Active Directory or LDAP mastered users. This issue was caused by a synchronization error between Okta Servers in US Cell 4 and an authoritative NTP service as a result of a recent network maintenance configuration change.  For the small number of impacted tenants, the subsequent server clock-drift resulted in intermittent import processing errors, including occasional user deprovisioning. While working to resolve the issue, Okta placed US Cell 4 into a Read-Only mode between 11:27pm and 12:10am PDT. Administrative updates via Okta Admin or the API would have been unavailable during this time. The issue was fully resolved at 6/27/2017 @ 12:10am PDT. <br> <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-User-Unexpectedly-Deactivated-And-Attribute-Updates-Not-Occurring-On-Import-06-20-2017-06-27-2017). 2017-06-22T08:37:10.000Z https://www.salesforce.com/a9C2A000000bm9IUAQ Okta experienced a disruption between 8:34pm PST and 9:08pm PST in US Cell 2. A failure in the manual sequencing of a planned database maintenance procedure resulted in slightly elevated error rates. Admins as well as integrations making API update calls would have also experienced extended Read-Only mode while corrective actions were taken. Database maintenance scripts have been augmented to prevent a similar occurrence in the future <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-06192017). 2017-06-16T01:26:00.000Z https://www.salesforce.com/a9C2A000000bm6BUAQ Beginning at 5:45pm PDT, Okta experienced intermittent availability of the Okta Mobile for Android app in the Google Play Store. The issue was due to an unexpected change to the Google Play Store. Okta worked with Google, and full availability of the application was restored at 8:24pm PDT. Users who had previously installed Okta Mobile on their devices were unaffected, as the application continued to work normally throughout the incident. We are continuing to work with Google to avoid similar issues in the future. <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Okta-Mobile-Android-Unavailable-In-Google-Play-Store). 2017-05-18T00:47:21.000Z https://www.salesforce.com/a9C2A000000blruUAA Okta experienced a service disruption at 6:01am with increased response times and a small number of authentication failures due to a drop in network throughput between hosts in US Cell 2. Corrective action was taken to address this condition and authentication times returned to normal levels by 6:39am. <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-05152017). 2017-05-18T00:46:55.000Z https://www.salesforce.com/a9C2A000000blrzUAA Okta experienced a performance degradation of job processing as corrective actions were taken to restore service from an earlier incident. As an investigative step, job processing in US Cell 2 was paused from 6:38am to 7:34am PDT. <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-05152017). 2017-05-09T20:59:31.000Z https://www.salesforce.com/a9C2A000000blcGUAQ Okta experienced a service disruption between 9:55am PST and 10:11am PST following a database misconfiguration. Intermittent authentication failures may have been experienced by end users between 9:55am and 10:01am. In addition administrators as well as integrations making API update calls in US Cell 2 may have experienced a period of Read-Only mode during this time as corrective actions were taken. <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-May-5-2017-Service-Disruption-Database-Failover). 2017-05-09T20:57:38.000Z https://www.salesforce.com/a9C2A000000blcLUAQ Okta experienced an intermittent disruption to email delivery starting May 4th, at 8:26am PST. The issue was the result of a bug in a deployment automation script which resulted in an incomplete configuration being applied to one of the email relay servers which had to be relaunched due to hardware failure. The issue was resolved by correcting the server's configuration settings on May 5th, at 10:47am PST. Okta is resolving the deployment script bug and adding additional server launch validation steps to prevent any future re-occurrence of this issue. <br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-May-5-2017-Email-Feature-Disruption). 2017-04-20T00:46:23.000Z https://www.salesforce.com/a9C2A000000XZsoUAG Starting at 10:15am PDT Okta experienced delays in delivering SMS messages to customers because of a failure with one of our redundant SMS vendors. Messages sent via our secondary vendor were also delayed due to a significant increase in volume. Service was restored at 11:45am PDT and all delayed SMSs were delivered by then. Okta will be working with our messaging vendors to root cause the incident and prevent this from happening in the future. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-Feature-Disruption-04-18-2017). 2017-03-23T00:12:47.000Z https://www.salesforce.com/a9C2A000000XZl4UAG Okta experienced a service disruption in US Cell 5 beginning at 7:49pm PDT following a failure in the infrastructure network layer. The failure was the result of a configuration problem that was preventing hosts from establishing new connections as connections needed to be refreshed. While corrective actions were being taken and connections re-established, processing of web and API authentication requests was affected. The cell returned to normal operations by 8:36pm PDT. The issue was traced to a failure of our validation procedure for network infrastructure changes that will be corrected to prevent, detect and promptly repair similar issues in the future. 2017-03-15T19:03:27.000Z https://www.salesforce.com/a9C2A000000XZkGUAW Okta experienced an issue in US Cell 2 starting at 1:40pm PST when two edge IP addresses were erroneously reassigned from the pool of active IPs. Root cause was traced to an outdated configuration file. While correction actions were in progress, a small percentage of customers may have experienced sporadic connection timeouts. US Cell 2 was returned to normal operations by 2:21pm PST. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/Documentation/Knowledge_Article/Root-Cause-Analysis-March-2-2017-Performance-Issue). 2017-02-17T02:30:45.000Z https://www.salesforce.com/a9C2A000000XZiUUAW Okta experienced a feature disruption between 8:06am PST and 8:22am PST following a database memory management failure. Admins as well as integrations making API update calls in US Cell 1 may have experienced a period of Read-Only mode during this time as corrective actions were taken. 2017-02-07T01:14:22.000Z https://www.salesforce.com/a9C2A000000XZfGUAW On Thursday, February 2, 2017, between 4:16am and 6:20am PST, Okta experienced a service disruption in US Cell 2 in which end-users experienced latency and errors while accessing Office 365. Between 4:16am and 5:05am PST end-users in US Cell 2 experienced an average 25% error rate connecting to Office 365. Error rates increased between 5:06am and 6:20am PST, and peaked as high as 95% at 6:01am PST. During this time, users may also have experienced latency or errors when connecting to other applications. <br><br> From 5:30am and 6:05am, end-users in US Cell 1 - 4 also experienced sporadic latency and timeouts, with latency peaking at 40%, while error and timeouts remained below 10% of requests for interactive user sessions. This degradation was mitigated and service returned to normal at approximately 6:20am PST. <br><br> The service disruption was triggered by an anomalous spike in Office 365 authentication requests which were not correctly rate-limited. Okta is investigating the source of the spike in Office 365 authentication requests. Okta has also corrected the rate-limit configuration and added additional capactiy and tuning improvements to prevent this issue from occurring in the future. <br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/articles/Knowledge_Article/Root-Cause-Analysis-Service-Disruption-02022017). 2017-02-02T06:09:47.000Z https://www.salesforce.com/a9C2A000000XZewUAG Okta experienced a feature disruption in our SAML documentation framework at 11:08am PST as the result of a documentation release framework bug. During this time, administrators who attempted to add SAML applications or view existing SAML setup instructions were unable to do so as the setup instructions were not properly rendered. The issue was resolved by correcting the documentation package bug. The SAML application setup instructions were restored by 1:15pm PST. 2017-01-20T02:05:49.000Z https://www.salesforce.com/a9C2A000000XZeNUAW Okta experienced an issue impacting the application router infrastructure which led to timeout and connection failures for customers in US Cells 1, 2, 3 and 4 beginning at 11:28am PST. Root cause was traced to a specific error handling bug in the router infrastructure. Once identified, the bug was bypassed via a config change to restore service across each of the impacted Cells by 11:42am PST. Event Root Cause Analysis details can be found [here](https://support.okta.com/help/articles/Knowledge_Article/Root-Cause-Analysis-January-17-2017-Service-Disruption). Login Required. 2017-01-14T01:36:45.000Z https://www.salesforce.com/a9C2A000000XZe3UAG Okta experienced a degradation to async processing in US Cell 2 starting at 8:30am PST. This resulted in a delay to job and system log event processing. The start time for import jobs was delayed an average of 3 hours between 8:45am PST and 7:30pm PST. Event processing delays resulted in system log lags up to 5 hours. The degradation was the result of an unintended increase in the volume of jobs and events, which was caused by a backend change to the profile sync functionality. By 9:30pm PST all async processing was at normal levels, and system event log information was current. 2017-01-13T00:46:55.000Z https://www.salesforce.com/a9C2A000000XZdeUAG Okta experienced an unexpected increase in load on the US Cell 1 load balancers beginning at 6:07am PST. The increase was traced to recently updated back-end agent request error handling logic. Approximately 9% of web and API authentication requests intermittently failed while operational actions were taken to rollback the updated agent request error handling logic. Processing of web and API authentication requests returned to normal levels at 7:05am PST. Additional capacity has since been added to the load-balancers and the updated logic has been rolled back in all cells.<br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/articles/Knowledge_Article/Root-Cause-Analysis-January-9-2017-Service-Degradation) 2017-01-13T00:46:36.000Z https://www.salesforce.com/a9C2A000000XZdjUAG Okta experienced an unexpected increase in load on the US Cell 3 load balancers beginning at 7:59am PST. The increase was traced to recently updated back-end agent request error handling logic. Approximately 6% of web and API authentication requests intermittently failed while operational actions were taken to rollback the updated agent request error handling logic. Processing of web and API authentication requests returned to normal levels at 8:16am PST. Additional capacity has since been added to the load-balancers and the updated logic has been rolled back in all cells.<br><br> Event Root Cause Analysis details can be found [here](https://support.okta.com/help/articles/Knowledge_Article/Root-Cause-Analysis-January-9-2017-Service-Degradation) 2016-12-23T17:36:48.000Z https://www.salesforce.com/a9C2A000000XZcgUAG Okta experienced an unexpected database connection spike in US Cell 1 beginning at 5:50am PST following the initiation of an database transaction that did not perform as expected. The spike impacted the successful processing of a subset of web and API authentication requests as well as intermittent failure of administrative functions. Between 6:06am and 6:10am a peak of 10% of web and API authentication requests failed. Administrative functions would have seen intermittent failures while operational actions were taken to return the service to a healthy state at 6:15am.