Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Histórico de interrupções do Auth0

    12 Auth0 incidents · Ebrel 2026 — official updates, affected components, duration and resolution details.

    Voltar ao status atual

    Questão de Página de Utilização de Quota no Centro de Suporte

    Início 23 Gouere 2026 da 16:06 UTC · 0m

    OutageMajor incident
    Componentes afetados
    Auth0 CA-1

      Traduzido automaticamente da atualização oficial do incidente.

      Detectamos um problema.

      Início 14 Gouere 2026 da 02:49 UTC · 2h 40m

      OutageMajor incident
      Componentes afetados
      Auth0 US-1 - Tenant LogsAuth0 US-1
      1. 14 Gouere 2026 da 02:49 UTCinvestigating

        Estamos a investigar um incidente que afectou os nossos serviços. Nossa equipe está trabalhando ativamente para entender a causa raiz e mitigar o problema. Forneceremos atualizações à medida que reunirmos mais informações.

      2. 14 Gouere 2026 da 03:08 UTCidentified

        Identificámos um problema com o nosso serviço de streaming de registros de inquilinos. Nós forneceremos atualizações adicionais com mudanças no status do incidente e à medida que nossos esforços de mitigação progredirem.

      3. 14 Gouere 2026 da 03:42 UTCidentified

        Identificámos um problema com o nosso serviço de streaming de registros de inquilinos. Continuamos a investigar a causa raiz e forneceremos atualizações adicionais com mudanças no status do incidente e com o progresso dos nossos esforços de mitigação. Este problema não está impactando nenhum serviço de autenticação principal.

      4. 14 Gouere 2026 da 04:26 UTCidentified

        Continuamos a investigar a causa raiz em nosso serviço de streaming de registros de inquilinos. Os logs dos inquilinos são acessíveis através do painel de gerenciamento Auth0. Forneceremos a próxima atualização às 7h UTC com quaisquer mudanças no status do incidente e conforme nossos esforços de mitigação progridem. Este problema não está impactando nenhum serviço de autenticação principal.

      5. 14 Gouere 2026 da 05:29 UTCresolved

        Os serviços foram restaurados. Nós sinceramente pedimos desculpas pelo impacto que isso teve em você e seus usuários.

      Traduzido automaticamente da atualização oficial do incidente.

      We have detected an issue.

      Início 26 Mezheven 2026 da 06:57 UTC · 53m

      OutageMajor incident
      Componentes afetados
      Auth0 US-1 - AuthenticationAuth0 US-1
      1. 26 Mezheven 2026 da 06:57 UTCinvestigating

        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. 26 Mezheven 2026 da 07:23 UTCmonitoring

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

      3. 26 Mezheven 2026 da 07:50 UTCresolved

        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. 8 Gouere 2026 da 17:31 UTCpostmortem

        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)

      Elevated Errors on US-5 Public Cloud Environment

      Início 22 Mezheven 2026 da 15:48 UTC · 40m

      OutageMajor incident
      Componentes afetados
      Auth0 US-5 - AuthenticationAuth0 US-5
      1. 22 Mezheven 2026 da 15:41 UTCinvestigating

        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. 22 Mezheven 2026 da 15:48 UTCidentified

        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.

      3. 22 Mezheven 2026 da 16:22 UTCmonitoring

        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.

      4. 22 Mezheven 2026 da 16:28 UTCresolved

        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. 2 Gouere 2026 da 02:21 UTCpostmortem

        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)

      Elevated Errors on AU-1 Public Cloud Environment

      Início 22 Mezheven 2026 da 15:21 UTC · 1h 7m

      OutageMajor incident
      Componentes afetados
      Auth0 AU - Authentication
      1. 22 Mezheven 2026 da 15:21 UTCinvestigating

        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. 22 Mezheven 2026 da 15:48 UTCidentified

        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.

      3. 22 Mezheven 2026 da 16:22 UTCmonitoring

        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.

      4. 22 Mezheven 2026 da 16:28 UTCresolved

        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. 2 Gouere 2026 da 02:22 UTCpostmortem

        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)

      We have detected an issue.

      Início 11 Mezheven 2026 da 05:49 UTC · 1h 21m

      OutageMajor incident
      1. 11 Mezheven 2026 da 05:49 UTCinvestigating

        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. 11 Mezheven 2026 da 06:55 UTCmonitoring

        We are currently monitoring the incident

      3. 11 Mezheven 2026 da 07:10 UTCresolved

        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. 23 Mezheven 2026 da 22:07 UTCpostmortem

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

      Elevated Errors on US-1 Public Cloud

      Início 1 Mezheven 2026 da 18:23 UTC · 1h 0m

      OutageMajor incident
      Componentes afetados
      Auth0 US-1 - Authentication
      1. 1 Mezheven 2026 da 18:23 UTCinvestigating

        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. 1 Mezheven 2026 da 18:32 UTCidentified

        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. 1 Mezheven 2026 da 19:11 UTCmonitoring

        The Engineering team has applied a fix for the issue and we're monitoring the environment to ensure stability. Errors rates on the affected environment are beginning to subside. Due to resource exhaustion observed on the infrastructure supporting the environment, we have scaled up these resources to mitigate impact. A full investigation into the root cause of the issue will continue. We'll provide further update as our status changes.

      4. 1 Mezheven 2026 da 19:23 UTCresolved

        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. 9 Mezheven 2026 da 22:31 UTCpostmortem

        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)

      [Retroactive] Elevated Errors in Authentication API

      Início 21 Mae 2026 da 18:10 UTC · 1m

      OutageMajor incident
      Componentes afetados
      Auth0 EU-1 - Authentication
      1. 21 Mae 2026 da 18:10 UTCidentified

        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. 21 Mae 2026 da 18:11 UTCresolved

        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. 1 Mezheven 2026 da 20:16 UTCpostmortem

        A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/website/2026-05-20_-_Elevated_Errors_on_Multiple_EU-Region_Cloud_Environments.pdf](https://cdn.auth0.com/website/2026-05-20_-_Elevated_Errors_on_Multiple_EU-Region_Cloud_Environments.pdf)

      Elevated Errors on Public Cloud Environments

      Início 28 Ebrel 2026 da 10:00 UTC · 11h 31m

      IssuesMinor incident
      Componentes afetados
      Auth0 US-1 - Authentication
      1. 28 Ebrel 2026 da 10:00 UTCidentified

        We're currently investigating a disruption to Auth0 Services on the Public Cloud environment. Our third-party Edge provider has confirmed an issue originating from within their services. This event specifically impacts customers who are utilizing self-managed custom domains for Authentication, MFA, and Management API. We're closely monitoring for progress from our provider following their investigation. We'll provide updates as we gather more information and as our status changes.

      2. 28 Ebrel 2026 da 21:32 UTCresolved

        Our third-party Edge provider has reported that their service disruption has been mitigated within their environment. We've observed recovery for all previously affected Auth0 services and now see stability in the Public Cloud environment. After no further recurrence of the issue, we're now marking this incident as resolved. A root cause analysis (RCA) will be posted here within 14 business days. We sincerely apologize for the impact this had on you and your users.

      3. 8 Mae 2026 da 19:38 UTCpostmortem

        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)

      Regional Connectivity Issues in CA Public Cloud

      Início 28 Ebrel 2026 da 05:03 UTC · 44m

      OutageMajor incident
      Componentes afetados
      Auth0 CA-1 - Authentication
      1. 28 Ebrel 2026 da 05:03 UTCinvestigating

        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. 28 Ebrel 2026 da 05:30 UTCidentified

        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. 28 Ebrel 2026 da 05:46 UTCresolved

        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. 8 Mae 2026 da 19:29 UTCpostmortem

        A root-cause analysis for this issue has been performed and is now available at: [https://cdn.auth0.com/blog/20260428\_-\_Error\_Rates\_caused\_by\_Regional\_Infrastructure\_Failure.pdf](https://cdn.auth0.com/blog/20260428_-_Error_Rates_caused_by_Regional_Infrastructure_Failure.pdf)

      Elevated Errors on Public Cloud Environments

      Início 22 Ebrel 2026 da 18:29 UTC · 31m

      OutageMajor incident
      Componentes afetados
      Auth0 EU-1 - Authentication
      1. 22 Ebrel 2026 da 18:29 UTCinvestigating

        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. 22 Ebrel 2026 da 19:01 UTCresolved

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

      3. 7 Mae 2026 da 16:36 UTCpostmortem

        A root-cause analysis for this issue has been performed and is now available at:[https://cdn.auth0.com/blog/20260422\_-\_Elevated\_Errors\_on\_Public\_Cloud\_from\_DNS\_Resolution\_Failures.pdf](https://cdn.auth0.com/blog/20260422_-_Elevated_Errors_on_Public_Cloud_from_DNS_Resolution_Failures.pdf)

      Elevated Errors on Public Cloud Environments

      Início 22 Ebrel 2026 da 18:29 UTC · 32m

      OutageMajor incident
      Componentes afetados
      Auth0 US-3 - Authentication
      1. 22 Ebrel 2026 da 18:29 UTCinvestigating

        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. 22 Ebrel 2026 da 19:01 UTCresolved

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

      3. 7 Mae 2026 da 16:31 UTCpostmortem

        A root-cause analysis for this issue has been performed and is now available at:[https://cdn.auth0.com/blog/20260422\_-\_Elevated\_Errors\_on\_Public\_Cloud\_from\_DNS\_Resolution\_Failures.pdf](https://cdn.auth0.com/blog/20260422_-_Elevated_Errors_on_Public_Cloud_from_DNS_Resolution_Failures.pdf)