Okta Outage History

An issue impacting third party provider(s) regarding import slowness has been resolved. Additional root cause information will be available within 5 business days.

The following is the RCA summary for a recent incident where a third-party provider experienced an issue that impacted the Okta service. Timing: Incident start: August 7, at 06:02 PM PDT Incident resolved: August 8, at 02:00PM PT Detection: Okta Engineering was alerted to backend jobs queues increasing due to a slow third-party provider API response. Impact: Customers may have seen slow job processing in Okta. Summary: Jobs were queued due to job execution times increase while waiting for third-party provider API responses. Our third-Party provider has identified a configuration error and resolved this issue by provisioning additional resources to these APIs. Preventive Actions: Okta has introduced additional logging to identify similar disruptions closer to their start.

Android Okta Verify end-users may not receive push notifications due to a third-party outage. Launching Android Okta Verify manually will allow authentication. Okta will provide an update as it becomes available.

Okta monitoring shows push notifications on Android Okta Verify due to a third-party outage have recovered. Additional root cause information will be available within 10 Business days.

The following is the RCA summary for a recent incident where a third-party provider or downstream service experienced an issue that impacted the Okta service. Timing: Incident start: June 12, 2025, 10:50 AM PT Incident resolved: June 12, 2025, 12:15 PM PT Detection: Okta Engineering noticed errors related to this feature on June 12, 2025. Impact: During this outage, Android users attempting to authenticate via Push would not receive a push notification on their device and would be required to open Okta Verify to complete authentication. Summary: Google Cloud Services confirmed disruptions to their services (including those necessary for the delivery of Android push notifications) that were resolved on June 12, 2025, at 13:49 PT. More details, as provided by Google, can be found here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW.

We have identified an issue with Okta Personal where end users are unable use the application

Engineering has identified and resolved an issue where end users are unable to access Okta Personal vault due to a failed DB migration. End user data was unaffected.

Out of an abundance of caution, an update was posted at 11:05 am PDT on June 11, 2025. However following additional investigation, it was determined that a broad service degradation / disruption notice was not applicable. Okta will continue to monitor closely and directly engage with any customers as needed.”

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.

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 has contacted Paylocity and is working to resolve this as quickly as possible. We’ll provide an update in 60 minutes, or sooner if additional information becomes available.

Okta Engineering has received confirmation from Paylocity that this issue is resolved and is monitoring our backend logging for the Paylocity OIN integration. Our logging indicates an improvement in import success rates. At this time, customers should resume Paylocity imports.

The Paylocity OIN integration import issue for all Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor Paylocity OIN integration import performance. Additional root cause information will be available within 5 Business days.

Detection: Customers began reporting that Paylocity OIN Integration imports were removing users from Okta. The import jobs were receiving an error response from the Paylocity SCIM API backend. Impact: Paylocity OIN Integration import jobs would receive an error from the Paylocity backend which would then cause the import job to remove users as not found if Paylocity was configured as the profile master. Root Cause: Paylocity confirmed they had erroneously disabled the SCIM API that the Okta integration relies on. This API was disabled between 7:53 AM PST and 1:00 PM PST. Remediation Steps: Okta customers using the Paylocity OIN Integration would need to rerun any imports that occurred during this time window to restore users that had been removed. Import roadblock settings in Okta would prevent excessive removals if configured.

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.

An issue impacting SMS OTP to end users in China has been resolved. Additional root cause information will be available within 5 Business days.

Timing: Incident start: September 17, 2024, at 5:00 PM PDT Incident resolved: September 17, 2024 at 7:28 PM PDT Detection: Okta Customers reported that users in China were not receiving their multi-factor authentication (MFA) one-time passwords (OTP) via SMS. Impact: Users in China were unable to receive SMS-based OTPs for MFA during the incident period. Root Cause: One of Okta’s telephony providers implemented an unannounced configuration change, leading to SMS delivery disruption to users in China. Remediation Steps: Okta teams immediately notified our telephony provider of the disruption. The provider was able to identify and reverse the problematic change, restoring SMS service to China.