Auth0 incident

Elevated Errors on Public Cloud Environments

Auth0 experienced a critical incident on April 22, 2026 affecting Auth0 EU-1 (Production) (Authentication) and Auth0 EU-1 (Production) (Machine to Machine) and 1 more component, lasting 31m. The incident has been resolved; the full update timeline is below.

Started: Apr 22, 2026, 06:29 PM UTC
Resolved: Apr 22, 2026, 07:01 PM UTC
Duration: 31m
Detected by Pingoru: Apr 22, 2026, 06:29 PM UTC

Affected components

Auth0 EU-1 (Production) (Authentication)Auth0 EU-1 (Production) (Machine to Machine)Auth0 EU-2 (Production) (Authentication)Auth0 EU-2 (Production) (Machine to Machine)Auth0 AU (Production) (Authentication)Auth0 AU (Production) (Machine to Machine)Auth0 JP-1 (Production) (Authentication)Auth0 JP-1 (Production) (Machine to Machine)Auth0 UK-1 (Production) (Authentication)Auth0 UK-1 (Production) (Machine to Machine)

Update timeline

investigating Apr 22, 2026, 06:29 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.
resolved Apr 22, 2026, 07:01 PM UTC

Customers experienced service disruption due to a DNS misconfiguration that was inadvertently applied in preparation for infrastructure enhancement. This issue was resolved after the misconfiguration was manually corrected. We monitored the environment to ensure stability and confirmed that 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.
resolved May 07, 2026, 04:36 PM UTC

A root-cause analysis for this issue has been performed and is now available at:[https://cdn.auth0.com/blog/20260422\_-\_Elevated\_Errors\_on\_Public\_Cloud\_from\_DNS\_Resolution\_Failures.pdf](https://cdn.auth0.com/blog/20260422_-_Elevated_Errors_on_Public_Cloud_from_DNS_Resolution_Failures.pdf)