Auth0 incident

Authentication Services Impacted on Public Cloud Environment

Major Resolved View vendor source →

Auth0 experienced a major incident on March 5, 2026 affecting Auth0 US-1 (Production) (Authentication) and Auth0 US-1 (Production) (Machine to Machine) and 1 more component, lasting 10h 6m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2026, 02:04 PM UTC
Resolved
Mar 06, 2026, 12:10 AM UTC
Duration
10h 6m
Detected by Pingoru
Mar 05, 2026, 02:04 PM UTC

Affected components

Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-3 (Production) (Authentication)Auth0 US-3 (Production) (Machine to Machine)Auth0 US-4 (Production) (Authentication)Auth0 US-4 (Production) (Machine to Machine)Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)Auth0 EU-1 (Production) (Authentication)Auth0 EU-1 (Production) (Machine to Machine)

Update timeline

  1. investigating Mar 05, 2026, 02:04 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 Mar 05, 2026, 02:39 PM UTC

    Our Engineering team has investigated and we've identified the cause of the event. We're making progress on mitigating impact and have applied a fix to a subset of affected environments. After applying this fix, we're observing a successful recovery of our services. Customers using variables defined outside of their action method definition on runtime node18 or less may experience unexpected behavior. We will continue to monitor mitigation of the issue as we continue to roll this fix out across the remaining affected environments.

  3. monitoring Mar 05, 2026, 03:05 PM UTC

    Our Engineering team is monitoring this event, and we're applying the fix during approved scheduled release windows in order to minimize possible service disruptions. Customers using variables defined outside of their action method definition on runtime node18 or less may experience unexpected behavior. We'll provide another update as changes in status occur.

  4. resolved Mar 06, 2026, 12:10 AM 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 18, 2026, 04:41 AM UTC

    A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260304\_-\_Action\_State\_Persistence\_in\_All\_Regional\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260304_-_Action_State_Persistence_in_All_Regional_Public_Cloud_Environments.pdf)