Okta incident

Okta Admin Console Issue Viewing Users

Major Resolved View vendor source →
Started
Mar 13, 2026, 06:40 PM UTC
Resolved
Apr 15, 2026, 11:36 PM UTC
Duration
33d 4h
Detected by Pingoru
Mar 13, 2026, 06:40 PM UTC

Affected components

okta-emea.com cell 1okta.com cell 1Core Platform

Update timeline

  1. resolved Mar 13, 2026, 06:40 PM UTC

    At 10:30 AM PT on 3/13/2026, the Okta Engineering team became aware of an impact to the Okta Admin Console. affecting customers on OK1 and EU1 cells. During this time, customers may not be able to view all the users. The Okta Engineering team is investigating and working to mitigate the issue as soon as possible. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.

  2. resolved Mar 13, 2026, 06:48 PM UTC

    At around 11:20AM PT, Okta Engineering has confirmed that the issue has been resolved in both cells, EU1 and OK1. An RCA will be provided in five business days. We apologize for any inconvenience this may have caused.

  3. resolved Mar 20, 2026, 08:35 PM UTC

    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 kind. Detection and Impact On March 13, 2026, at 10:49 AM PT, Okta detected a service degradation that prevented some customers on the OK1 and EU1 cells from performing directory operations, viewing or searching for users, groups, and devices in the Okta Admin Console. Customers may have experienced "Invalid search query" messages or 5xx errors. This issue also affected several API endpoints related to users, groups, and devices, which may have impacted customer integrations relying on this functionality. End-user authentication was not impacted. Root Cause Summary The root cause of this incident was a planned configuration change that exposed a bug in the underlying service, resulting in system errors and disrupting both directory-based APIs. Remediation Steps Upon detection, Okta's engineering teams initiated incident response procedures. Once the problematic configuration change was identified as the source of the errors, it was immediately reverted. After the reversion was applied and verified, full functionality was restored to all impacted customers. Preventative Actions Okta is taking steps to prevent future occurrences of this kind, including enhancing our testing processes, hardening and improving our configuration rollout strategy, and upgrading our monitoring and alerting systems for enhanced detection. Start Time: 03/13/2026 10:17 AM PT End Time: 03/13/2026 11:21 AM PT Duration (# of minutes): 64

Looking to track Okta downtime and outages?

Pingoru polls Okta's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Okta reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Okta alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Okta for free

5 free monitors · No credit card required