Elevated Errors on US-1 Public Cloud
Auth0 reported elevated errors on US-1 Public Cloud that affected User Authentication and Machine to Machine Authentication. Auth0 manually scaled backend resources and monitored the environment. Auth0 states that the incident is resolved and that it lasted about 64 minutes.
State
Resolved
Started
Lasted
1 h 4 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
21 min 33%
Monitoring
43 min 67%
Updates
Times in UTCAs posted by Auth0
This event was self-resolved. To provide additional resiliency, we manually scaled backend resources. After monitoring the environment to ensure stability, we consider this incident resolved. Authentication services are functioning as expected. We apologize for the impact that this event has caused on your users. A Root Cause Analysis detailing this event will be shared within 7 business days.
Previously, users would have experienced issues with authentication functionality. Authentication flows are operating normally at this time and the issue is mitigated. We are monitoring the US-1 Public Cloud environment to ensure stability before considering this event resolved.
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.
Affected components
4Auth0 in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
9
Median duration
37 min
This incident
1.7× the median
Other Auth0 incidents
All incidentsAuth0·Third-Party Outage Impacting US-1 Public Cloud
After monitoring the affected environments to ensure stability, we confirm that previously affected services have been restored following the fixes deployed by our third-party service provider. A root cause analysis (RCA) will be posted here within 10 business days. We sincerely apologize for the impact this had on you and your users.
Auth0·Elevated Errors on Multiple Public Cloud Environments
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2026-10-14\_-\_Third-Party\_Outage\_Impacting\_Public\_and\_Private\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/2026-10-14_-_Third-Party_Outage_Impacting_Public_and_Private_Cloud_Environments.pdf)
Auth0·Elevated Errors on US-4 Public Cloud
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-10-09_-_Elevated_Service_Errors_on_US-4_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-10-09_-_Elevated_Service_Errors_on_US-4_Public_Cloud_Environment.pdf)
Auth0·Elevated Errors on US-5 Public Cloud
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-09-30_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-09-30_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf)
Auth0·We have detected an issue.
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-09-16_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-09-16_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf)
Follow Auth0
Your coding agent knows when Auth0 is down, and tells you when a failure is theirs, not yours. You can also get Auth0 incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "auth0" and tell me if Auth0 has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=auth0/feed subscribe https://outages.live/feed.xml?providers=auth0FAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane