Auth0 Outage History

Uptime record, past incidents, and downtime history for Auth0.

Checking current status...
62.1% uptime over 58 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 6Apr 4

Monthly Uptime

Month Uptime Days Tracked Days with Issues
April 2026 100% 4 0
March 2026 38.7% 31 19
February 2026 87% 23 3

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 58 Days)

Feb 6 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

March 2026
Disruption to Auth0 Support Center
major

Started: Mar 17, 5:25 AM

monitoring
The Auth0 Support Center is now fully operational, and case creation functionality has been restored. We are continuing to monitor our systems to ensure ongoing stability. We sincerely apologize for any inconvenience this disruption may have caused.
Mar 17, 6:25 AM
identified
We are actively collaborating with our third-party provider to resolve the ongoing issues affecting the Auth0 Support Center. The Authentication and Management API are NOT impacted by this service disruption in the Support Center. If you are experiencing a production-critical impact on end-user authentications, please contact our support team immediately via our dedicated phone line.
Mar 17, 5:50 AM
investigating
We are aware of an issue with our provider, and access to support.auth0.com may not be available. We are working with our provider on mitigations and will provide an update as soon as it's available. We apologise for the inconvenience this is causing you.
Mar 17, 5:25 AM
Authentication Services Impacted on Public Cloud Environment
major

Started: Mar 5, 2:04 PM

monitoring
Our Engineering team is monitoring this event, and we're applying the fix during approved scheduled release windows in order to minimize possible service disruptions. Customers using variables defined outside of their action method definition on runtime node18 or less may experience unexpected behavior. We'll provide another update as changes in status occur.
Mar 5, 3:05 PM
identified
Our Engineering team has investigated and we've identified the cause of the event. We're making progress on mitigating impact and have applied a fix to a subset of affected environments. After applying this fix, we're observing a successful recovery of our services. Customers using variables defined outside of their action method definition on runtime node18 or less may experience unexpected behavior. We will continue to monitor mitigation of the issue as we continue to roll this fix out acro...
Mar 5, 2:39 PM
investigating
We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
Mar 5, 2:09 PM