Authentication Services Impacted on Public Cloud Environment
Current Status: Resolved | Last updated at March 19, 2026, 17:48 UTC
Affected environments: EU-1 Production, AU Production, US-1 Production, US-3 Production, JP-1 Production, EU-2 Production, US-4 Production, UK-1 Production, CA-1 Production, US-5 Production
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
History for this incident
Resolved
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.
Monitoring
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.
Identified
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.
Investigating
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.