Is Auth0 Down Right Now? Check if there is a current outage ongoing.

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.

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

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.

We applied a fix for the issue and are monitoring the system. The alternative email <redacted> is deactivated, please use the support centre (https://support.auth0.com) to open the tickets if you need to contact us.

We are investigating an issue with Support Center that is preventing customers from opening new cases with the Support team. As a backup, you can email us at < >, and a support case will be automatically created for you. Once the incident is resolved, this email address will stop accepting emails.

We are currently investigating an incident that impacted our services of the tenant dashboard and support centre. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20250515\_Increased\_Error\_Rates\_in\_US3\_Public\_Cloud\_Environment.pdf](https://cdn.auth0.com/website/20250515_Increased_Error_Rates_in_US3_Public_Cloud_Environment.pdf)

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.

The errors for this issue have now subsided and services are operating as expected. We are continuing to monitor and review this issue.

We have isolated and identified the errors for this issue and we are continuing to review this with our Engineering team.

Our Engineering team is still reviewing this issue. We've confirmed that there was impact to management API calls in Public Cloud US-3. We will provide additional updates in approximately 15 minutes.

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.

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

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.

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

Our Engineering team has identified the mitigation actions that need to be put in place for this issue.

Our Engineering team has identified the root cause of this issue and we are reviewing if any additional mitigation actions are needed. We will post additional updates here in 15 minutes.

Our Engineering team is observing additional errors impacting US-3. We are continuing to investigate this issue and will post updates here as our investigation progresses.

Services has been restored. Auth0 management dashboard user details page is working as expected.

We applied a fix for the issue and are monitoring the system. Please clear the cache of the browser and refresh the page to have the fix loaded.

We continue to investigate an issue that is impacting our Auth0 Management Dashboard. Auth0 tenant administrators are currently unable to load user details in the UI. Customers are advised to use Auth0 management API endpoints to retrieve and manage user profiles.

We are currently investigating an issue that is impacting our Auth0 Management Dashboard. Auth0 tenant administrators are currently unable to load user details in the UI.

We are currently investigating an issue that is impacting our Auth0 Management Dashboard. Auth0 tenant administrators are currently unable to load user details in the UI.

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

Services has been stable. 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.

We detected elevated error rates on Authentication API between 18:32 and 18:37 UTC. The issue self-resolved and no actions are required from our customers. We are continuing to monitor the system.

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 are currently investigating an incident that impacted our services of the tenant dashboard and support centre.Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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

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

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.

Services are now functioning as expected and our team is observing full recovery. We are reviewing any potential mitigation actions and no customer action is required at this time.

Our Engineering team has isolated the traffic pattern and what we believe the root cause of this issue to be. We will provide an additional update here in 15 minutes as our team continues to review this issue. This issue is ongoing and being actively investigated and triaged.

Our Engineering team is continuing to review increased error rates impacting our public cloud US-4 region. We will post additional updates here as our investigation progress in approximately 15 minutes.

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.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2025-04-23-User\_Logins\_Failed\_in\_AU-1\_and\_JP-1\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/2025-04-23-User_Logins_Failed_in_AU-1_and_JP-1_Public_Cloud_Environments.pdf)

Following reports of some customers in JP-1 having issues logging in, our Engineering team investigated and fixed these errors between 01:50 and 02:12 UTC. The errors were resolved at 02:31 UTC. 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.

We applied a fix for the issue and are continuing to monitor the system.

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

Our Engineering team is actively continuing to review this issue and engage additional resources. We have not yet identified the root cause of this issue and we will post additional updates here in 15 minutes as our review progresses.

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.

Services has been stable. 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.

We detected elevated error rates on Authentication API between 18:32 and 18:37 UTC. The issue self-resolved and no actions are required from our customers. We are continuing to monitor the system.

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 detected elevated error rates on Authentication API between 18:32 and 18:37 UTC. The issue self-resolved and no actions are required from our customers. We are continuing to monitor the system.

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.

Following review of this issue a misconfiguration that was made as part of routine / ongoing work caused limited issues with full support center functionality from approximately 16:30 to 17:30 UTC. Our Engineering team has reverted these changes and observed full recovery. Should you have any further questions or concerns, please contact our support center. Core authentication and customer logins were not affected as part of this issue. Our Engineering team has identified that this primarily impacted the ability to run reports from support center. No further customer action is required at this time.

Our support center is now fully operational and functioning as expected. Customers may have noticed limited impact to certain support center functionality such as use of reports. Our Engineering team is reviewing this retroactively and you can contact our support team should you have any further questions or concerns.

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

