Auth0

Affected: User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-14 05:01 UTC

   We are currently investigating an incident that impacted our services. Users may experience issues with authentication functionality. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. resolved 2026-10-14 05:32 UTC

   Our investigation has determined that the issue originated from infrastructure hosted by our third-party service provider. Elevated errors on the environment have subsided, and services have been restored. A root cause analysis (RCA) will be posted here within 7 business days....

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Management API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 19:00 UTC

   We're currently investigating an incident that impacted our services. This event impacts authentication and Management API functionality. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. monitoring 2026-10-09 19:01 UTC

   We've identified a load spike event that caused elevated service errors on the US-4 Public Cloud environment. These errors have subsided after our autoscaling mechanisms triggered. The issue has self-resolved, and we're monitoring the environment to ensure stability. We'll...

3. resolved 2026-10-09 19:13 UTC

   After monitoring the environment to ensure stability, we confirm that services have been restored. Our investigation into the full root cause will continue, as we confirm the source of the issue. A root cause analysis (RCA) will be posted here within 7 business days. We...

4. postmortem 2026-10-15 19:06 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Management API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-30 20:11 UTC

   We are currently investigating an incident that impacted our services. Users may experience issues with authentication functionality. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. identified 2026-09-30 20:32 UTC

   We're continuing to investigate the service disruption on the US-5 Public Cloud Environment. We're assessing service metrics and logs to determine the source of the issue. We're evaluating a potential issue within infrastructure hosted by our third-party service provider. We'll...

3. identified 2026-09-30 20:54 UTC

   We're actively investigating with our third-party provider regarding the latency discrepancies that we observe within their hosted infrastructure. Additionally, we're investigating an issue involving a high number of service connections causing exhaustion on backend resources....

4. monitoring 2026-09-30 21:14 UTC

   We've observed that service error rates on the US-5 Public Cloud Environment have subsided and returned to baseline, marking a return to service functionality. The service disruption has been mitigated and we're monitoring the ensure stability. Meanwhile, our investigation is...

5. resolved 2026-09-30 21:24 UTC

   After monitoring the environment to ensure stability, we observe that services have been restored. Our investigation into origin of the event will continue, in collaboration with our third-party provider. A root cause analysis (RCA) will be posted here within 7 business days. We...

6. postmortem 2026-10-07 19:38 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-09-30_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-09-30_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 03:06 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.

2. investigating 2026-09-16 03:40 UTC

   We are continuing to investigate the issue and will provide further updates with changes in the incident status as our mitigation efforts progress.

3. monitoring 2026-09-16 03:47 UTC

   The Auth0 Engineering team has applied the mitigation and observed the service is restoring. We're monitoring the environment to ensure stability.

4. resolved 2026-09-16 03:55 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.

5. postmortem 2026-09-25 21:08 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-09-16_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/2026-09-16_-_Elevated_Errors_on_US-5_Public_Cloud_Environment.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 15:50 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.

2. resolved 2026-09-01 16:01 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...

3. postmortem 2026-09-03 18:23 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Multi-factor Authentication, Management API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 10:28 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.

2. identified 2026-08-27 10:56 UTC

   We have identified the cause, and have performed a rollback. We will provide further updates with changes in the incident status and as our mitigation efforts progress.

3. monitoring 2026-08-27 11:06 UTC

   The Auth0 Engineering team has applied a fix for the issue and we're monitoring the environment to ensure stability.

4. resolved 2026-08-27 12:03 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.

5. postmortem 2026-09-08 22:15 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 07:21 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.

2. monitoring 2026-08-25 07:42 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.

3. resolved 2026-08-25 07:58 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.

4. postmortem 2026-09-22 00:37 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Tenant Logs, Other

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 20:09 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.

2. resolved 2026-08-07 13:42 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.

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Other, Other, Other, Other, Other, Other, Other, Other, Other, Other

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-06 16:51 UTC

   We are currently experiencing an issue that impacts access to support.auth0.com. Our team is actively working to mitigate the issue and restore full portal access as quickly as possible. We apologize for the inconvenience. Core Authentication is not impacted. If you require...

