Auth0 incident

Elevated Errors on Public Cloud Environments

Minor Resolved View vendor source →

Auth0 experienced a minor incident on April 28, 2026 affecting US-1 (Production) and US-3 (Production) and 1 more component, lasting 11h 31m. The incident has been resolved; the full update timeline is below.

Started
Apr 28, 2026, 10:00 AM UTC
Resolved
Apr 28, 2026, 09:32 PM UTC
Duration
11h 31m
Detected by Pingoru
Apr 28, 2026, 10:00 AM UTC

Affected components

US-1 (Production)US-3 (Production)US-4 (Production)US-5 (Production)EU-1 (Production)EU-2 (Production)AU (Production)JP-1 (Production)UK-1 (Production)CA-1 (Production)

Update timeline

  1. identified Apr 28, 2026, 10:00 AM UTC

    We're currently investigating a disruption to Auth0 Services on the Public Cloud environment. Our third-party Edge provider has confirmed an issue originating from within their services. This event specifically impacts customers who are utilizing self-managed custom domains for Authentication, MFA, and Management API. We're closely monitoring for progress from our provider following their investigation. We'll provide updates as we gather more information and as our status changes.

  2. resolved Apr 28, 2026, 09:32 PM UTC

    Our third-party Edge provider has reported that their service disruption has been mitigated within their environment. We've observed recovery for all previously affected Auth0 services and now see stability in the Public Cloud environment. After no further recurrence of the issue, we're now marking this incident as resolved. A root cause analysis (RCA) will be posted here within 14 business days. We sincerely apologize for the impact this had on you and your users.

  3. resolved May 08, 2026, 07:38 PM UTC

    A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260428\_-\_Increased\_Error\_Rates\_on\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260428_-_Increased_Error_Rates_on_Public_Cloud_Environments.pdf)