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.
Posted Mar 05, 2026 - 15:05 UTC
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.
Posted Mar 05, 2026 - 14:39 UTC
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.
Posted Mar 05, 2026 - 14:04 UTC
This incident affects: Auth0 Europe (PROD) (User Authentication, Machine to Machine Authentication), Auth0 Australia (PROD) (User Authentication, Machine to Machine Authentication), Auth0 US (PROD) (User Authentication, Machine to Machine Authentication), Auth0 US-3 (PROD) (User Authentication, Machine to Machine Authentication), Auth0 JP-1 (PROD) (User Authentication, Machine to Machine Authentication), Auth0 EU-2 (PROD) (User Authentication, Machine to Machine Authentication), Auth0 US-4 (PROD) (User Authentication, Machine to Machine Authentication), Auth0 UK-1 (PROD) (User Authentication, Machine to Machine Authentication), Auth0 CA-1 (PROD) (User Authentication, Machine to Machine Authentication), and Auth0 US-5 (PROD) (User Authentication, Machine to Machine Authentication).