2. investigating 2026-08-06 16:52 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-06 17:44 UTC

   We're continuing to carry out our mitigation strategy to restore access to support.auth0.com. We apologize for the inconvenience. Core Authentication is not impacted. We'll continue to provide updates with changes in status.

4. resolved 2026-08-06 17:59 UTC

   Access to support.auth0.com has been restored. A root cause analysis (RCA) will be posted here within 21 business days. We sincerely apologize for the impact this had on you and your users.

5. postmortem 2026-09-03 17:47 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2026-08-06\_-\_Increased\_Error\_Rates\_on\_Support\_Portal\_SSO\_Login.pdf](https://cdn.auth0.com/blog/2026-08-06_-_Increased_Error_Rates_on_Support_Portal_SSO_Login.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Management API, Management API, Auth0 Dashboard, Auth0 Dashboard

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-24 11:09 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.

2. monitoring 2026-07-24 11:12 UTC

   The issue self-resolved and we're monitoring the environment to ensure stability.

3. resolved 2026-07-24 11:45 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.

4. postmortem 2026-08-03 21:12 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Other, Other, Other, Other, Other, Other, Other, Other, Other, Other

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 14:31 UTC

   We are currently investigating an incident that impacted our services on the Auth0 Support Center. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. monitoring 2026-07-23 15:20 UTC

   Our Engineering team is seeing recovery, and users should now be able to access their Tenants, Private Instance, and Reports sections of Support Center. This issue did not impact any core authentication services. We're monitoring the environments to ensure stability and that...

3. resolved 2026-07-23 16:06 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.

4. postmortem 2026-09-15 02:24 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Tenant Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 02:49 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.

2. identified 2026-07-14 03:08 UTC

   We have identified an issue with our tenant logs streaming service. We will provide further updates with changes in the incident status and as our mitigation efforts progress.

3. identified 2026-07-14 03:42 UTC

   We have identified an issue with our tenant logs streaming service. We are continuing to investigate the root cause and will provide further updates with changes in the incident status and as our mitigation efforts progress. This issue is not impacting any core authentication...

4. identified 2026-07-14 04:26 UTC

   We are continuing to investigate the root cause in our tenant logs streaming service. The tenant logs are accessible via Auth0 management dashboard. We will provide next update at 7am UTC with any changes in the incident status and as our mitigation efforts progress. This issue...

5. resolved 2026-07-14 05:29 UTC

   Services have been restored. We sincerely apologize for the impact this had on you and your users.

6. postmortem 2026-08-15 23:17 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-26 06:57 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.

2. monitoring 2026-06-26 07:23 UTC

   The service has recovered from the issue and we're monitoring the environment to ensure stability.

3. resolved 2026-06-26 07:50 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.

4. postmortem 2026-07-08 17:31 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Multi-factor Authentication, Management API

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-22 15:41 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.

2. identified 2026-06-22 15:48 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...

3. monitoring 2026-06-22 16:22 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...

4. resolved 2026-06-22 16:28 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.

5. postmortem 2026-07-02 02:21 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Multi-factor Authentication, Management API

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-22 15:21 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.

2. identified 2026-06-22 15:48 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...

3. monitoring 2026-06-22 16:22 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...

4. resolved 2026-06-22 16:28 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.

5. postmortem 2026-07-02 02:22 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Auth0 Dashboard

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 05:49 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.

2. monitoring 2026-06-11 06:55 UTC

   We are currently monitoring the incident

3. resolved 2026-06-11 07:10 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.

4. postmortem 2026-06-23 22:07 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Management API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 18:23 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.

2. identified 2026-06-01 18:32 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.

3. monitoring 2026-06-01 19:11 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...

4. resolved 2026-06-01 19:23 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.

5. postmortem 2026-06-09 22:31 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)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-21 18:10 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.

2. resolved 2026-05-21 18:11 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.

3. postmortem 2026-06-01 20:16 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 02:43 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.

2. identified 2026-05-08 02:45 UTC

   We're observing elevated error rates on the US-3 Public Cloud environment, with a high variability of impact to user experience. Our third-party provider has confirmed network instability within their managed infrastructure, causing disruption to Auth0 services. We will provide...

3. identified 2026-05-08 03:40 UTC

   After assessing impact on the affected Public Cloud environment, we've determined that the disruption to Auth0 services been minimal. We're continuing to track mitigation progress from our third-party provider and their managed infrastructure. We'll continue to provide updates...

4. monitoring 2026-05-08 04:43 UTC

   We're continuing to monitor the Public Cloud environment that may have experienced minimal impact from this event. However, Auth0 services have remained healthy, so we're monitoring our metrics closely as our third-party provider addresses the issue within their managed...

5. monitoring 2026-05-08 23:20 UTC

   We're continuing to track the regional infrastructure issue with our third-party provider. Auth0 services have remained healthy, but we're monitoring to ensure stability while our provider works to mitigate the issue in their environment. They anticipate full recovery within the...

6. resolved 2026-05-09 03:40 UTC

   Services have been restored. A root cause analysis (RCA) will be posted here within 21 business days. We sincerely apologize for the impact this had on you and your users.

7. postmortem 2026-08-28 01:11 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Multi-factor Authentication, Management API, Management API, Management API, Management API, Management API, Management API, Management API, Management API, Mangement API, Management API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-04-28 10:00 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...

2. resolved 2026-04-28 21:32 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...

3. postmortem 2026-05-08 19:38 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)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 05:03 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.

2. identified 2026-04-28 05:30 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.

3. resolved 2026-04-28 05:46 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.

4. postmortem 2026-05-08 19:29 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-22 18:29 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.

2. resolved 2026-04-22 19:01 UTC

   Customers experienced service disruption due to a DNS misconfiguration that was inadvertently applied in preparation for infrastructure enhancement. This issue was resolved after the misconfiguration was manually corrected. We monitored the environment to ensure stability and...

3. postmortem 2026-05-07 16:36 UTC

   A root-cause analysis for this issue has been performed and is now available...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-22 18:29 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.

2. resolved 2026-04-22 19:01 UTC

   Customers experienced service disruption due to a DNS misconfiguration that was inadvertently applied in preparation for infrastructure enhancement. This issue was resolved after the misconfiguration was manually corrected. We monitored the environment to ensure stability and...

3. postmortem 2026-05-07 16:31 UTC

   A root-cause analysis for this issue has been performed and is now available...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Other, Other, Other, Other, Other, Other, Other, Other, Other, Other, Other

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-17 05:25 UTC

   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.

2. identified 2026-03-17 05:50 UTC

   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...

3. monitoring 2026-03-17 06:25 UTC

   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.

4. resolved 2026-03-17 06:51 UTC

   The Auth0 Support Center is fully operational, and case creation functionality has been restored. Following a period of monitoring, we have confirmed the systems are stable. We sincerely apologize for any inconvenience this disruption may have caused.

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-05 14:04 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.

2. identified 2026-03-05 14:39 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...

3. monitoring 2026-03-05 15:05 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...

4. resolved 2026-03-06 00:10 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.

5. postmortem 2026-03-18 04:41 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-28 00:45 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.

2. investigating 2026-02-28 01:19 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.

3. investigating 2026-02-28 01:48 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...

4. monitoring 2026-02-28 02:17 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...

5. monitoring 2026-02-28 02:44 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.

6. resolved 2026-02-28 03:34 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.

7. postmortem 2026-03-11 18:19 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-22 16:26 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.

2. identified 2026-02-22 16:42 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...

3. identified 2026-02-22 16:58 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...

4. identified 2026-02-22 17:31 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.

5. identified 2026-02-22 18:09 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.

6. monitoring 2026-02-22 18:41 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...

7. resolved 2026-02-22 18:52 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...

8. postmortem 2026-03-05 17:04 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Management API, Management API, Management API, Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-20 21:00 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.

2. identified 2026-02-23 14:30 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.

3. identified 2026-02-23 15:30 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.

4. resolved 2026-02-23 16:30 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.

5. postmortem 2026-03-12 01:25 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Other, Other, Other, Other, Other, Other, Other, Other, Other, Other, Other

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-11 00:29 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.

2. monitoring 2026-02-11 03:25 UTC

   We have determined that the issue has originated from one of our third-party providers. Users are impacted when attempting to load assets from our CDN resource. Our provider has applied the necessary changes to mitigate this issue and we are now seeing recovery and monitoring to...

3. resolved 2026-02-11 04:50 UTC

   Services have 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.

4. postmortem 2026-02-25 08:57 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Management API, Management API, Management API, Management API, Management API, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-06 20:38 UTC

   We're currently investigating an incident that impacted our services. Auth0 Manage, FGA Dashboard, and Status Page are inaccessible. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. resolved 2026-02-06 21:20 UTC

   This issue has now been resolved. Impact from this event affected multiple Auth0 services, however User Authentication was not impacted. Our investigation determined that a recent deployment inadvertently impacted multiple services and pages. We reverted to a previous version in...

3. postmortem 2026-02-25 09:06 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Management API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-28 20:16 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.

2. resolved 2025-12-28 20:18 UTC

   Services have 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.

3. postmortem 2026-01-14 21:31 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20251228_-_Elevated_Errors_on_EU-2_Public_Cloud.pdf](https://cdn.auth0.com/website/20251228_-_Elevated_Errors_on_EU-2_Public_Cloud.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-05 09:31 UTC

   We are currently investigating an incident that impacted our edge networking services. Our team is actively working to understand the root cause and mitigate the issue.

2. monitoring 2025-12-05 09:43 UTC

   Our edge provider has implemented a fix and we are continuing to monitor to ensure no further impact

3. resolved 2025-12-05 10:03 UTC

   Edge networking services have 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.

4. postmortem 2025-12-18 21:09 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-04 23:15 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.

2. identified 2025-12-04 23:20 UTC

   We are investigating the errors associated with this event, and are observing that they are currently trending back to normal thresholds. After further analysis we believe this issue may have affected only a small subset of tenants. We will continue to update with changes in our...

3. monitoring 2025-12-04 23:28 UTC

   This event has self-resolved and error rates subsided within the affected environment. Authentication functionality has recovered, and users should no longer be impacted by this issue. We will continue to investigate root cause while we monitor the environment to ensure...

4. resolved 2025-12-04 23:36 UTC

   We've monitored the environment to ensure stability, and error rates have remain subsided. This issue is now fully resolved. We sincerely apologize for the impact this had on you and your users.

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-20 11:30 UTC

   We are currently investigating an incident that is impacting our Dashboard services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. monitoring 2025-11-20 11:37 UTC

   We have identified the root cause of the issue and have performed a rollback to the affected environment. We are seeing recovery after our rollback and are monitoring to ensure full stability. We will continue to update every 30 minutes.

3. monitoring 2025-11-20 11:41 UTC

   We have identified the root cause of the issue and have performed a rollback to the affected environment. We are seeing recovery after our rollback and are monitoring to ensure full stability. We will continue to update every 30 minutes.

4. resolved 2025-11-20 12:10 UTC

   Services have 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 tenant members.

5. postmortem 2025-12-04 21:42 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-18 14:30 UTC

   On November 18, 2025, our Engineering team identified an issue that adversely impacted US-3, US-4, and US-5 Public Cloud customers following an event we experienced with service degradation from our Edge Provider. We are performing an in-depth analysis of these events.

2. resolved 2025-11-18 15:57 UTC

   These issues have since been fully resolved and mitigated. We are working on a root-cause analysis (RCA) report which we will share here in the coming days. We sincerely apologize for any impact this has caused you and your users.

3. postmortem 2025-11-25 02:18 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-18 11:20 UTC

   We have identified an issue that impacted some customers due to a service degradation that our edge provider was experiencing beginning at approximately 11:20 UTC. Our Engineering team has been reviewing and performing an impact analysis while our Support team is working with...

2. identified 2025-11-18 12:39 UTC

   Our Engineering team is continuing to review cases on this matter for impacted customers. We will advise with an additional update in approximately 30 minutes once our Engineering team has triaged this issue further.

3. identified 2025-11-18 14:30 UTC

   We have identified a subset of customer traffic patterns that was impacted by our Edge Providers issues. We are starting to see residual customer recovery.

4. monitoring 2025-11-18 14:42 UTC

   We are now observing gradual recovery for impacted customers and our Engineering team is continuing to monitor this issue.

5. resolved 2025-11-18 14:43 UTC

   Services have been restored. A root cause analysis (RCA) will be posted here once our review of this incident completes.

6. postmortem 2025-11-25 00:42 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-18 05:26 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.

2. monitoring 2025-11-18 05:47 UTC

   We applied a fix for the issue. The error rates have subsided and we are monitoring the system.

3. resolved 2025-11-18 05:57 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.

4. postmortem 2025-12-04 00:16 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20251118_-_Increased_Errors_on_CA-1_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20251118_-_Increased_Errors_on_CA-1_Public_Cloud_Environment.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-17 15:31 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.

2. identified 2025-11-17 15:32 UTC

   We have identified a recent deployment that has impacted the affected environment and a rollback is being performed to mitigate the issue. We will continue to update as our progress continues or as our status changes.

3. monitoring 2025-11-17 15:39 UTC

   We've observed that the rollback performed on the environment has reduced error rates to pre-incident thresholds. Users should experience recovery to authentication functionality. We're monitoring the environment to ensure stability.

4. resolved 2025-11-17 15:53 UTC

   After monitoring the environment following our resolution actions, we've observed error rates have subsided, and authentication functionality remains stable. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you and...

5. postmortem 2025-12-01 17:51 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20251117_-_Elevated_Errors_in_JP-1_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20251117_-_Elevated_Errors_in_JP-1_Public_Cloud_Environment.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-16 19:31 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.

2. investigating 2025-11-16 19:42 UTC

   Our Engineering team is investigating load on one of our databases servicing this environment. We will provide additional updates here in approximately 15-30 minutes as we work to identify the root cause of this issue and discuss any necessary mitigation.

3. identified 2025-11-16 20:05 UTC

   We've identified a potential issue with database queries and connections which service this environment. We have engaged additional Engineering resources to review the logs associated with this issue and we will provide an additional update in approximately 30 minutes as we...

4. monitoring 2025-11-16 20:33 UTC

   Our Engineering team has taken the necessary remediation steps and we are now observing full recovery in the environment. We are continuing to monitor this issue, however all symptoms have resolved.

5. resolved 2025-11-16 20:38 UTC

   Services are now 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.

6. postmortem 2025-11-26 19:29 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20251116_Increased_Errors_in_US3_Public_Cloud_Environment.pdf](https://cdn.auth0.com/website/20251116_Increased_Errors_in_US3_Public_Cloud_Environment.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-14 07:50 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.

2. investigating 2025-11-14 08:05 UTC

   Our environment is experiencing elevated errors. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

3. monitoring 2025-11-14 08:20 UTC

   We applied a fix for the issue and the errors have subsided. We are monitoring the system.

4. resolved 2025-11-14 08:59 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.

5. postmortem 2025-11-26 19:27 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-09 19:35 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.

2. identified 2025-11-09 20:09 UTC

   We are observing elevated error rates rates in the Prod-EU-2 Public Cloud environment. Users may experience authentication issues. We are currently investigating the issue for root cause and will update when our status changes.

3. resolved 2025-11-09 20:38 UTC

   The elevated errors observed in the affected space have subsided and authentication functionality 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.

4. postmortem 2025-11-24 20:17 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Tenant Logs

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-08 01:58 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.

2. identified 2025-11-08 02:13 UTC

   We are investigating an issue occurring within the AU-1 Public Cloud environment that is impacting tenant logging functionality. We will continue to post updates as we progress in our investigation and as our status changes.

3. identified 2025-11-08 02:26 UTC

   We are continuing to investigate the issue with tenant log streaming functionality. An assessment of recent changes to the affected environment is being conducted to narrow down potential root cause. We will continue to update as our status changes or as we make progress in our...

4. identified 2025-11-08 02:39 UTC

   We have narrowed down the issue to a potential configuration discrepancy, and we are currently in the process of remediating the issue. We will continue to update as our status changes.

5. monitoring 2025-11-08 03:03 UTC

   We've performed a configuration change to the affected environment and are observing successful recovery in logging functionality. We are monitoring the environment to ensure stability.

6. resolved 2025-11-08 03:19 UTC

   After monitoring the environment for stability, we have confirmed that logging is functioning successfully, remediating impact to users. We consider this issue resolved.

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication, Multi-factor Authentication, Management API, Auth0 Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-29 08:14 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.

2. identified 2025-10-29 08:29 UTC

   We have identified an issue with Actions that is showing signs of recovery and our Engineering team are continuing to work on the issue. We will continue to update every 15 minutes.

3. monitoring 2025-10-29 08:37 UTC

   Error rates have recovered to normal levels across both APIs, we are continuing to monitor

4. identified 2025-10-29 10:22 UTC

   We have identified an uptick in error rates re-occurring and are investigating

5. identified 2025-10-29 11:12 UTC

   We have identified a recurring issue and are taking actions for remediation

6. identified 2025-10-29 11:27 UTC

   Our incident team is continuing work on resolving this incident. We have no estimated time of resolution at this time. We will provide an update every 15 minutes.

7. identified 2025-10-29 11:43 UTC

   Our incident team is continuing work on resolving this incident.

8. monitoring 2025-10-29 12:08 UTC

   We are seeing improvements in the error rate following remediatory actions and are now monitoring the system

9. monitoring 2025-10-29 12:48 UTC

   We are working with our provider on additional preventative actions and have successfully stabilized error rates in the environment. Our Engineering team will continue to monitor this event over the next several hours to ensure no recurrence of this issue.

10. resolved 2025-10-29 15:27 UTC

    Services are now 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.

11. postmortem 2025-11-11 16:33 UTC

    A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-09 14:38 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.

2. monitoring 2025-10-09 14:50 UTC

   We have identified the root cause of the issue and have performed a rollback to the affected environment. Users would not have been able to use the Auth0 Dashboard during the impact window. We are seeing recovery after our rollback and are monitoring to ensure full stability. We...

3. resolved 2025-10-09 14:56 UTC

   Services has been restored. We will continue to monitor the environment to ensure the issue does not reoccur. A root cause analysis (RCA) will be posted here within 14 days. We sincerely apologize for the impact this had on you.

4. postmortem 2025-10-23 23:56 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard, Auth0 Dashboard

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-18 14:39 UTC

   We are currently investigating an issue with Auth0 Dashboard. We will provide more information here shortly as our investigation progresses.

2. investigating 2025-09-18 14:47 UTC

   We are continuing to review errors from this issue and provide updates as our investigation progresses. We will provide more information here in approximately 15 minutes.

3. identified 2025-09-18 14:56 UTC

   Our Engineering team has identified the root cause of this issue and customers may notice errors when selecting the save button after making changes on the Auth0 Dashboard. We are working urgently applying necessary mitigation actions and we will provide another update here in...

4. identified 2025-09-18 15:14 UTC

   Our Engineering team has reviewed the change to fix this issue and we will confirm shortly once we are seeing improvement.

5. monitoring 2025-09-18 15:17 UTC

   Our Engineering team has applied the necessary changes and we are now seeing recovery and monitoring this issue.

6. resolved 2025-09-18 16:08 UTC

   Services have 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.

7. postmortem 2025-10-01 22:29 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250918\_Auth0\_Dashboard\_Settings\_Not\_Saving.pdf](https://cdn.auth0.com/blog/20250918_Auth0_Dashboard_Settings_Not_Saving.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Machine to Machine Authentication

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-10 19:07 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.

2. identified 2025-09-10 19:25 UTC

   We have determined that impact is limited to a single customer environment. Our Engineering team has confirmed that the issue was due to a configuration set by the customer and we are working with them directly to mitigate the issue.

3. resolved 2025-09-10 19:36 UTC

   Our Engineering team has confirmed that the issue was due to a configuration set by the customer. We are resolving this incident, and our Support teams will continue to work on assisting our customers with improving these errors.

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication, User Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication, Machine to Machine Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-21 18:18 UTC

   We are investigating reports of network latency impacting specific US localities due to an issue on one of our Edge Provider's colocations. We are working urgently to investigate this issue and we will advise shortly as our investigation progresses.

2. identified 2025-08-21 18:29 UTC

   Our Edge Provider has identified an issue that is impacting traffic and is working towards mitigation urgently. We will provide additional updates here in approximately 15 minutes as we work with them to understand the root cause of this issue and remediate impact to our...

3. identified 2025-08-21 18:42 UTC

   Our Edge Provider is working towards a fix. This impacts customers utilizing traffic specifically from their Virginia-based colocation. We are working with our provider directly on getting additional updates as they work to resolve this issue as soon as possible. We will post an...

4. identified 2025-08-21 19:13 UTC

   We are seeing some resolution for these network errors as our Edge Provider has implemented some additional mitigation actions. We will provide further updates in 15 minutes as we continue to work with our provider.

5. monitoring 2025-08-21 19:51 UTC

   Error rates have subsided and our team is monitoring.

6. resolved 2025-08-21 20:07 UTC

   Services have 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.

7. postmortem 2025-09-03 22:07 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250821\_Edge\_Provider\_Colocation\_Failure\_Impacting\_US\_Traffic.pdf](https://cdn.auth0.com/blog/20250821_Edge_Provider_Colocation_Failure_Impacting_US_Traffic.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, User Authentication, User Authentication

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-18 08:07 UTC

   We are currently investigating an incident that impacting loginWithPopup flows. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. investigating 2025-07-18 10:03 UTC

   We are continuing to investigate the issue to determine the root cause.

3. identified 2025-07-18 10:31 UTC

   We have identified the cause, and are working on providing a resolution.

4. monitoring 2025-07-18 10:37 UTC

   We have rolled back the change impacting popup authentication flows and are continuing to monitor the system.

5. resolved 2025-07-18 11:03 UTC

   Services have 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.

6. postmortem 2025-07-30 22:01 UTC

   A root-cause analysis for this issue has been performed and is now available at:...

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Multi-factor Authentication, Email Delivery

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-14 09:55 UTC

   We are currently investigating a resurfaced issue that was impacting our notification services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

2. monitoring 2025-07-14 10:00 UTC

   We applied a fix for the issue and we are monitoring the system.

3. resolved 2025-07-14 10:49 UTC

   Services have been restored. We sincerely apologize for the impact this had on you and your users.

4. postmortem 2025-07-25 19:47 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250714\_Increased\_Error\_Rates\_in\_EU2\_Public\_Cloud.pdf](https://cdn.auth0.com/blog/20250714_Increased_Error_Rates_in_EU2_Public_Cloud.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.

Affected: User Authentication, Multi-factor Authentication, Email Delivery

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-14 05:50 UTC

   We are experiencing a partial service disruption on email and SMS notifications, which will impact Passwordless and Email/SMS OTP sending. This is currently being investigated.

2. monitoring 2025-07-14 08:10 UTC

   We applied a fix for the notifications issue and are monitoring the system.

3. resolved 2025-07-14 08:48 UTC

   Services have been restored. We sincerely apologize for the impact this had on you and your users.

4. postmortem 2025-07-25 19:47 UTC

   A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250714\_Increased\_Error\_Rates\_in\_EU2\_Public\_Cloud.pdf](https://cdn.auth0.com/blog/20250714_Increased_Error_Rates_in_EU2_Public_Cloud.pdf)

Excerpts are shortened. Read the full incident on Auth0's status page.