Our Engineering team has identified what we believe to be the root cause of this issue and we are reviewing mitigation actions.

Our Engineering team is actively aware of an ongoing issue that is impacting our ability to fully utilize our customer support portal. We will post additional updates here as our investigation progresses.

We have isolated that this issue was caused by a misconfiguration. Any customers who require further assistance should contact our Support teams and refer to the following article which provides guidance on end of life rollout for mandatory use of SNI at - https://support.auth0.com/help/s/article/End-of-Life-Rollout-for-Mandatory-Use-of-SNI-for-HTTPS-Requests

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.

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

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.

Support Center Services has been restored.

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

We are investigating an issue with the Support Center that is preventing customers from logging in and managing support cases.

Our Engineering team has identified what we believe to be the root cause of this issue and we are reviewing mitigation actions.

Our Engineering team is actively aware of an ongoing issue that is impacting our ability to fully utilize our customer support portal. We will post additional updates here as our investigation progresses.

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

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.

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

Our team is continuing to review the results of mitigation actions that were taken for all impacted environments. While we are still seeing this issue we are working urgently to completely resolve this. We will post another update here in approximately 15 minutes.

Our mitigation actions are now underway and it will take several minutes for these actions to complete. We will confirm here with additional updates in approximately 15 minutes.

Our Engineering team has identified and isolated the root cause of this issue. We are working urgently on mitigation actions to address this and we will post further updates here in approximately 15 minutes our efforts progress.

