- Detected by Pingoru
- Sep 16, 2026, 03:06 AM UTC
- Resolved
- Sep 16, 2026, 03:55 AM UTC
- Duration
- 49m
Affected: Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)
Timeline · 4 updates
-
investigating Sep 16, 2026, 03:06 AM UTC
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.
-
investigating Sep 16, 2026, 03:40 AM UTC
We are continuing to investigate the issue and will provide further updates with changes in the incident status as our mitigation efforts progress.
-
monitoring Sep 16, 2026, 03:47 AM UTC
The Auth0 Engineering team has applied the mitigation and observed the service is restoring. We're monitoring the environment to ensure stability.
-
resolved Sep 16, 2026, 03:55 AM UTC
Services have been restored. 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.
Read the full incident report →
Critical September 1, 2026 - Detected by Pingoru
- Sep 01, 2026, 03:50 PM UTC
- Resolved
- Sep 01, 2026, 04:01 PM UTC
- Duration
- 10m
Affected: Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-3 (Production) (Authentication)Auth0 US-3 (Production) (Machine to Machine)Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)Auth0 EU-1 (Production) (Authentication)Auth0 EU-1 (Production) (Machine to Machine)Auth0 EU-2 (Production) (Authentication)Auth0 EU-2 (Production) (Machine to Machine)Auth0 UK-1 (Production) (Authentication)Auth0 UK-1 (Production) (Machine to Machine)
Timeline · 3 updates
-
investigating Sep 01, 2026, 03:50 PM UTC
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.
-
resolved Sep 01, 2026, 04:01 PM UTC
The Auth0 Engineering team has applied a fix for the issue. Error rates on affected environments are subsiding. Impacted customers should observe service restoration at this time. After monitoring the environment to ensure service stability, we're considering this incident resolved.
-
resolved Sep 03, 2026, 06:23 PM UTC
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)
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2026, 07:21 AM UTC
- Resolved
- Aug 25, 2026, 07:58 AM UTC
- Duration
- 37m
Affected: Auth0 EU-2 (Production) (Authentication)Auth0 EU-2 (Production) (Machine to Machine)
Timeline · 3 updates
-
investigating Aug 25, 2026, 07:21 AM UTC
We're investigating an issue that impacted the Tenant Log Streaming service on the EU-2 Public Cloud environment. Customers may not be able to access their log data through the streaming service.
-
monitoring Aug 25, 2026, 07:42 AM UTC
We've mitigated the issue by performing a restart on the affected Tenant Log Streaming service in the EU-2 Public Cloud environment. Customers should observe service functionality returning. We're monitoring the environment to ensure stability.
-
resolved Aug 25, 2026, 07:58 AM UTC
After monitoring the environment, we confirm that the issue remains mitigated, and we're considering this incident as resolved. We apologize for the impact that this event has caused on your users. A Root Cause Analysis detailing this event will be shared within 21 business days.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2026, 08:09 PM UTC
- Resolved
- Aug 07, 2026, 01:42 PM UTC
- Duration
- 17h 32m
Affected: Auth0 US-5 (Production) (Tenant Logs)
Timeline · 2 updates
-
investigating Aug 06, 2026, 08:09 PM UTC
We're currently investigating an issue affecting tenant logs and management of group memberships. We'll provide updates regarding our progress or as our investigation status changes.
-
resolved Aug 07, 2026, 01:42 PM UTC
Services have been restored. A root cause analysis (RCA) will be posted here within 14 business days. We sincerely apologize for the impact this had on you and your users.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 11:09 AM UTC
- Resolved
- Jul 24, 2026, 11:45 AM UTC
- Duration
- 36m
Affected: Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-1 (Production) (Management API)Auth0 US-1 (Production) (Auth0 Dashboard)Auth0 US-4 (Production) (Authentication)Auth0 US-4 (Production) (Machine to Machine)Auth0 US-4 (Production) (Management API)Auth0 US-4 (Production) (Auth0 Dashboard)
Timeline · 4 updates
-
investigating Jul 24, 2026, 11:09 AM UTC
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.
-
monitoring Jul 24, 2026, 11:12 AM UTC
The issue self-resolved and we're monitoring the environment to ensure stability.
-
resolved Jul 24, 2026, 11:45 AM UTC
Services have been restored. 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.
-
resolved Aug 03, 2026, 09:12 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-07-24_-_Multiple_Cloud_Environments_Impacted_by_Regional_Outage.pdf](https://cdn.auth0.com/website/2026-07-24_-_Multiple_Cloud_Environments_Impacted_by_Regional_Outage.pdf)
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 03:48 PM UTC
- Resolved
- Jun 22, 2026, 04:28 PM UTC
- Duration
- 40m
Affected: Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)Auth0 US-5 (Production) (Multifactor Authentication)Auth0 US-5 (Production) (Management API)
Timeline · 5 updates
-
investigating Jun 22, 2026, 03:41 PM UTC
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.
-
identified Jun 22, 2026, 03:48 PM UTC
An elevated volume of errors are being observed on the US-5 Public Cloud environment, affecting a subset of customers. We've identified a load-shedding event that appear connected to the event. We've disabled ingress load shedding to mitigate impact and are monitoring for recovery. We will provide further updates with changes in the incident status and as our mitigation efforts progress.
-
monitoring Jun 22, 2026, 04:22 PM UTC
After performing our previous step in disabling ingress load shedding on the US-5 Public Cloud environment, we've since observed subsiding error rates, and have received customer confirmations that services are recovering. We're continuing to monitor the environment for stability and will continue to provide updates regarding service status.
-
resolved Jun 22, 2026, 04:28 PM UTC
After monitoring the environment to ensure stability, we observed that services have been restored. 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.
-
resolved Jul 02, 2026, 02:21 AM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-06-22_-_Elevated_Errors_on_AU-1_and_US-5_Public_Cloud_Environments.pdf](https://cdn.auth0.com/website/2026-06-22_-_Elevated_Errors_on_AU-1_and_US-5_Public_Cloud_Environments.pdf)
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 03:21 PM UTC
- Resolved
- Jun 22, 2026, 04:28 PM UTC
- Duration
- 1h 7m
Affected: Auth0 AU (Production) (Authentication)Auth0 AU (Production) (Machine to Machine)Auth0 AU (Production) (Multifactor Authentication)Auth0 AU (Production) (Management API)
Timeline · 5 updates
-
investigating Jun 22, 2026, 03:21 PM UTC
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.
-
identified Jun 22, 2026, 03:48 PM UTC
An elevated volume of errors are being observed on the AU-1 Public Cloud environment, affecting a subset of customers. We've identified a load-shedding event that appear connected to the event. We've disabled ingress load shedding to mitigate impact and are monitoring for recovery. We will provide further updates with changes in the incident status and as our mitigation efforts progress.
-
monitoring Jun 22, 2026, 04:22 PM UTC
After performing our previous step in disabling ingress load shedding on the AU-1 Public Cloud environment, we've since observed subsiding error rates, and have received customer confirmations that services are recovering. We're continuing to monitor the environment for stability and will continue to provide updates regarding service status.
-
resolved Jun 22, 2026, 04:28 PM UTC
After monitoring the environment to ensure stability, we observed that services have been restored. 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.
-
resolved Jul 02, 2026, 02:22 AM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2026-06-22\_-\_Elevated\_Errors\_on\_AU-1\_and\_US-5\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/2026-06-22_-_Elevated_Errors_on_AU-1_and_US-5_Public_Cloud_Environments.pdf)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 06:23 PM UTC
- Resolved
- Jun 01, 2026, 07:23 PM UTC
- Duration
- 1h
Affected: Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-1 (Production) (Management API)
Timeline · 5 updates
-
investigating Jun 01, 2026, 06:23 PM UTC
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.
-
identified Jun 01, 2026, 06:32 PM UTC
We have identified elevated errors indicating an infrastructural issue that is impacting the US-1 Public Cloud environment. We're currently formulating mitigating actions. We will provide further updates with changes in the incident status and as our mitigation efforts progress.
-
monitoring Jun 01, 2026, 07:11 PM UTC
The Engineering team has applied a fix for the issue and we're monitoring the environment to ensure stability. Errors rates on the affected environment are beginning to subside. Due to resource exhaustion observed on the infrastructure supporting the environment, we have scaled up these resources to mitigate impact. A full investigation into the root cause of the issue will continue. We'll provide further update as our status changes.
-
resolved Jun 01, 2026, 07:23 PM UTC
We've monitored the environment to ensure stability after applying our fix, and services have been restored. 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.
-
resolved Jun 09, 2026, 10:31 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-06-01_-_Increased_Error_Rates_on_US-1_Public_Cloud.pdf](https://cdn.auth0.com/website/2026-06-01_-_Increased_Error_Rates_on_US-1_Public_Cloud.pdf)
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 06:10 PM UTC
- Resolved
- May 21, 2026, 06:11 PM UTC
- Duration
- 32s
Affected: Auth0 EU-1 (Production) (Authentication)
Timeline · 3 updates
-
identified May 21, 2026, 06:10 PM UTC
On May 20, 2026, between 15:00-15:20 UTC, we experienced elevated errors in our Authentication API. Impacted users would have experienced 5xx error codes when attempting to log in. There is no active impact, and no actions are required from our customers.
-
resolved May 21, 2026, 06:11 PM UTC
The errors have self-resolved, and the services have been stable. We will continue to investigate the issue's root cause and provide an analysis within 7 business days. We sincerely apologize for the impact this had on you and your users.
-
resolved Jun 01, 2026, 08:16 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-05-20_-_Elevated_Errors_on_Multiple_EU-Region_Cloud_Environments.pdf](https://cdn.auth0.com/website/2026-05-20_-_Elevated_Errors_on_Multiple_EU-Region_Cloud_Environments.pdf)
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 10:00 AM UTC
- Resolved
- Apr 28, 2026, 09:32 PM UTC
- Duration
- 11h 31m
Affected: US-1 (Production)US-3 (Production)US-4 (Production)US-5 (Production)EU-1 (Production)EU-2 (Production)AU (Production)JP-1 (Production)UK-1 (Production)CA-1 (Production)Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-1 (Production) (Multifactor Authentication)Auth0 US-1 (Production) (Management API)Auth0 US-3 (Production) (Authentication)Auth0 US-3 (Production) (Machine to Machine)Auth0 US-3 (Production) (Multifactor Authentication)Auth0 US-3 (Production) (Management API)Auth0 US-4 (Production) (Authentication)Auth0 US-4 (Production) (Machine to Machine)Auth0 US-4 (Production) (Multifactor Authentication)Auth0 US-4 (Production) (Management API)Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)Auth0 US-5 (Production) (Multifactor Authentication)Auth0 US-5 (Production) (Management API)Auth0 EU-1 (Production) (Authentication)Auth0 EU-1 (Production) (Machine to Machine)Auth0 EU-1 (Production) (Multifactor Authentication)Auth0 EU-1 (Production) (Management API)Auth0 EU-2 (Production) (Authentication)Auth0 EU-2 (Production) (Machine to Machine)Auth0 EU-2 (Production) (Multifactor Authentication)Auth0 EU-2 (Production) (Management API)Auth0 AU (Production) (Authentication)Auth0 AU (Production) (Machine to Machine)Auth0 AU (Production) (Multifactor Authentication)Auth0 AU (Production) (Management API)Auth0 JP-1 (Production) (Authentication)Auth0 JP-1 (Production) (Machine to Machine)Auth0 JP-1 (Production) (Multifactor Authentication)Auth0 JP-1 (Production) (Management API)Auth0 UK-1 (Production) (Authentication)Auth0 UK-1 (Production) (Machine to Machine)Auth0 UK-1 (Production) (Multifactor Authentication)Auth0 UK-1 (Production) (Management API)Auth0 CA-1 (Production) (Authentication)Auth0 CA-1 (Production) (Machine to Machine)Auth0 CA-1 (Production) (Multifactor Authentication)Auth0 CA-1 (Production) (Management API)
Timeline · 3 updates
-
identified Apr 28, 2026, 10:00 AM UTC
We're currently investigating a disruption to Auth0 Services on the Public Cloud environment. Our third-party Edge provider has confirmed an issue originating from within their services. This event specifically impacts customers who are utilizing self-managed custom domains for Authentication, MFA, and Management API. We're closely monitoring for progress from our provider following their investigation. We'll provide updates as we gather more information and as our status changes.
-
resolved Apr 28, 2026, 09:32 PM UTC
Our third-party Edge provider has reported that their service disruption has been mitigated within their environment. We've observed recovery for all previously affected Auth0 services and now see stability in the Public Cloud environment. After no further recurrence of the issue, we're now marking this incident as resolved. A root cause analysis (RCA) will be posted here within 14 business days. We sincerely apologize for the impact this had on you and your users.
-
resolved May 08, 2026, 07:38 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260428\_-\_Increased\_Error\_Rates\_on\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260428_-_Increased_Error_Rates_on_Public_Cloud_Environments.pdf)
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 05:03 AM UTC
- Resolved
- Apr 28, 2026, 05:46 AM UTC
- Duration
- 43m
Affected: Auth0 CA-1 (Production) (Authentication)Auth0 CA-1 (Production) (Machine to Machine)
Timeline · 4 updates
-
investigating Apr 28, 2026, 05:03 AM UTC
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.
-
identified Apr 28, 2026, 05:30 AM UTC
Our Engineering team has identified the root cause of this issue and our mitigation efforts are underway. We will provide an additional update once those mitigation efforts have been completed.
-
resolved Apr 28, 2026, 05:46 AM UTC
Services have been restored. 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.
-
resolved May 08, 2026, 07:29 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260428\_-\_Error\_Rates\_caused\_by\_Regional\_Infrastructure\_Failure.pdf](https://cdn.auth0.com/blog/20260428_-_Error_Rates_caused_by_Regional_Infrastructure_Failure.pdf)
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 02:04 PM UTC
- Resolved
- Mar 06, 2026, 12:10 AM UTC
- Duration
- 10h 6m
Affected: Auth0 US-1 (Production) (Authentication)Auth0 US-1 (Production) (Machine to Machine)Auth0 US-3 (Production) (Authentication)Auth0 US-3 (Production) (Machine to Machine)Auth0 US-4 (Production) (Authentication)Auth0 US-4 (Production) (Machine to Machine)Auth0 US-5 (Production) (Authentication)Auth0 US-5 (Production) (Machine to Machine)Auth0 EU-1 (Production) (Authentication)Auth0 EU-1 (Production) (Machine to Machine)Auth0 EU-2 (Production) (Authentication)Auth0 EU-2 (Production) (Machine to Machine)Auth0 AU (Production) (Authentication)Auth0 AU (Production) (Machine to Machine)Auth0 JP-1 (Production) (Authentication)Auth0 JP-1 (Production) (Machine to Machine)Auth0 UK-1 (Production) (Authentication)Auth0 UK-1 (Production) (Machine to Machine)Auth0 CA-1 (Production) (Authentication)Auth0 CA-1 (Production) (Machine to Machine)
Timeline · 5 updates
-
investigating Mar 05, 2026, 02:04 PM UTC
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.
-
identified Mar 05, 2026, 02:39 PM UTC
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 across the remaining affected environments.
-
monitoring Mar 05, 2026, 03:05 PM UTC
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.
-
resolved Mar 06, 2026, 12:10 AM UTC
Services have been restored. 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.
-
resolved Mar 18, 2026, 04:41 AM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260304\_-\_Action\_State\_Persistence\_in\_All\_Regional\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260304_-_Action_State_Persistence_in_All_Regional_Public_Cloud_Environments.pdf)
Read the full incident report →
- Detected by Pingoru
- Feb 28, 2026, 01:19 AM UTC
- Resolved
- Feb 28, 2026, 03:34 AM UTC
- Duration
- 2h 15m
Affected: Auth0 US-4 (Production) (Authentication)
Timeline · 7 updates
-
investigating Feb 28, 2026, 12:45 AM UTC
We are currently investigating an incident that impacted our services. Impacted users would experience intermittent session timeouts. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
-
investigating Feb 28, 2026, 01:19 AM UTC
We are still experiencing errors. Our engineering team is actively investigating, with a current focus on reviewing system logs and telemetry to identify the root cause. We will provide an update within 30 minutes or as soon as new information becomes available.
-
investigating Feb 28, 2026, 01:48 AM UTC
We are currently performing infrastructure optimizations to address performance degradation. We have refined our database configuration and are scaling up backend capacity to better manage current traffic loads. We are actively monitoring the environment to confirm that these adjustments successfully stabilize the service.
-
monitoring Feb 28, 2026, 02:17 AM UTC
Our Engineering team has applied a fix, and while we're seeing clear indications of recovery, we're proceeding with an abundance of caution to ensure full stability. We will continue to monitor and will provide an update within 30 minutes or as soon as new information becomes available.
-
monitoring Feb 28, 2026, 02:44 AM UTC
The initial impact has fully recovered, and we've transitioned from active response to a dedicated monitoring phase. While we expect services to remain stable, if you experience any intermittent session timeout errors, please contact our support team for assistance.
-
resolved Feb 28, 2026, 03:34 AM UTC
Services has been restored. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.
-
resolved Mar 11, 2026, 06:19 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-02-28_-_Authentication_Errors_on_US-4_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-02-28_-_Authentication_Errors_on_US-4_Public_Cloud_Environment.pdf)
Read the full incident report →
- Detected by Pingoru
- Feb 22, 2026, 04:42 PM UTC
- Resolved
- Feb 22, 2026, 06:52 PM UTC
- Duration
- 2h 10m
Affected: Auth0 US-3 (Production) (Authentication)Auth0 US-3 (Production) (Machine to Machine)
Timeline · 8 updates
-
investigating Feb 22, 2026, 04:26 PM UTC
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.
-
identified Feb 22, 2026, 04:42 PM UTC
Our investigation has determined that a surge in unexpected traffic is consuming an inordinate amount of resources on the affected Public Cloud environment. To return services to normal levels we're taking mitigating steps to resolve impact. We will continue to update as our status progresses.
-
identified Feb 22, 2026, 04:58 PM UTC
Our action to address the unexpected traffic to mitigate the issue did not fully recover service functionality. Error rates still remain elevated on the affected environment. We're extending our investigation to other potential root causes. We will continue to update as our status changes.
-
identified Feb 22, 2026, 05:31 PM UTC
Our investigation into this event is ongoing. Error rates continue to remain elevated at this time. We're inspecting error logs for potential insights into root cause. Further updates will be provided as our investigation progresses.
-
identified Feb 22, 2026, 06:09 PM UTC
We're continuing to analyze logs from the resources that support the impacted environment, which indicate server and query failures. Error rates continue to remain elevated on the Public Cloud environment. We'll continue to provide updates as our status changes.
-
monitoring Feb 22, 2026, 06:41 PM UTC
We have implemented mitigating actions and are observing a reduction of errors. We're monitoring the environment to ensure stability and that there is no recurrence of impact. The full root cause of the event is still undergoing investigation. We'll continue to update as we obtain more information.
-
resolved Feb 22, 2026, 06:52 PM UTC
After monitoring, we've observed that the environment has remained stable. Services have been restored and authentication is functioning as expected. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and your users.
-
resolved Mar 05, 2026, 05:04 PM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20260222_-_Authentication_Errors_on_the_US-3_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20260222_-_Authentication_Errors_on_the_US-3_Public_Cloud_Environment.pdf)
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:00 PM UTC
- Resolved
- Feb 23, 2026, 04:30 PM UTC
- Duration
- 2d 19h
Affected: Auth0 US-1 (Production) (Management API)Auth0 US-3 (Production) (Management API)Auth0 US-4 (Production) (Management API)Auth0 US-5 (Production) (Management API)
Timeline · 5 updates
-
investigating Feb 20, 2026, 09:00 PM UTC
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.
-
identified Feb 23, 2026, 02:30 PM UTC
Services have been restored for a subset of Public Cloud customers. Restoration efforts are ongoing for full recovery. We will continue to provide updates as our status changes.
-
identified Feb 23, 2026, 03:30 PM UTC
Additional Public Cloud environments are seeing restoration of service. Our efforts towards full restoration is ongoing. We'll continue to provide updates as changes in status occur.
-
resolved Feb 23, 2026, 04:30 PM UTC
Services have been restored. 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.
-
resolved Mar 12, 2026, 01:25 AM UTC
A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260302\_-\_Management\_Service\_Disruption\_on\_Multiple\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20260302_-_Management_Service_Disruption_on_Multiple_Public_Cloud_Environments.pdf)
Read the full incident report →
