Auth0 outage history

Auth0 carried out planned maintenance affecting Production across multiple regions, including CA-1, EU-1, EU-2, JP-1, UK-1, US-1, US-3, US-4, and US-5. During the maintenance window, some users may have experienced intermittent access or authentication interruptions. The status page indicates the affected components entered maintenance and later returned to normal operation, with the window starting at 3:16 PM UTC and concluding at 6:01 AM UTC, for a total duration of about 14 hours and 45 minutes.

Auth0 carried out scheduled maintenance across production regions CA-1, EU-1, EU-2, JP-1, UK-1, US-1, US-3, US-4, and US-5. The maintenance window began at 2:11 PM UTC and concluded at 6:06 AM UTC, spanning roughly eight days. During this period, production services in the affected regions entered maintenance mode as part of the planned operation.

All listed production components were returned to normal operation after the window completed, per Auth0's status updates. This was a planned maintenance event intended to improve reliability and performance across Auth0 production environments.

Auth0 experienced an outage beginning at Oct 23, 2026 5:41 PM UTC when the US-1 Production environment went down amid a third-party outage impacting the US-1 public cloud. This disruption interrupted authentication and login flows for applications relying on Auth0 in that region. A planned maintenance window followed at 5:47 PM UTC, reflecting Auth0's response to the disruption. By Oct 27, 2026 2:01 PM UTC, all listed Production regions had been brought back online: AU / Production, CA-1 / Production, EU-1 / Production, EU-2 / Production, JP-1 / Production, UK-1 / Production, US-1 / Production, US-3 / Production, US-4 / Production, and US-5 / Production. Users in these regions would have experienced login failures or degraded sign-in experiences during the outage, and authentication services resumed as each region came back online.

Auth0 began a planned maintenance window across production regions starting at Oct 19, 2026 4:36 PM UTC. The work progressed in multiple regions, but on Oct 23, 2026 5:41 PM UTC the US-1 Production region entered an outage attributed to a third-party issue impacting the US Public Cloud. Other regions remained under maintenance during this period while teams investigated and prepared recovery. Users relying on Auth0 authentication in the US-1 region likely experienced login or token-related issues during this window. The disruption was centered on US-1 and did not reflect a global Auth0 outage; maintenance continued in the other listed regions until recovery.

Auth0 experienced a regional outage in the US-4 Production environment, affecting authentication for services relying on that region. The incident began at Oct 9, 2026 7:02 PM UTC when the US-4 Production component transitioned to down, followed by a status update to Monitoring at 7:06 PM UTC as engineers investigated the issue.

Recovery occurred when the US-4 Production component returned to up at Oct 9, 2026 7:31 PM UTC, marking a resolution after about thirty minutes. The impact was contained to the US-4 Production environment, with authentication services in that region restored to normal.

Auth0 faced an outage in its US-5 Public Cloud Production environment, causing login failures for users within that region. The issue began at 8:16 PM UTC as elevated errors were observed on the US-5 Public Cloud. A user in Georgia reported login issues around 8:30 PM UTC, indicating tangible impact for affected customers.

Status page updates show a progression from Investigating to Identified and then Monitoring, with the US-5 Production component returning to normal by 9:36 PM UTC. Recovery followed a little over an hour of degraded authentication availability across the region, after which services stabilized.

Auth0 reported a brief degradation of the Tenant Logs service in the EU-2 Public Cloud, affecting the Production environment. Starting 12:36 AM UTC, users in that region may have experienced intermittent issues with accessing or streaming logs while the service was degraded.

The issue was resolved by 12:41 AM UTC, with the EU-2 Production component returning to normal. The impact was localized to EU-2 and did not show evidence of global disruption.

Auth0 experienced a brief outage affecting the US-5 Production authentication environment. The incident began at 3:11 AM UTC when the status page moved from up to down and the team announced Investigating. Authentication requests and token issuance in the US-5 Production environment could have failed during the disruption.

About 50 minutes later, at 4:01 AM UTC, the US-5 / Production component returned to normal and Auth0 resumed normal operation. Status updates then indicated recovery and the service returned to an up state. The incident was limited to the US-5 Production environment with no ongoing issues after restoration.

Auth0 performed a planned DNS change across the auth0.com domain as part of resiliency work, affecting production regions EU-2, CA-1, AU, JP-1, UK-1, US-3, US-4, US-5, and EU-1. The maintenance window began at Sep 2, 2026 3:26 PM UTC and concluded with all regions returning to the up state by Sep 8, 2026 4:01 AM UTC. The work was described as scheduled with no customer impact expected, and subsequent updates indicated a clean progression from maintenance back to up across production components.

Auth0 experienced a brief outage affecting authentication across multiple production regions. The incident began at Sep 1, 2026 3:56 PM UTC when the service flagged elevated error rates across six regions: EU-2, US-1, UK-1, US-3, US-5, and EU-1. Users and applications relying on Auth0 likely faced authentication errors or timeouts during the disruption. By 4:11 PM UTC, the affected regions had returned to normal, marking the incident as resolved after roughly 15 minutes.

Auth0’s status updates show a prompt investigation and remediation, with services restored across the listed regions. The outage appeared confined to production environments named above, with recovery occurring within the same approximate window and no further degradation reported after the fix.