Is Auth0 down?

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.

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

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.

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.

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.

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

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 is not impacting any core authentication services.

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

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.

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

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.

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

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.

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.

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.

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.

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)

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.

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.

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.

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.

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)