Live

Auth0

Auth0 is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

10

Days with an incident

10

Median duration

43 min

Longest incident

17 h 32 min

Components

114

Auth0 Europe (PROD)

User Authentication Operational
90 days ago1 day with an incidentToday
Machine to Machine Authentication Operational
90 days ago1 day with an incidentToday
Multi-factor Authentication Operational
90 days agoNo incidentsToday
Management API Operational
90 days agoNo incidentsToday
Tenant Logs Operational
90 days agoNo incidentsToday
Email Delivery Operational
90 days agoNo incidentsToday
Other Operational
90 days ago1 day with an incidentToday
[DEPRECATED] Custom DB Connections & Rules Operational
90 days agoNo incidentsToday
[DEPRECATED] CDN (cdn.eu.auth0.com) Operational
90 days agoNo incidentsToday
[DEPRECATED] Custom Domains Operational
90 days agoNo incidentsToday
[DEPRECATED] Search API v2 Operational
90 days agoNo incidentsToday
[DEPRECATED] Search API v3 Operational
90 days agoNo incidentsToday
Auth0 Dashboard Operational
90 days agoNo incidentsToday

Auth0 Australia (PROD)

User Authentication Operational
90 days agoNo incidentsToday
Machine to Machine Authentication Operational
90 days agoNo incidentsToday
Multi-factor Authentication Operational
90 days agoNo incidentsToday
Management API Operational
90 days agoNo incidentsToday
Tenant Logs Operational
90 days agoNo incidentsToday
Email Delivery Operational
90 days agoNo incidentsToday
Other Operational
90 days ago1 day with an incidentToday
[DEPRECATED] Custom DB Connections & Rules Operational
90 days agoNo incidentsToday
[DEPRECATED] CDN (cdn.au.auth0.com) Operational
90 days agoNo incidentsToday
[DEPRECATED] Custom Domains Operational
90 days agoNo incidentsToday
[DEPRECATED] Search API v2 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=auth0
Slack
/feed subscribe https://outages.cc/feed.xml?providers=auth0

Go from tracking outages to fixing production issues with Polylane.

Try Polylane