We are investigating an incident that impacted logins to the Auth0 dashboard with Google as the identity provider. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250414\_Increased\_Error\_Rate\_for\_US3\_Public\_Cloud\_Environment.pdf](https://cdn.auth0.com/blog/20250414_Increased_Error_Rate_for_US3_Public_Cloud_Environment.pdf)

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

We applied a fix for this issue and error rates have now subsided. We are continuing to monitor the environment.

Our Engineering team has identified what we believe to be the root cause of this issue and we are taking additional mitigation measures to limit the impact our customers are currently experiencing. We will post an additional update here in approximately 15 minutes once these actions have completed.

Our Engineering team is actively continuing to review this issue and engage additional resources. We have not yet identified the root cause of this issue and we will post additional updates here in 15 minutes as our review progresses. We are currently attempting to identify and isolate the root cause for these error rate spikes.

Our Engineering team is continuing to investigate increased error rates which are impacting our Public Cloud US-3 customers. We will post additional updates here in 15 minutes as we progress.

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.

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.

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

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.

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.

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

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.

Our Engineering team is continuing to review increased error rates impacting our public cloud US-4 region. We will post additional updates here as our investigation progress in approximately 15 minutes.

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.

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

The system has been stable, and the issue did not reoccur. We will continue to investigate the issue’s root cause and provide an analysis within 14 days. We sincerely apologize for the impact this had on you and your users.

We have implemented a fix, and the issue has been resolved.

A limited subset of customers logging into an Organization or performing Management API operations on an Organization related entities would experience server errors on April 10, 2024, from approximately 12:25 to 12:38 UTC. The issue was isolated to Organization-related entities, and other access implementations were unaffected. There is no active impact, and no actions are required from our customers.

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.

We applied a fix for the issue and are continuing to monitor the system.

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

Our Engineering team is actively continuing to review this issue and engage additional resources. We have not yet identified the root cause of this issue and we will post additional updates here in 15 minutes as our review progresses.

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 are investigating an incident that impacted logins to the Auth0 dashboard with Google as the identity provider. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

Our Engineering team is continuing to investigate increased error rates which are impacting our Public Cloud US-3 customers. We will post additional updates here in 15 minutes as we progress.

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.

On April 3, 2025, our Engineering team investigated customer reports of passwordless magic link emails not working for their environments. End users were receiving magic link emails with an 'undefined domain' in the url for magic link . This issue did not affect successful user authentication overall and was isolated to scenarios where tenant admins create a passwordless user using admin API with 'email\_verified=false'. The root cause of this issue was traced back to a code regression our Engineering team introduced. These errors were mitigated following our rollback of the offending code changes in all impacted environments. To prevent this issue from recurring, we are reviewing our functional tests with key learnings from this incident. We sincerely apologize for the impact this issue had on you and your users.

This issue has now been fully resolved. Please contact our Support team should you require any further assistance.

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

Our deployments to remediate this issue are still ongoing and we are beginning to see full recovery for impacted environments. We will post an additional update here over the next few hours as we review the rollout of these deployments and customers will continue to see gradual remediation for this.

Our Engineering team is continuing to rollout a fix for this issue however we have now identified that a very limited subset of users were affected by this. Some users created that are using magic link passwordless verification emails may have encountered an email link issue when attempting to authenticate. We will confirm here in 1-2 hours once our rollout fix for this has completed.

Our Engineering team is continuing to review an issue we identified which has impacted use of one time password magic link for authentication across multiple environments. We are working urgently to remediate this issue and will advise once our mitigation efforts have completed.

Our Engineering team has identified a regression which is impacting end user ability to utilize one time password magic link based authentication. We are working urgently to mitigate this issue and we will post additional updates here in 15 minutes.

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 are investigating an issue with the Support Center that is preventing customers from logging in and managing support cases.

We have implemented a fix, and the issue has been resolved.

A limited subset of customers logging into an Organization or performing Management API operations on an Organization related entities would experience server errors on April 10, 2024, from approximately 12:25 to 12:38 UTC. The issue was isolated to Organization-related entities, and other access implementations were unaffected. There is no active impact, and no actions are required from our customers.

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

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.

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

We are currently investigating an incident that impacted our services. Users are experiencing errors in accessing or making updates in the Auth0 Dashboard. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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

Services has been fully stable at 18:47 UTC and after extended monitoring, we are now closing this incident. 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.

We applied a fix for the issue and the errors are subsiding. We estimate that the errors would be fully resolved in the next 15 minutes. We are continuing to monitor the system.

We are continuing to see intermittent spikes and are actively implementing solutions. We will provide updates as they are available.

Impacted users may experience 5xx or 4xx error codes when attempting to log in. We have identified the root cause of the issue and are working to mitigate the impact. We will provide another update within the next 30 minutes.

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.

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

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.

Error rates in the environment have now subsided and our Engineering team is continuing to monitor following earlier mitigation actions. All services in the environment are now functioning has expected.

Our Engineering team is continuing to work on mitigation actions to rectify the issues we are seeing for authentication in US-3. We will provide additional updates here in 30 minutes as these actions progress.

Our Engineering team has now identified the root cause of these errors in US-3 Public Cloud. We are working urgently to apply mitigation actions for this issue and we will post additional updates here as our mitigation actions progress.

Our Engineering team is actively continuing to review the increased error rates we are observing that are impacting services in our Public Cloud US-3 region. We will continue to post updates here as our investigation progresses.

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.

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

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.

Between 14:59 and 16:05 UTC, we identified service disruptions in Authentication and Management API in our US3 and US4 environments. Impacted users would have experienced 4xx error codes. There is no active impact, and no further action is required from our customers. We will continue to monitor the situation and post updates here.

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

This issue was caused by a code regression in which an incorrect configuration was imported and used. The service in question was imported and mistakenly used on the wrong UI pipeline, causing these errors and our team reverted builds to remove the offending code change. No further action is required by our customer and we do not expect this issue to recur as we’ve flagged this release for internal review.

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.

We applied a fix for the issue and are monitoring the system. Services are now functioning as expected.

We have identified a regression which we believe caused this issue. We are reviewing mitigation of this issue urgently.

We are currently investigating an issue for Auth0 dashboard where customers may be experiencing issues creating new tenants. Our Engineering team is reviewing this and we will advise as our investigation progresses.

> Out of an abundance of caution, we have thoroughly investigated the service interruption encountered in this event and determined that a broad regression was not applicable.  If you are experiencing similar issues, we recommend contacting our Support teams for further assistance.

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.

We have identified the cause, applied a fix for the issue and are monitoring the system.

We are currently investigating an incident that impacted our services. End users will see logins failing for customers using Custom Forms. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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.

We have identified the cause, applied a fix for the issue and are monitoring the system.

We are currently investigating an incident that impacted our services. End users will see logins failing for customers using Custom Forms. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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.

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

We are currently investigating an incident that impacted our services. Users are experiencing errors in accessing or making updates in the Auth0 Dashboard. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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.

We applied a fix for the issue and the errors are subsiding. We estimate that the errors would be fully resolved in the next 15 minutes. We are continuing to monitor the system.

We are continuing to see intermittent spikes and are actively implementing solutions. We will provide updates as they are available.

Impacted users may experience 5xx or 4xx error codes when attempting to log in. We have identified the root cause of the issue and are working to mitigate the impact. We will provide another update within the next 30 minutes.

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.

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

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.

We have identified the cause and working on implementing a fix. We will continue to update every 15 minutes.

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.

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

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.

We are continuing to monitor for any further issues.

Users may have experienced an issue where administrators have partial account visibility when accessing the Manage Dashboard. We have identified the root cause and applied a fix. There is no active impact and we are continuing to monitor the situation.

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.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250301\_-Service\_Interruptions\_on\_Auth0\_Dashboard\_for\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20250301_-Service_Interruptions_on_Auth0_Dashboard_for_Public_Cloud_Environments.pdf)

