Auth0 Outage History

Auth0 experienced elevated errors across multiple public cloud environments including US, EU, AU, UK, JP, and CA regions for 20 minutes. The incident impacted Auth0's authentication services across these global regions. The team investigated and mitigated the issue, though the specific root cause and resolution details were not detailed in the available updates.

Auth0 experienced a major incident with elevated errors across multiple public cloud environments, affecting 9 regions including US, EU, AU, UK, JP, and CA deployments. The service disruption lasted 12 minutes before being resolved.

Auth0's Support Center experienced a major disruption affecting all regions including US, EU, UK, Canada, Australia, and Japan. The outage lasted approximately 1.5 hours before service was restored. All Auth0 regional components were impacted during this incident.

Auth0 experienced a 4-minute service disruption affecting their Management Service across multiple public cloud environments (US-1, US-3, US-4, US-5). The incident impacted Auth0's core services, preventing customers from accessing management functionality. Service was gradually restored, with a subset of public cloud customers recovering first, followed by additional environments until full restoration was achieved.

Auth0's authentication services experienced a major incident across all global regions (US, EU, UK, Canada, Australia, and Japan) lasting over 11 days. The issue was identified as affecting customers using variables defined outside of their action method definition on runtime node18 or earlier, causing unexpected behavior in authentication workflows. The engineering team applied a fix and rolled it out across affected environments during scheduled maintenance windows to minimize further disruptions.

Auth0's US-4 Public Cloud Environment experienced intermittent session timeouts for 2.8 hours, causing users to be unexpectedly logged out of their sessions. The engineering team resolved the issue by performing infrastructure optimizations, including refining database configuration and scaling up backend capacity to handle traffic loads. The service has fully recovered and returned to normal operation.