Auth0 Outage History

Auth0 is up right now

Pingoru has recorded 27 incidents for Auth0: 27 in the last 12 months and 10 in the last 90 days.

Source: status.auth0.com

27incidents recorded
27last 12 months
10last 90 days
10 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Auth0 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026413 of 720 (2%)
May 20261128 of 744 (17%)
June 202654 of 720 (1%)
July 202623 of 744 (0%)
August 2026320 of 744 (3%)
September 202632 of 720 (0%)
October 202651 of 744 (0%)
November 202600 of 114 (0%)

Incidents, newest first

Major February 22, 2026 Elevated Errors on US-3 Public Cloud 2h 10m Auth0 US-3 (Production) (Authentication), Auth0 US-3 (Production) (Machine to Machine)

Started Feb 22, 2026, 04:42 PM UTC· resolved Feb 22, 2026, 06:52 PM UTC

  1. investigating Feb 22, 2026, 04:26 PM UTC

    We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

  2. identified Feb 22, 2026, 04:42 PM UTC

    Our investigation has determined that a surge in unexpected traffic is consuming an inordinate amount of resources on the affected Public Cloud environment. To return services to normal levels we're taking mitigating steps to resolve impact. We will continue to update as our status progresses.

  3. identified Feb 22, 2026, 04:58 PM UTC

    Our action to address the unexpected traffic to mitigate the issue did not fully recover service functionality. Error rates still remain elevated on the affected environment. We're extending our investigation to other potential root causes. We will continue to update as our status changes.

  4. identified Feb 22, 2026, 05:31 PM UTC

    Our investigation into this event is ongoing. Error rates continue to remain elevated at this time. We're inspecting error logs for potential insights into root cause. Further updates will be provided as our investigation progresses.

  5. identified Feb 22, 2026, 06:09 PM UTC

    We're continuing to analyze logs from the resources that support the impacted environment, which indicate server and query failures. Error rates continue to remain elevated on the Public Cloud environment. We'll continue to provide updates as our status changes.

  6. monitoring Feb 22, 2026, 06:41 PM UTC

    We have implemented mitigating actions and are observing a reduction of errors. We're monitoring the environment to ensure stability and that there is no recurrence of impact. The full root cause of the event is still undergoing investigation. We'll continue to update as we obtain more information.

  7. resolved Feb 22, 2026, 06:52 PM UTC

    After monitoring, we've observed that the environment has remained stable. Services have been restored and authentication is functioning as expected. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.

  8. resolved Mar 05, 2026, 05:04 PM UTC

    A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20260222_-_Authentication_Errors_on_the_US-3_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20260222_-_Authentication_Errors_on_the_US-3_Public_Cloud_Environment.pdf)

Read the full incident report →

Minor February 20, 2026 Management Service Disruption on Multiple Public Cloud Environments 2d 19h Auth0 US-1 (Production) (Management API), Auth0 US-3 (Production) (Management API), Auth0 US-4 (Production) (Management API), Auth0 US-5 (Production) (Management API)

Started Feb 20, 2026, 09:00 PM UTC· resolved Feb 23, 2026, 04:30 PM UTC

  1. investigating Feb 20, 2026, 09:00 PM UTC

    We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

  2. identified Feb 23, 2026, 02:30 PM UTC

    Services have been restored for a subset of Public Cloud customers. Restoration efforts are ongoing for full recovery. We will continue to provide updates as our status changes.

  3. identified Feb 23, 2026, 03:30 PM UTC

    Additional Public Cloud environments are seeing restoration of service. Our efforts towards full restoration is ongoing. We'll continue to provide updates as changes in status occur.

  4. resolved Feb 23, 2026, 04:30 PM UTC

    Services have been restored. A root cause analysis (RCA) will be posted here within 7 business days. We sincerely apologize for the impact this had on you and your users.

  5. resolved Mar 12, 2026, 01:25 AM UTC

    A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260302\_-\_Management\_Service\_Disruption\_on\_Multiple\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260302_-_Management_Service_Disruption_on_Multiple_Public_Cloud_Environments.pdf)

Read the full incident report →