Okta Outage History

Started Apr 23, 2025, 08:55 PM UTC· resolved Apr 30, 2025, 04:47 PM UTC

1. resolved Apr 23, 2025, 08:55 PM UTC

   Okta Engineering became aware of an issue with a downstream email provider. Customers may experience errors with MFA Emails, password reset, and user activation. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Apr 24, 2025, 12:31 AM UTC

   We have received confirmation that the errors have subsided. We will continue to monitor the situation until it's fully resolved.

3. resolved Apr 24, 2025, 04:30 AM UTC

   The issue affecting our email delivery has been resolved. Additional root cause information will be available within 10 Business days.

4. resolved Apr 30, 2025, 04:44 PM UTC

   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: April 23, 2025, at 1:55 PM PDT Incident resolved: April 23, 2025, at 2:55 PM PDT Impact: During the disruption period, customers and users in standard production and preview cells did not receive expected system-generated emails. This included emails for password resets, MFA when using email as a factor, account activation, and any other email notifications related to org or policy changes. These emails were delayed and only began to arrive once Okta’s third-party email provider recovered at approximately 2:55 PM PDT. Root Cause: Okta’s third-party downstream email provider experienced a disruption that prevented emails from being sent during the disruption period. Preventive Actions: Okta has added additional monitoring and alerting to detect such issues more rapidly in the future, enabling us to validate the issue with our downstream providers more quickly and respond.

Read the full incident report →

Started Apr 16, 2025, 12:32 AM UTC· resolved Apr 23, 2025, 10:17 PM UTC

1. resolved Apr 16, 2025, 12:32 AM UTC

   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 Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Apr 23, 2025, 10:17 PM UTC

   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: April 14, 2025, at 1:40 PM PDT Incident resolved: April 15, 2025, at 5:54 PM PDT Detection: Okta Engineering noticed errors related to this feature on April 15, 2025. Impact: Customers may have seen failures when attempting to set up Apple Business Manager (ABM) integrations. Summary: Apple confirmed disruptions to ABM that were resolved on April 15, 2025, at 5:54 PM PDT. Preventive Actions: Okta has introduced additional logging to identify similar disruptions closer to their start.

Read the full incident report →

Started Apr 04, 2025, 03:00 PM UTC· resolved Apr 11, 2025, 09:39 PM UTC

1. resolved Apr 04, 2025, 03:00 PM UTC

   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. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11, okta.com:12, okta.com:14

2. resolved Apr 04, 2025, 04:27 PM UTC

   We're currently investigating an issue causing the degradation of OIG Access Requests. Our engineering team is actively working to identify and resolve the problem. We will provide another update in 30 minutes or less if more details become available.

3. resolved Apr 04, 2025, 04:48 PM UTC

   We're currently investigating an issue causing the degradation of OIG Access Requests. Our engineering team is actively working to identify and resolve the problem. We will provide another update in 30 minutes or less if more details become available.

4. resolved Apr 04, 2025, 05:05 PM UTC

   We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

5. resolved Apr 04, 2025, 05:06 PM UTC

   We have identified the potential cause of the issue. Our Engineering team is working on fixing the Okta Identity Governance (OIG) access request issue and we have been observing improvements. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

6. resolved Apr 04, 2025, 05:24 PM UTC

   Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.

7. resolved Apr 04, 2025, 05:50 PM UTC

   Okta continues to monitor the current situation with the Okta Identity Governance (OIG) access request issue. Our monitoring shows a recovery to normal conditions. Our next update will be in 30 minutes or sooner if additional information becomes available.

8. resolved Apr 04, 2025, 06:13 PM UTC

   An issue impacting Okta Identity Governance (OIG) access requests for users in all US Production Cells has been resolved. Additional root cause information will be available within 5 Business days.

9. resolved Apr 11, 2025, 09:37 PM UTC

   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 Friday, April 4th at 7:59 am (PT), Okta’s monitoring systems alerted our Engineering team that some OIG users in US Commercial Cells were experiencing slow requests and request errors for governance requests via Okta Inbox. Retry attempts would eventually succeed. Root Cause Summary: Based on our investigation, an increase in a specific query requiring significant resources resulted in extra database load. This resulted in increased query latency, workload connection errors, and inbound API call failures. Remediation Steps: Upon receiving alerts, Okta began diagnosing the issue and launched a series of scaling activities. The team identified the root cause of the issue and took action to remediate the situation. At approximately 9:42 am (PT) Okta saw a decrease in query delays in the affected cell. At 9:43 am (PT) service latency returned to normal operation. Preventative Actions: To ensure this does not happen again, teams are remediating expensive database operations to prevent recurrence of this issue. Okta is looking into enhancing monitoring to identify expensive database operations faster. Additionally, runbooks are being updated to allow for faster remediation

Read the full incident report →

Started Feb 12, 2025, 03:08 PM UTC· resolved Feb 21, 2025, 06:20 PM UTC

1. resolved Feb 12, 2025, 03:08 PM UTC

   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. Affected cells: okta.com:14

2. resolved Feb 12, 2025, 03:36 PM UTC

   Okta is aware of an issue causing Flows and Connection tabs from showing in the Okta Workflows Console. The steps in the following KB can be used to resolve while Okta teams work to perform a permanent fix: https://support.okta.com/help/s/article/no-access-to-flows-or-connections-tabs-in-workflows-console?language=en_US

3. resolved Feb 12, 2025, 03:41 PM UTC

   Okta is aware of an issue causing Flows and Connection tabs from showing in the Okta Workflows Console. The steps in the following KB can be used to resolve while Okta teams work to perform a permanent fix: https://support.okta.com/help/s/article/no-access-to-flows-or-connections-tabs-in-workflows-console?language=en_US We will provide another update in 30 minutes or less if more details become available.

4. resolved Feb 12, 2025, 03:59 PM UTC

   An issue impacting access to Workflows for admins in OK14 has been resolved. Additional root cause information will be available within 5 Business days.

5. resolved Feb 21, 2025, 06:19 PM UTC

   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 February 11, 2025 at 4:02pm PST Okta was alerted through its monitoring systems of a feature rollout failure in US Cell OK14. On February 12th 5:00am PST Okta began to receive reports that users were unable to view or access resources in the Workflows app. The impact was isolated to customers on US Cell OK14. Root Cause Summary: Okta determined that the cause was a cache invalidation issue which prevented additional intended feature rollouts from occurring. This caused subsequent failures in the feature rollout system and resulted in Read Only or limited access for some Workflows users. Remediation Steps: Upon receiving the support cases Okta took action to remediate the situation. Okta redeployed the feature rollout and a manual workaround guide was made available to impacted customers. All functionality and normal processing resumed once redeployment was complete at 8:35am PST February 12th. Preventative Actions: Okta will work to improve our monitoring system in order to ensure cache invalidation does not disrupt deployment sequencing during future releases. Okta will modify the feature rollout system to account for the cache invalidation timeout. Duration (# of minutes): 993 minutes

Read the full incident report →

Started Jan 15, 2025, 07:06 PM UTC· resolved Jan 24, 2025, 07:04 AM UTC

1. resolved Jan 15, 2025, 07:06 PM UTC

   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. Affected cells: okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:11

Read the full incident report →

Started Jan 14, 2025, 05:31 PM UTC· resolved Jan 23, 2025, 12:32 AM UTC

1. resolved Jan 14, 2025, 05:31 PM UTC

   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. Affected cells: okta.com:8

2. resolved Jan 22, 2025, 11:52 PM UTC

   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.

Read the full incident report →

Started Jan 09, 2025, 07:32 PM UTC· resolved Feb 24, 2025, 07:21 PM UTC

1. resolved Jan 09, 2025, 07:32 PM UTC

   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. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, okta.com:15, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Jan 16, 2025, 02:42 AM UTC

   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.

Read the full incident report →

Started Dec 13, 2024, 02:47 PM UTC· resolved Sep 10, 2025, 07:52 PM UTC

1. resolved Dec 13, 2024, 02:47 PM UTC

   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. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, okta.com:15, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Dec 13, 2024, 03:00 PM UTC

   Okta teams have become aware of disruption affecting customers in all cells. During this time, customer admins may be unable to access the Okta Help Center, and users may see HTTP 429 errors when attempting to log in. Okta teams are investigating and working to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. resolved Dec 13, 2024, 03:33 PM UTC

   Okta Engineering has isolated the issue, and Okta teams have made DNS changes to mitigate the disruption. Customer admins should begin to have access to the Okta Help Center, and users should stop seeing HTTP 429 errors as DNS continues to propagate. We are seeing the error rates subside, and we will continue to monitor the situation. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. resolved Dec 13, 2024, 03:45 PM UTC

   An issue impacting user login has been resolved. Our monitoring shows a return to normal conditions, and we will continue to monitor for any further errors. Additional root cause information will be available within 5 business days.

5. resolved Dec 20, 2024, 10:58 PM UTC

   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: Beginning on December 13th at 4:47AM PT, Okta became aware of customer reports regarding issues related to authentication and access, at which time the response teams began investigating the incident. During this time, customer admins in all commercial and FedRamp Moderate cells were unable to login to the Okta Help Center via login.okta.com. Additionally, users of embedded and custom browsers may have experienced error messages impacting log in flows in certain cases. Root Cause Summary: Okta Engineering determined that the root cause of the issue was due to a DNS record deletion of a reserved subdomain that was executed as part of automated resource cleanup processes which began at 2:01AM PT. Remediation Steps: At 7:07AM PT, the source of the error was identified and Okta engineering restored the DNS record at 7:15AM PT. At 7:25AM PT all processing had returned to normal. After determining that the clean up process was the source of the deletion, Okta engineering disabled it at 8:42AM PT. Preventative Actions: Certain cleanup operations have been paused until additional protections are put in place, including protecting reserved DNS records. In order to prevent similar incidents from happening again, Okta is addressing the following: Add stronger protections and enhanced monitoring around reserved DNS records in clean-up operations Updates to our monitoring and runbooks for login.okta.com service issues In the event that Okta Help Center is not available, customers can use the relevant support number found at: https://www.okta.com/contact/. When calling in, they will be asked for their Customer Support Account ID for caller verification.

Read the full incident report →

Started Dec 11, 2024, 06:32 PM UTC· resolved Sep 10, 2025, 07:51 PM UTC

1. resolved Dec 11, 2024, 06:32 PM UTC

   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. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, okta.com:8, okta.com:16

2. resolved Dec 11, 2024, 07:41 PM UTC

   Okta's Engineering Team has identified an issue affecting end-user and admin login and has taken remediation steps on affected cells. We are currently seeing an improvement in login success rates and will continue to monitor for full recovery.

3. resolved Dec 11, 2024, 07:50 PM UTC

   The login issue for all impacted Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor for any further errors. Additional root cause information will be available within 5 Business days.

4. resolved Dec 18, 2024, 11:59 PM UTC

   We sincerely apologize for any impact this incident has caused to you, your business, and your customers. At Okta trust and transparency are our top priorities. Outlined below are the facts regarding this incident. We are committed to implementing improvements to the service to prevent future occurrences of this kind of incident. Detection and Impact: On December 11th at 10:42AM PT, Okta internal monitoring alerted on-call responders regarding an issue across cells OK1 and EU1, and later on, limited impact in OK5, OK8, and OK16. During this time, some users were unable to load the Okta Sign In Widget, preventing authentication actions. Some admins were unable to open support cases unless they had an active session within the Okta Help Center. Existing sessions for end users and admins continued to operate normally. All other Okta products and services continued to function as designed. Root Cause Summary: The Okta engineering team was attempting to preemptively mitigate an identified risk in an upcoming version. While the change followed all processes for such changes, it was applied incorrectly ahead of the deployment causing the login page to reference an unavailable version of the Okta Sign in Widget in impacted production cells. For per-environment timelines, please review the specific timelines below. Timelines: OK1 10:32AM - 11:08AM PT 36 minutes [SIW Gen2] OK1 10:32AM - 11:15AM PT 43 minutes [SIW Gen3] EU1 10:40AM - 11:15AM PT 35 minutes [SIW Gen2] EU1 10:40AM - 11:18AM PT 38 minutes [SIW Gen3] OK8 11:01AM - 11:25AM PT 24 minutes [SIW Gen 2] OK8 11:01AM - 11:30AM PT 29 minutes [SIW Gen 3] OK16 10:59AM - 11:23AM PT 24 minutes [SIW Gen 2] OK5 10:47AM - 11:47AM PT 60 minutes [SIW Gen 2] Remediation Steps: Upon receiving automated alerts and support cases, Okta began diagnosing the incident and discovered the root cause at 10:58AM PT. At that time, the team started incrementally remediating the issue. The team rolled back the change across all impacted environments by 11:47AM PT. Preventative Actions: In order to prevent similar incidents from happening again, Okta has immediately addressed the following: Updated controls and enhanced approval flows for configuration changes Enhanced monitoring and alerting for content load errors for faster detection and response Duration (Minutes): 78

Read the full incident report →

Started Nov 19, 2024, 07:56 PM UTC· resolved Sep 10, 2025, 07:48 PM UTC

1. resolved Nov 19, 2024, 07:56 PM UTC

   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. Affected cells: okta-emea.com:1, okta.com:1, okta.com:2, okta.com:3, okta.com:4, okta.com:6, okta.com:7, oktapreview.com:1, oktapreview.com:2, okta.com:8, okta.com:9, okta.com:11, okta.com:12, oktapreview.com:3, okta.com:14, okta.com:16, okta.com:17

2. resolved Nov 19, 2024, 08:27 PM UTC

   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.

3. resolved Nov 19, 2024, 09:22 PM UTC

   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.

4. resolved Nov 19, 2024, 09:36 PM UTC

   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.

5. resolved Nov 25, 2024, 11:05 PM UTC

   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.

Read the full incident report →

Started Nov 15, 2024, 03:02 AM UTC· resolved Sep 10, 2025, 07:51 PM UTC

1. resolved Nov 15, 2024, 03:02 AM UTC

   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. Affected cells: okta.com:6

2. resolved Nov 15, 2024, 04:38 AM UTC

   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.

3. resolved Nov 23, 2024, 12:25 AM UTC

   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 November 14th, at 6:14 pm PST, Okta was alerted to an issue where requests to US Cell OK6 from a specific geo location may have experienced increased errors and slow response times, and may have received HTTP 503 error messages. Root Cause Summary Based on our investigation and findings, the root cause of this issue was due to a configuration error resulting from a software deployment by our 3rd party service provider. 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 US Cell OK6 by 7:16 pm PST on November 14th. Preventative Actions Okta plans to continue to work with our 3rd party service provider to monitor and detect georegional issues faster and have added new guidance to the operational processes further to improve time to service recovery.

Read the full incident report →

Started Oct 28, 2024, 01:15 PM UTC· resolved Sep 10, 2025, 07:48 PM UTC

1. resolved Oct 28, 2024, 01:15 PM UTC

   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. Affected cells: okta.com:14

2. resolved Oct 28, 2024, 02:59 PM UTC

   Okta's Engineering team has become aware of an import and update issue affecting customers in OK14. During this time, customers in OK14 may experience imports and updates that progress very slowly. Okta's Engineering team is investigating and working to mitigate the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. resolved Oct 28, 2024, 03:32 PM UTC

   Okta Engineering continues to investigate and work to mitigate import and update issues affecting customers in OK14. During this time, customers in OK14 may experience imports and updates that progress very slowly and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

4. resolved Oct 28, 2024, 04:00 PM UTC

   Okta Engineering has identified the potential cause of the issue and continues to work towards mitigating the disruption. Customers in OK14 may experience imports and updates that progress very slowly, and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

5. resolved Oct 28, 2024, 04:27 PM UTC

   Okta Engineering continues to work towards mitigating the disruption. Customers in OK14 may experience imports and updates that progress very slowly, and Okta Workflows initiated by Okta events and delegated workflows in FL14 may fail to progress. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. resolved Oct 28, 2024, 04:46 PM UTC

   Okta continues to monitor the current situation with the import and update delays in OK14. Our monitoring shows that import and update throughput is improving and delays are reducing. Our next update will be in 30 minutes or sooner if additional information becomes available.

7. resolved Oct 28, 2024, 05:18 PM UTC

   An issue impacting import and update performance in OK14 has been addressed. Additional root cause information will be available within 5 Business days.

8. resolved Nov 04, 2024, 11:25 PM UTC

   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 October 28th at 5:06 AM (PT), Okta was alerted that a few customers experienced delays related to imports in US Cell 14. During this time customers may have observed delayed imports as a result, delays in user activation, provisioning, password sync and additional async tasks At 9:38am(PT) task processing in the cell was restored to normal processing times. Root Cause Summary This issue was a result of a build up of both active and queued asynchronous tasks. Under heavy load of these tasks, the scheduler dequeued records too slowly and created a large backlog. This large backlog resulted in scheduling delays of tasks such as imports. Remediation Steps Okta Engineering scaled out for additional processing capacities, and tuned the dequeuing parameters to pull more records from the queue. These actions successfully addressed the issue, and all imports returned to normal processing levels. Preventative Actions Okta Engineering is reviewing and updating alerting, making improvements to address tasks queuing, and updating logging to better identify future issues related to queueing. Total Duration Total Duration (Minutes): 271 Actual Time: 5:07am PT - 9:38am PT

Read the full incident report →