Auth0 reported "Elevated Errors on US-4 Public Cloud" on its status page at 2026-10-09 19:01 UTC.

When did the incident start and end?

It started at 2026-10-09 19:01 UTC and ended at 2026-10-09 19:13 UTC. It lasted 12 min.

How do I get alerts for Auth0?

Subscribe to the Auth0 live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Auth0. outages.live reads it every few minutes and keeps every update.

Auth0Incident · 2026-10-09 19:01 UTC

Elevated Errors on US-4 Public Cloud

Q: What is affected?

Auth0 lists these components: User Authentication, Machine to Machine Authentication, Management API.

ResolvedOfficial update

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)

The latest update from Auth0.

State

Resolved

Started

23 d ago

2026-10-09 19:01 UTC

Lasted

12 min

until 2026-10-09 19:13 UTC

Worst impact

Partial outage

Timeline

4 updates

19:0119:0419:0719:1019:13

Partial outageUpdate postedTimes in UTC

Monitoring

12 min 100%

Updates

Times in UTC

As posted by Auth0

Postmortem2026-10-15 19:06 UTC

Resolved2026-10-09 19:13 UTC

After monitoring the environment to ensure stability, we confirm that services have been restored. Our investigation into the full root cause will continue, as we confirm the source of the issue. 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.

Monitoring2026-10-09 19:01 UTC

We've identified a load spike event that caused elevated service errors on the US-4 Public Cloud environment. These errors have subsided after our autoscaling mechanisms triggered. The issue has self-resolved, and we're monitoring the environment to ensure stability. We'll provide further updates with new information or when changes in status occur.

Investigating2026-10-09 19:00 UTC

We're currently investigating an incident that impacted our services. This event impacts authentication and Management API 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

User AuthenticationMachine to Machine AuthenticationManagement API

Auth0 in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

43 min

This incident

72% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

17 h 32 min

median 43 min

90 days agoToday

Other Auth0 incidents

All incidents

Auth0·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.

Resolvedresolved 9 d ago

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)

Resolvedresolved 19 d ago

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)

Resolvedresolved 32 d ago

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)

Resolvedresolved 47 d ago

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)

Resolvedresolved 61 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane