Auth0 장애 기록

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 14일 AM 2:49 UTCinvestigating

   우리는 현재 우리의 서비스에 영향을 미치는 사건을 조사하고 있습니다. 우리의 팀은 뿌리 원인을 이해하고 문제를 완화하기 위해 적극적으로 노력하고 있습니다. 우리는 더 많은 정보를 수집하여 업데이트 할 것입니다.

2. 2026년 7월 14일 AM 3:08 UTCidentified

   우리는 우리의 tenant 로그 스트리밍 서비스에 문제가 확인했습니다. 우리는 사건 상태의 변화와 우리의 완화 노력 진행으로 더 많은 업데이트를 제공 할 것입니다.

3. 2026년 7월 14일 AM 3:42 UTCidentified

   우리는 우리의 tenant 로그 스트리밍 서비스에 문제가 확인했습니다. 우리는 뿌리 원인을 조사하고 사건 상태의 변화와 우리의 완화 노력 진행으로 더 업데이트를 제공할 것입니다. 이 문제는 핵심 인증 서비스에 영향을 미치지 않습니다.

4. 2026년 7월 14일 AM 4:26 UTCidentified

   우리는 우리의 tenant 로그 스트리밍 서비스에 루트 원인을 조사 계속. 10개의 로그는 Auth0 관리 대시보드를 통해 접근할 수 있습니다. 우리는 사건 상태의 변화와 우리의 완화 노력 진행으로 7am UTC에 다음 업데이트를 제공 할 것입니다. 이 문제는 핵심 인증 서비스에 영향을 미치지 않습니다.

5. 2026년 7월 14일 AM 5:29 UTCresolved

   서비스 복원되었습니다. 우리는 진심으로 당신에게 영향을 미치는 영향에 대해 사과하고 사용자.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 26일 AM 6: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. 2026년 6월 26일 AM 7:23 UTCmonitoring

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

3. 2026년 6월 26일 AM 7: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. 2026년 7월 8일 PM 5: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)

1. 2026년 6월 22일 PM 3: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. 2026년 6월 22일 PM 3: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. 2026년 6월 22일 PM 4: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. 2026년 6월 22일 PM 4: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. 2026년 7월 2일 AM 2: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)

1. 2026년 6월 22일 PM 3: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. 2026년 6월 22일 PM 3: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. 2026년 6월 22일 PM 4: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. 2026년 6월 22일 PM 4: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. 2026년 7월 2일 AM 2: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)

1. 2026년 6월 11일 AM 5: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. 2026년 6월 11일 AM 6:55 UTCmonitoring

   We are currently monitoring the incident

3. 2026년 6월 11일 AM 7: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. 2026년 6월 23일 PM 10: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)

1. 2026년 6월 1일 PM 6: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. 2026년 6월 1일 PM 6: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. 2026년 6월 1일 PM 7: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. 2026년 6월 1일 PM 7: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. 2026년 6월 9일 PM 10: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)

1. 2026년 5월 21일 PM 6: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. 2026년 5월 21일 PM 6: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. 2026년 6월 1일 PM 8: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)

1. 2026년 4월 28일 AM 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. 2026년 4월 28일 PM 9: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. 2026년 5월 8일 PM 7: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)

1. 2026년 4월 28일 AM 5: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. 2026년 4월 28일 AM 5: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. 2026년 4월 28일 AM 5: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. 2026년 5월 8일 PM 7: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)

1. 2026년 4월 22일 PM 6: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. 2026년 4월 22일 PM 7: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. 2026년 5월 7일 PM 4: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)

1. 2026년 4월 22일 PM 6: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. 2026년 4월 22일 PM 7: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. 2026년 5월 7일 PM 4: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)