Auth0's US-5 Public Cloud environment logged elevated authentication errors for 1h 23m on 30 September 2026. Auth0 traced the problem to its own third-party infrastructure provider, not to anything in your setup.
Started
20:14 UTC
Duration
Lasted 1h 23m
Source
IsDown
Next time
Auth0 is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: US-5
What happened?
Auth0 posted that it was investigating an incident affecting authentication functionality on the US-5 Public Cloud Environment starting at 20:11 UTC. By 20:33 Auth0 said it was evaluating a potential issue within infrastructure hosted by a third-party service provider, rather than in Auth0's own code. At 20:55 the update narrowed further: Auth0 described latency discrepancies within that third-party provider's hosted infrastructure, combined with a high number of service connections exhausting backend resources. By 21:15 Auth0 reported that error rates on US-5 had subsided and returned to baseline, and moved the incident to monitoring while it kept working with the third-party provider's technical teams on root cause. The incident ran from 20:14 to 21:37 UTC, a duration of 1h 23m, and only the one component, US-5, was listed as affected. No user reports were filed during this window on the record provided. Auth0 published four updates in total, and no further update or post-mortem has followed the 21:15 monitoring note. Over the past 90 days Auth0 has logged 9 incidents with a median duration of 1 hour 16 minutes, so this one sits close to its recent norm in length. Across all time Auth0's history shows 226 incidents at a rate of 4.5 per month.
Learning
Auth0's own account points to a dependency failure one layer below its application code, in infrastructure run by a third-party provider that Auth0 itself relies on. That is the kind of fault an uptime check against your own login pages or API endpoints often will not catch cleanly, because the symptom shows up as elevated error rates and connection exhaustion rather than a flat outage. UptimeRobot's 30-day figures for Auth0 show 3 incidents, all resolved, with a median duration of 48 minutes, a separate measurement from Auth0's own incident log and not in conflict with it. Both readings can be correct at once: your endpoint can look fine between failed requests while the underlying provider is genuinely degraded. This is exactly the shape of failure worth recognising, intermittent auth errors tied to backend resource exhaustion rather than a hard down. Your own monitoring tells you about your half of the system. UptimeRobot watches the provider's half too, so next time you know which side broke without guessing.