The Auth0 Dashboard and all impacted support websites (Auth0 Docs (auth0.com/docs), Support Center (support.auth0.com), and Status page (status.auth0.com)) have been stable, and errors have been resolved. 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.

The Manage service has been restored following the implementation of mitigation measures. We have placed additional safeguards to prevent recurrence and will continue to monitor the situation.

We have identified that the Manage service has not fully recovered. Impacted users may experience temporary disruptions accessing the Auth0 Dashboard. Our teams are actively working to resolve the issue. We will provide another update within the next 30 minutes.

The impacted services (https://manage.auth0.com, https://status.auth0.com and https://support.auth0.com) are currently recovering and we will continue to monitor the situation. If you are unable to access these resources, please try logging in again.

We have identified the root cause of the issue and are implementing a fix. We will continue to update every 15 minutes.

We are continuing to investigate an ongoing issue where the Dashboard and the Auth0 Support Center might be temporarily unavailable.

The Auth0 Manage Dashboard is unavailable, and our Engineers have been alerted. This does not affect your authentication transactions, and you can still make management transactions via our Management API. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20250301\_-Service\_Interruptions\_on\_Auth0\_Dashboard\_for\_Public\_Cloud\_Environments.pdf](https://cdn.auth0.com/blog/20250301_-Service_Interruptions_on_Auth0_Dashboard_for_Public_Cloud_Environments.pdf)

The errors stopped at approximately 20:11 UTC and we have not seen any additional spikes at this time. Our engineering team is continuing to investigate the root cause of the issue. We will provide an analysis within 14 days. We sincerely apologize for the impact this had on you and your users.

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

We are currently investigating an incident that impacted our services. Affected users are experiencing issues with Manage Dashboard. We are not seeing errors in Authentication and Management APIs at this time. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

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.

We applied a fix for the issue and are monitoring the system. Services are now functioning as expected.

We have identified a regression which we believe caused this issue. We are reviewing mitigation of this issue urgently.

We are currently investigating an issue for Auth0 dashboard where customers may be experiencing issues creating new tenants. Our Engineering team is reviewing this and we will advise as our investigation progresses.

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

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

Our Engineering team has identified an issue which briefly impacted customers for several minutes in our EU-1 and EU-1 public cloud regions on February 12, 2025. We are continuing to review this issue in further depth and the issue has since been fully resolved and mitigated.

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

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.

Our Engineering team has identified an issue which has impacted customers across our EU-2, JP-1 and US-4 Public Cloud region. This issue is now completely resolved and we are continuing to review the various error rate spikes which impacted customers across multiple time frames.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20250219\_Increased\_Error\_Rates\_Impacting\_US3\_US4\_UK1\_Public\_Cloud.pdf](https://cdn.auth0.com/website/20250219_Increased_Error_Rates_Impacting_US3_US4_UK1_Public_Cloud.pdf)

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.

Our Engineering has identified increased error rates which also impacted some customers in our US-4 Public Cloud region earlier on February 19. This issue is now fully resolved and we are not seeing any further impact.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20250219\_Increased\_Error\_Rates\_Impacting\_US3\_US4\_UK1\_Public\_Cloud.pdf](https://cdn.auth0.com/website/20250219_Increased_Error_Rates_Impacting_US3_US4_UK1_Public_Cloud.pdf)

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.

Our Engineering has identified increased error rates which also impacted some customers in our UK-1 Public Cloud region earlier on February 19. This issue is now fully resolved and we are not seeing any further impact.

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

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.

After applying fixes for the issue we observed the error rates going down to normal levels. We are currently monitoring the system.

We have applied more changes and are monitoring the situation to confirm it resolves the incident. We will continue to update every 15 minutes.

We have made progress on the incident and applied some changes. We will continue to update every 15 minutes.

We have identified the cause and are making progress with the investigation. We will continue to update every 15 minutes.

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.

Following thorough investigation by our Engineering team this issue did not in fact have broad customer impact and was not the result of a broad regression. We have further analyzed the errors and confirmed they were isolated to a single customer environment. We are continuing to work with our Support team on helping assist customers with the error in question and no additional customer action is required to remediate this issue. Please contact our Support team should you have any additional questions or concerns.

The errors were self-resolved, and the services have been stable. We will continue to investigate the issue’s root cause and provide an analysis within 14 days. We sincerely apologize for the impact this had on you and your users.

Between 22:38 and 22:47 UTC, we experienced elevated errors in our EU-1 public cloud environment. Users who were affected would have experienced 5XX error codes or latency when attempting to log in. There is no active impact, and no actions are required from our customers.

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

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.

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

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.

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

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.

Our Engineering team has identified an issue that impacted our services in US-4 from approximately 13:20 to 13:41. This issue has automatically resolved now and we are retroactively reviewing impact to our customers.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2024\_11\_26\_Failing\_Logins\_for\_Requires\_Username\_DB\_Connection\_Settings\_Update.pdf](https://cdn.auth0.com/blog/2024_11_26_Failing_Logins_for_Requires_Username_DB_Connection_Settings_Update.pdf)

Our team has found the root cause: login field is type 'email' now. If our customers experience failing logins as a result - it was possible to login without '@' before - they can enable 'Requires Username' in the connection settings to properly configure the feature and fix the issue.

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.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2024\_11\_26\_Failing\_Logins\_for\_Requires\_Username\_DB\_Connection\_Settings\_Update.pdf](https://cdn.auth0.com/blog/2024_11_26_Failing_Logins_for_Requires_Username_DB_Connection_Settings_Update.pdf)

Our team has found the root cause: login field is type 'email' now. If our customers experience failing logins as a result - it was possible to login without '@' before - they can enable 'Requires Username' in the connection settings to properly configure the feature and fix the issue.

On November 26, our Engineering team identified an issue which was impacting a subset of our customers who rely on username login flows without the use of '@' as part of their custom db configurations. We continue to work with impacted customers who may have been affected by this issue.

We experienced a service disruption due to an issue with one of our upstream providers. Impacted customers received error messages related to a temporary failure in the DNS lookup process from ~09:45 to ~10:10 UTC. The issue had self-resolved, and no actions are required from our customers. We are continuing to monitor the situation and evaluate alternative solutions to enhance the resiliency of our services. We apologize for the impact this has caused you and your users.

Our monitoring alerted us to increased failures in our networking edge at approximately 09:45 UTC on December 5, 2024. Simultaneously, our Support team began receiving reports that customers are experiencing increased errors when attempting to login.

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

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.

We have identified additional impact on Tenant Logs and User Search features.

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

We are currently implementing a fix. We will continue to update every 15 minutes.

We are currently implementing a fix. We will continue to update every 15 minutes.

We have made progress on the incident and are implementing a fix in the coming minutes. We will continue to update every 15 minutes.

We have identified the root cause, and are working on applying a fix as soon as possible. We will continue to update every 15 minutes.

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.

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

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

Our Engineering team has identified an issue which impacted our services for Manage Dashboard from approximately 14:45 to 14:59 UTC on October 28. Services are now restored and functioning as expected.

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

Services have been restored and this issue is resolved. We sincerely apologize for the impact this had on you and your users. Should you have any further concerns, please reach out to our Support team. A root-cause analysis report (RCA) will be posted here within 14 days.

Our Engineering team is now monitoring this issue post mitigation and the fix applied is working as expected.

Our deployment efforts are continuing to progress with the fix for this issue working as expected for the vast majority of our customer base. Our Engineering team is watching any remaining deployment efforts and the fix is working as expected where deployed.

Our deployment efforts are underway to mitigate this issue and we will be gradually rolling out the fix to all affected customer environments over the next few hours. We will post an update here once our mitigation efforts have been completed.

Our Engineering team has identified the code regression which is causing this issue and we are working urgently to address with an updated release. The necessary changes are being reviewed and we will release this fix to impacted customer environments as soon as possible. We will update here in approximately one hour as our mitigation efforts progress.

We are currently investigating an incident that impacted our services. We observed a service degradation for Facebook logins. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2024-09-30-2024-10-09\_-\_Service\_Disruptions\_for\_Auth0\_Dashboard.pdf](https://cdn.auth0.com/blog/2024-09-30-2024-10-09_-_Service_Disruptions_for_Auth0_Dashboard.pdf)

We have not seen any additional spike in error rates at this time, and our engineering team is continuing to investigate the root cause of the issue. We will provide an analysis within 14 days. We sincerely apologize for the impact this had on you and your users.

Between 12:54 and 13:17 UTC, we experienced elevated errors in our Manage Dashboard. Impacted users would have experienced error codes when accessing the dashboard. There is no active impact, and no actions are required from our customers. Our Engineering team is continuing to monitor this issue.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2024-09-30-2024-10-09\_-\_Service\_Disruptions\_for\_Auth0\_Dashboard.pdf](https://cdn.auth0.com/blog/2024-09-30-2024-10-09_-_Service_Disruptions_for_Auth0_Dashboard.pdf)

Services have been restored and are 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.

Our team is continuing to monitor, however we have not seen any new recurrence of this issue and manage dashboard services for customers are continuing to function as expected.

Services have now recovered and our Engineering team is continuing to monitor this issue. Manage dashboard is now functioning as expected.

Our Engineering team has identified the errors which were causing issues on our manage dashboard service. We will post additional updates here shortly.

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.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/2024-09-30-2024-10-09\_-\_Service\_Disruptions\_for\_Auth0\_Dashboard.pdf](https://cdn.auth0.com/blog/2024-09-30-2024-10-09_-_Service_Disruptions_for_Auth0_Dashboard.pdf)

Between 19:30 and 19:50 UTC, our Engineering teams saw a burst of errors impacting the Manage Dashboard. During the impact window, the affected users may have experienced intermittent timeouts and 5xx error codes. End-users may also experience silent failures during the login process or see an error message when attempting to complete the Auth Challenge CAPTCHA on their login page. The errors have subsided at this time, and no action is required from our customer. Our preliminary investigations point towards a network infrastructure-related issue. We are conducting a root cause analysis to understand the underlying reasons for the recent incidents for this service. 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.

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

Services are restored and functioning as expected in the environment. 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.

Our Engineering team is continuing to monitor this environment and we'll advise shortly with additional updates.

We applied a fix for the issue and our Engineering team is continuing to monitor the environment. Error rates have subsided now and services are functioning as expected.

We have identified the infrastructure issue which was triggering errors in this environment and our mitigation actions are completed. We will confirm here once error rates have fully subsided. Additional updates will follow here in approximately 15 minutes.

Our Engineering team is working now on additional scaling actions to work to mitigate this issue while we further analyze and seek to identify the root cause of this event. Those mitigation actions are underway and we will provide additional updates here in 15 minutes.

We are continuing to investigate this issue and we have engaged additional resources to review these errors. We will post additional updates here as we progress in 15 minutes.

We are currently investigating an issue 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 thoroughly investigated the service interruption encountered in this event and determined that a broad regression was not applicable. We are resolving this incident, and no actions are required from our customers.

We have thoroughly investigated the service interruption encountered in this event and determined that a broad regression was not applicable. We are resolving this incident, and no actions are required from our customers.

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.

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

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.

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

We have observed an increase in error rates for login between 15:13 and 15:23 UTC. The impacted users would have experienced increased failures when attempting to login. The error rate has subsided but our engineering teams continue to monitor and investigate. We will provide updates as we gather more information.

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

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 your and your users.

Our network edge provider has implemented a fix, and we are currently monitoring the system.

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

Following extensive investigation of this event by our Engineering team, we have concluded that these errors were caused by a single customer-side misconfiguration and a broad regression was not applicable. Our investigation did not show impact to other customers from this event and we continue to work on improving our monitoring and alerting for these issues. Should you have any further questions or concerns, please reach out to our Support team for further assistance.

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.

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

We have identified the cause and our team are implementing fixes. We will continue to update every 15 minutes.

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.

A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/20240830-Elevated Error Rates in the AU Public Cloud Environment.pdf](https://cdn.auth0.com/website/20240830-ElevatedErrorRatesintheAUPublicCloudEnvironment.pdf)

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.

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

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.

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

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.

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.

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

Services has been stable. 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.

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

We determined that the impacted users may experience failures or timeout errors when attempting to log in. Our team has identified the cause and is implementing a fix. We will continue to update every 15 minutes.

We are currently investigating an incident that impacted our Authentication and Management APIs. 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 not seen any additional spikes in error rates and will be resolving this incident at this time. We have thoroughly investigated the service interruption encountered in this event and determined that the errors indicate issues with a customer configuration. Should you continue to experience timeout errors, please contact our Support teams.

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.