Auth0
Auth0 is operational
History
Incidents in 90 days
10
Days with an incident
10
Median duration
43 min
Longest incident
17 h 32 min
Components
114Auth0 Europe (PROD)
Auth0 Australia (PROD)
Aug 6, 2026
Services have been restored. A root cause analysis (RCA) will be posted here within 14 business days. We sincerely apologize for the impact this had on you and your users.status.auth0.com
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2026-08-06\_-\_Increased\_Error\_Rates\_on\_Support\_Portal\_SSO\_Login.pdf](https://cdn.auth0.com/blog/2026-08-06_-_Increased_Error_Rates_on_Support_Portal_SSO_Login.pdf)status.auth0.com
Maintenance
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=auth0Go from tracking outages to fixing production issues with Polylane.
Try Polylane