- Detected by Pingoru
- Jul 24, 2026, 07:30 AM UTC
- Resolved
- Jul 24, 2026, 01:57 PM UTC
- Duration
- 6h 27m
Affected: Core PlatformThird Party
Timeline · 2 updates
-
monitoring Jul 24, 2026, 07:30 AM UTC
At 3:55 AM PT on July 24th, 2026, the Okta Engineering team became aware of a a third-party incident occurred and affecting customers on OK7/OK14/OK12/OP3 cells of the environment. During this time customers on the impacted cell may experience timeout and not able to login. The issue was resolved at 4:25 AM PT and Okta continues to monitor as our monitoring shows a recovery to normal conditions. Affected cells: okta.com:7, okta.com:12, oktapreview.com:3, okta.com:14
-
monitoring Jul 24, 2026, 01:55 PM UTC
After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved. Additional root cause information will be available within five business days.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 02:15 PM UTC
- Resolved
- Jul 22, 2026, 05:17 PM UTC
- Duration
- 3h 2m
Affected: Workflows
Timeline · 5 updates
-
monitoring Jul 22, 2026, 03:14 PM UTC
Please be advised that our scheduled maintenance is currently still ongoing, and the Okta Engineering teams are actively engaged. During this extended window, customers may experience errors when logging in to Okta Workflows. We appreciate your patience as our teams work to complete this operation as quickly and safely as possible. To understand how this might impact your organization and to view recommended workarounds, please review our detailed support article: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US . We will provide further updates in 30 minutes, or sooner, as more information becomes available.
-
monitoring Jul 22, 2026, 03:49 PM UTC
Maintenance activity is still ongoing as we ensure the migration is completed safely and successfully. We will continue to share updates in 30 minutes or sooner, as they become available. In the meantime, please refer to the support article below for the latest guidance on workarounds and expected behaviors: https://support.okta.com/help/s/article/okta-workflows-cell-migration-expected-behaviors-and-workarounds?language=en_US
-
monitoring Jul 22, 2026, 04:19 PM UTC
We are now observing stable system performance following the migration activities. Our engineering teams remain actively engaged in monitoring all services. Core workflows are recovering, and customers should see continued improvements. We will provide our next update in 30 minutes, or sooner if new information becomes available.
-
resolved Jul 22, 2026, 04:59 PM UTC
After a period of stability and monitoring, we can now confirm that the service issue has been fully resolved. Additional root cause information will be available within five business days.
-
identified Jul 23, 2026, 02:15 AM UTC
The Workflows migration has extended beyond our anticipated completion and will now be completed at 4:00 PM UTC. We apologize for any inconvenience and will provide further updates as more 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
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2026, 01:32 AM UTC
- Resolved
- Jul 14, 2026, 01:52 AM UTC
- Duration
- 19m
Affected: Core Platform
Timeline · 1 update
-
investigating Jul 14, 2026, 01:32 AM UTC
This is just a test performed quarterly to ensure the tooling works. Affected cells: OK1
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 08:01 PM UTC
- Resolved
- Jul 21, 2026, 01:57 AM UTC
- Duration
- 7d 5h
Affected: Core Platform
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 07:40 PM UTC
- Resolved
- Jul 27, 2026, 07:00 PM UTC
- Duration
- 19d 23h
Affected: Workflows
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 02:00 PM UTC
- Resolved
- Jul 07, 2026, 12:53 PM UTC
- Duration
- 10d 22h
Affected: Core Platform
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 09:22 PM UTC
- Resolved
- Jul 09, 2026, 02:41 PM UTC
- Duration
- 16d 17h
Affected: Core Platform
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:45 AM UTC
- Resolved
- Jun 10, 2026, 02:19 AM UTC
- Duration
- 7d 16h
Affected: Single Sign-On
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 08:07 PM UTC
- Resolved
- May 08, 2026, 02:51 AM UTC
- Duration
- 7d 6h
Affected: Single Sign-On
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Apr 26, 2026, 02:05 AM UTC
- Resolved
- Apr 26, 2026, 02:14 AM UTC
- Duration
- 9m
Affected: Overall
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 04:08 PM UTC
- Resolved
- May 06, 2026, 07:14 AM UTC
- Duration
- 13d 15h
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17okta.com cell 18okta.com cell 19oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3Third Party
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 06:30 PM UTC
- Resolved
- Apr 21, 2026, 11:16 PM UTC
- Duration
- 8d 4h
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17okta.com cell 18okta.com cell 19oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3OIG Access Requests
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 08:42 AM UTC
- Resolved
- Apr 15, 2026, 11:37 PM UTC
- Duration
- 30d 14h
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17okta.com cell 18okta.com cell 19oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3Third Party
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 06:40 PM UTC
- Resolved
- Apr 15, 2026, 11:36 PM UTC
- Duration
- 33d 4h
Affected: okta-emea.com cell 1okta.com cell 1Core Platform
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 10:41 AM UTC
- Resolved
- Feb 11, 2026, 06:45 PM UTC
- Duration
- 7d 8h
Affected: okta.com cell 9Core Platform
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 03:30 PM UTC
- Resolved
- Apr 15, 2026, 11:37 PM UTC
- Duration
- 77d 8h
Affected: okta.com cell 9Third Party
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 06:55 PM UTC
- Resolved
- Jan 30, 2026, 10:35 PM UTC
- Duration
- 8d 3h
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17okta.com cell 18okta.com cell 19oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3Core PlatformThird Party
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 06:10 PM UTC
- Resolved
- Jan 26, 2026, 06:34 PM UTC
- Duration
- 7d
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3Core PlatformThird Party
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Dec 26, 2025, 08:30 AM UTC
- Resolved
- Jan 03, 2026, 01:52 AM UTC
- Duration
- 7d 17h
Affected: okta.com cell 6Core Platform
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Dec 14, 2025, 11:00 AM UTC
- Resolved
- Dec 23, 2025, 02:50 PM UTC
- Duration
- 9d 3h
Affected: okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 7okta.com cell 9okta.com cell 12okta.com cell 14oktapreview.com cell 3Core Platform
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 07:42 AM UTC
- Resolved
- Dec 18, 2025, 02:29 AM UTC
- Duration
- 7d 18h
Affected: okta.com cell 9Core Platform
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 08:31 AM UTC
- Resolved
- Dec 12, 2025, 04:32 PM UTC
- Duration
- 8d 8h
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17Core Platform
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 01:15 PM UTC
- Resolved
- Jan 26, 2026, 08:26 PM UTC
- Duration
- 54d 7h
Affected: okta.com cell 7Core Platform
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 06:34 PM UTC
- Resolved
- Nov 25, 2025, 12:21 AM UTC
- Duration
- 7d 5h
Affected: okta.com cell 14Core Platform
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 07:40 PM UTC
- Resolved
- Jan 26, 2026, 08:25 PM UTC
- Duration
- 75d
Affected: okta-emea.com cell 1okta.com cell 1okta.com cell 2okta.com cell 3okta.com cell 4okta.com cell 6okta.com cell 7okta.com cell 8okta.com cell 9okta.com cell 11okta.com cell 12okta.com cell 14okta.com cell 16okta.com cell 17oktapreview.com cell 1oktapreview.com cell 2oktapreview.com cell 3MFAThird Party
Timeline · 4 updates
Read the full incident report →