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)
The latest update from Auth0.
State
Resolved
Started
32 d ago
2026-09-30 20:32 UTC
Lasted
52 min
until 2026-09-30 21:24 UTC
Worst impact
Major outage
Timeline
6 updatesIdentified
42 min 81%
Monitoring
10 min 19%
Updates
Times in UTCAs posted by Auth0
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)
After monitoring the environment to ensure stability, we observe that services have been restored. Our investigation into origin of the event will continue, in collaboration with our third-party provider. 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.
We've observed that service error rates on the US-5 Public Cloud Environment have subsided and returned to baseline, marking a return to service functionality. The service disruption has been mitigated and we're monitoring the ensure stability. Meanwhile, our investigation is continuing and we're collaborating with our third-party provider's technical teams to identify and address the root cause of the issue within their hosted infrastructure.
We're actively investigating with our third-party provider regarding the latency discrepancies that we observe within their hosted infrastructure. Additionally, we're investigating an issue involving a high number of service connections causing exhaustion on backend resources. We'll continue to provide updates as we proceed to address the root cause of the service disruption.
We're continuing to investigate the service disruption on the US-5 Public Cloud Environment. We're assessing service metrics and logs to determine the source of the issue. We're evaluating a potential issue within infrastructure hosted by our third-party service provider. We'll provide further updates as our investigation progresses, and as changes in status occur.
We are currently investigating an incident that impacted our services. Users may experience issues with authentication functionality. 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
3Auth0 in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
10
Median duration
43 min
This incident
1.2× 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·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)
Auth0·Elevated Error Rates on Multiple Cloud Environments
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-09-01_-_Elevated_Errors_On_Multiple_Public_and_Private_Cloud_Environments.pdf](https://cdn.auth0.com/website/2026-09-01_-_Elevated_Errors_On_Multiple_Public_and_Private_Cloud_Environments.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.cc/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.cc/feed.xml?providers=auth0/feed subscribe https://outages.cc/feed.xml?providers=auth0FAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane