Auth0 service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for auth0.com. Compare the regional responses with the problem you see in Auth0.
Find Auth0 help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
An Auth0 corporate-site check cannot validate your tenant's login domain, token endpoint or identity-provider connection.
The checker above requests auth0.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Auth0 action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse infrastructure checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Use the tenant/region and application involved in the failed login.
Open the website in your browser and compare it with the result above.
Open Auth0 help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Tenant region, connection/application identifier, timestamp and log/request ID; redact tokens and user credentials.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Auth0.
These are troubleshooting comparisons, not claims that Auth0 is currently experiencing a particular incident.
Record the tenant/custom domain and distinguish login-page loading from callback or token-exchange failure.
If you administer the tenant, correlate the failed attempt with its logs and the relevant regional status component.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Auth0 seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open auth0.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Auth0 issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Auth0 support.
Run the auth0.com check and compare its original timestamps and responses with your actual error. An Auth0 corporate-site check cannot validate your tenant's login domain, token endpoint or identity-provider connection.
Use the community buttons on this page to share whether the service works for you. For help from Auth0, use the official help/reporting resource linked above. Use the tenant/region and application involved in the failed login.
Record the tenant/custom domain and distinguish login-page loading from callback or token-exchange failure. If you administer the tenant, correlate the failed attempt with its logs and the relevant regional status component.
Tenant region, connection/application identifier, timestamp and log/request ID; redact tokens and user credentials.