Konta Utilization Page Issue on Support Center
OutageBüyük çaplı olay
Etkilenen bileşenler
Auth0 CA-1
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
12 Auth0 incidents · Nisan 2026 — official updates, affected components, duration and resolution details.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Şu anda hizmetlerimizi etkileyen bir olayı araştırıyoruz. Ekibimiz aktif olarak kök nedenini anlamak ve sorunu azaltmak için çalışıyor. Daha fazla bilgi topladığımız gibi güncellemeler vereceğiz.
Onant günlük akış hizmetimizle bir sorun tespit ettik. Olay statüsündeki değişikliklerle daha fazla güncelleme sağlayacağız ve tazminat çabalarımız ilerledikçe.
Onant günlük akış hizmetimizle bir sorun tespit ettik. Kök nedenini incelemeye devam ediyoruz ve olay durumundaki değişikliklerle ve masyon çabalarımız ilerledikçe daha fazla güncelleme sağlayacaktır. Bu konu herhangi bir temel doğrulama hizmeti etkilemez.
10. günlük akış hizmetimizde kök nedenini incelemeye devam ediyoruz. Tenant loglar Auth0 yönetim paneli aracılığıyla erişilebilir. Olay durumundaki herhangi bir değişiklikle 7am UTC'de bir sonraki güncelleme yapacağız ve mitigation çabalarımız ilerledikçe. Bu konu herhangi bir temel doğrulama hizmeti etkilemez.
Hizmetler restore edilmiştir. Bunun sizin ve kullanıcılarınızın üzerindeki etkisi için içtenlikle özür dileriz.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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)
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 monitoring the incident
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-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)
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 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.
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.
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.
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)
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.
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.
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)
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.
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.
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)
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 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.
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/20260428\_-\_Error\_Rates\_caused\_by\_Regional\_Infrastructure\_Failure.pdf](https://cdn.auth0.com/blog/20260428_-_Error_Rates_caused_by_Regional_Infrastructure_Failure.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.
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.
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)
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.
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.
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)