Is Auth0 down?
No, Auth0 is not down.
Auth0’s status page reports no incidents, auth0.auth0.com and manage.auth0.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.auth0.com
- Reachable6 of 6 regionsAuth0 tenant (auth0.auth0.com) 6/6 · Auth0 dashboard 6/6
- Reports in the last hour0Normal
Auth0’s status page
From status.auth0.com. Read at
- US-1 (Production) US-1Operational
- US-3 (Production) US-3Operational
- US-4 (Production) US-4Operational
- US-5 (Production) US-5Operational
- EU-1 (Production) EU-1Operational
- EU-2 (Production) EU-2Operational
- AU (Production) AUOperational
- JP-1 (Production) JP-1Operational
Show all 10 components
- UK-1 (Production) UK-1Operational
- CA-1 (Production) CA-1Operational
Planned maintenance, : Planned Maintenance.
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 136 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (auth0.auth0.com)
By region
| Region | Auth0 tenant (auth0.auth0.com) auth0.auth0.com | Auth0 dashboard manage.auth0.com |
|---|---|---|
| N. Virginia us-east-1 | 200 · 113 ms | 302 · 110 ms |
| Oregon us-west-2 | 200 · 47 ms | 302 · 94 ms |
| Frankfurt eu-central-1 | 200 · 219 ms | 302 · 520 ms |
| Singapore ap-southeast-1 | 200 · 31 ms | 302 · 38 ms |
| Tokyo ap-northeast-1 | 200 · 141 ms | 302 · 43 ms |
| São Paulo sa-east-1 | 200 · 226 ms | 302 · 237 ms |
Two regions check Auth0 every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Auth0 ourselves since Oct 28, 2026. Earlier days come from its status page.
10 days with problems in the last 90 days.
Recent incidents
Incidents: 4 in the last 30 days and 9 in the last 90, lasting a median of 37 min.
- Third-Party Outage Impacting US-1 Public CloudMajor outage5 min
- Elevated Errors on Multiple Public Cloud EnvironmentsPartial outage30 min
- Elevated Errors on US-4 Public CloudPartial outage12 min
- Elevated Errors on US-5 Public CloudMajor outage52 min
- We have detected an issue.Partial outage49 min
- Elevated Error Rates on Multiple Cloud EnvironmentsMajor outage10 min
- We have detected an issue.Partial outage1 h 35 min
- Tenant Logs Service Impacted on EU-2 Public CloudDegraded37 min
- Tenant Logs and Group Memberships Impacted on US-5 Public CloudDegraded17 h 32 min
If Auth0 isn’t working for you
Auth0 is Okta's customer identity platform that apps use for login, sign-up, single sign-on and multifactor authentication.
Common Auth0 errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Too many requests. Check the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers. | A 429 from the Authentication API: an endpoint's rate limit was exceeded. | Your side | Retry with exponential backoff and check the rate-limit headers. Source |
429 Too Many Requests | Suspicious IP Throttling is blocking an IP address after too many failed logins or sign-ups. | Your side | Wait for the IP to be unthrottled, or adjust Attack Protection settings. Source |
Is it just you?
- If only some users fail to log in, check Attack Protection logs for throttled IPs or blocked accounts.
- Look at the tenant logs in the Auth0 dashboard for the exact error code of a failed login.
- Check status.auth0.com for your tenant's region.
- If your app's own login page fails but Auth0's dashboard works, check your app's callback and domain settings.
Alternatives to Auth0
Questions
You hit a rate limit or an IP was throttled by Suspicious IP Throttling. Check the rate-limit headers and Attack Protection settings.
Check status.auth0.com for incidents. If only some users or IP addresses fail, Attack Protection features such as Suspicious IP Throttling are a common cause.
Sources: auth0.com, auth0.com, status.auth0.com
Get alerted when Auth0 breaks your app.
If your product or your team depends on Auth0, its outage is your outage, and your users will blame you, not Auth0. Point a Site Qwality monitor at the Auth0 endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.