Datadog Eu 장애 기록

1. 2026년 7월 24일 PM 11:39 UTCinvestigating

   우리는 현재 몇몇 서비스 체크 감시자가 우리의 EU 지역에서 평가될지도 모르다 문제점을 조사하고 있습니다.

2. 2026년 7월 25일 AM 12:01 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 25일 AM 12:08 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 3일 AM 12:22 UTCinvestigating

   우리는 registry.datadoghq.com에서 Datadog 컨테이너 이미지를 끌어 당기는 오류를 조사하고 있습니다. 이 문제점의 결과로, 몇몇 사용자는 Datadog 대리인, 클러스터 대리인 및 다른 Datadog 콘테이너 이미지를 다운로드하거나 배치할 수 없습니다. 이미 실행중인 컨테이너는 영향을받지 않습니다.

2. 2026년 7월 3일 AM 12:55 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 3일 AM 1:21 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 3일 AM 1:28 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 1일 PM 6:32 UTCinvestigating

   여러 Datadog 제품에 걸쳐 높은 오류율을 투자하고 있습니다.

2. 2026년 7월 1일 PM 6:56 UTCinvestigating

   Fleet Automation, Security Products, Cloudcraft, Cloud Network Monitoring, Serverless, Kubernetes Autoscaling 및 Database Monitoring을 포함한 여러 제품에서 높은 오류율을 조사하고 있습니다.

3. 2026년 7월 1일 PM 7:11 UTCidentified

   우리는 높은 오류율의 문제점을 확인하고 완화 활동을 통해 일하고 있습니다.

4. 2026년 7월 1일 PM 7:19 UTCmonitoring

   우리는 소송 작업을 배포하고 복구를 모니터링하고 있습니다.

5. 2026년 7월 1일 PM 7:44 UTCmonitoring

   우리는 상황을 모니터링하고 추가 예방 조치를 취하고 있습니다.

6. 2026년 7월 1일 PM 8:31 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 6월 22일 AM 9:30 UTCinvestigating

   We are investigating increased latency processing Metrics. As a result of this issue, some users may see delays or gaps for metrics on graphs.

2. 2026년 6월 22일 AM 9:46 UTCinvestigating

   We have improvement in some Monitors.

3. 2026년 6월 22일 AM 10:27 UTCinvestigating

   We are still investigating. Only process metrics and process check monitors are still affected.

4. 2026년 6월 22일 AM 11:49 UTCmonitoring

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

5. 2026년 6월 22일 PM 12:13 UTCresolved

   This incident has been resolved.

1. 2026년 6월 19일 PM 1:18 UTCinvestigating

   We are investigating increased latency processing data. As a result of this issue, some users may see gaps or delays in RUM and other product graphs as well as empty or partial query results. To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.

2. 2026년 6월 19일 PM 1:30 UTCidentified

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and it will be backfilled and available once the services are operational again.

3. 2026년 6월 19일 PM 1:38 UTCmonitoring

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

4. 2026년 6월 19일 PM 3:11 UTCresolved

   This incident has been resolved.

1. 2026년 6월 12일 PM 7:02 UTCmonitoring

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and notifications will be caught up once the service is operational again.

2. 2026년 6월 12일 PM 7:14 UTCresolved

   This incident has been resolved.

1. 2026년 6월 2일 PM 1:42 UTCinvestigating

   We are investigating increased latency across multiple products. As a result of this issue, some users may see delays in data across the platform.

2. 2026년 6월 2일 PM 2:05 UTCinvestigating

   We are currently investigating an issue affecting multiple products. During this time, some customers may experience: Delayed or missing alert notifications for RUM, Synthetics, APM, and Log-based monitors Errors or delays when querying Logs, including in Log Explorer and Live Tail Delays or gaps in Event Management data Errors or failures in Error Tracking, Cloud SIEM, and Session Replay Degraded performance across Software Delivery products, including CI Visibility Broader platform degradation and intermittent request failures across services

3. 2026년 6월 2일 PM 2:30 UTCinvestigating

   We are continuing to investigate an issue affecting multiple products. During this time, some customers may experience: Delayed or missing alert notifications for RUM, Synthetics, APM, and Log-based monitors Errors or delays when querying Logs, including in Log Explorer and Live Tail Delays or gaps in Event Management data Errors or failures in Error Tracking, Cloud SIEM, and Session Replay Degraded performance across Software Delivery products, including CI Visibility Broader platform degradation and intermittent request failures across services

4. 2026년 6월 2일 PM 2:58 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2026년 6월 2일 PM 3:20 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026년 6월 2일 PM 3:30 UTCresolved

   This incident has been resolved.

1. 2026년 5월 21일 PM 6:59 UTCinvestigating

   We are investigating delays in Monitors Notifications, which began at 19:35 UTC

2. 2026년 5월 21일 PM 7:20 UTCidentified

   We have identified the underlying issue and are working on a fix. Delayed Monitor Notifications are limited to only distribution monitors.

3. 2026년 5월 21일 PM 7:28 UTCmonitoring

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

4. 2026년 5월 21일 PM 7:38 UTCresolved

   This incident has been resolved.

1. 2026년 5월 16일 AM 2:22 UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. 2026년 5월 16일 AM 2:39 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 5월 16일 AM 3:08 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026년 5월 16일 AM 3:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2026년 5월 16일 AM 3:42 UTCresolved

   This incident has been resolved and Azure metrics are reporting as expected.

1. 2026년 4월 30일 AM 8:18 UTCinvestigating

   We are investigating degraded performance with the Web Application.

2. 2026년 4월 30일 AM 9:02 UTCinvestigating

   We have identified the underlying issue and are working on a fix.

3. 2026년 4월 30일 AM 9:31 UTCinvestigating

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

4. 2026년 4월 30일 PM 12:32 UTCresolved

   This incident has been resolved.

1. 2026년 4월 16일 PM 12:52 UTCinvestigating

   We are currently investigating an issue where customers in our EU region might experience issues searching, creating, and updating their monitor and SLO configurations through the web application or API. As a result, dashboard widgets based on monitors or SLOs are also affected. Monitor alerts and SLO evaluations are not affected.

2. 2026년 4월 16일 PM 1:35 UTCinvestigating

   We are continuing to investigate the issue where customers in our EU region might experience issues searching, creating, and updating their monitor and SLO configurations through the web application or API. As a result, dashboard widgets based on monitors or SLOs are also affected. Monitor alerts and SLO evaluations are not affected.

3. 2026년 4월 16일 PM 2:21 UTCidentified

   We have identified the underlying issue and are working on a fix.

4. 2026년 4월 16일 PM 2:28 UTCmonitoring

   We have deployed a fix and we are monitoring the results. We will provide another update once the service is fully operational.

5. 2026년 4월 16일 PM 2:48 UTCresolved

   This incident has been resolved.

1. 2026년 3월 19일 AM 12:55 UTCinvestigating

   We are investigating an issue causing some metric monitors to intermittently report "No Data" status. This primarily affects monitors based on distribution metrics. Monitor alerting may be unreliable during this time. We are actively investigating and will provide updates as available.

2. 2026년 3월 19일 AM 2:05 UTCinvestigating

   We are continuing to investigate the issue and will provide updates as available.

3. 2026년 3월 19일 AM 2:39 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 3월 19일 AM 2:53 UTCresolved

   This incident has been resolved.

1. 2026년 3월 13일 AM 9:37 UTCinvestigating

   We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.

2. 2026년 3월 13일 AM 9:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 13일 AM 9:56 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 3월 13일 AM 10:28 UTCresolved

   This incident has been resolved.

1. 2026년 2월 5일 PM 4:01 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 2월 5일 PM 4:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 5일 PM 4:32 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 2026년 2월 5일 PM 4:51 UTCidentified

   We are continuing to work on a fix for this issue.

5. 2026년 2월 5일 PM 5:01 UTCidentified

   We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue.

6. 2026년 2월 5일 PM 5:24 UTCmonitoring

   We have observed full recovery of monitors and will continue to monitor

7. 2026년 2월 5일 PM 8:04 UTCresolved

   This incident has been resolved.

1. 2026년 1월 22일 PM 6:56 UTCinvestigating

   We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application. Please note that data processing and alerts are not affected by this incident.

2. 2026년 1월 22일 PM 7:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 22일 PM 7:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 1월 22일 PM 7:28 UTCresolved

   This incident has been resolved.

1. 2025년 11월 18일 PM 1:18 UTCinvestigating

   We are investigating delays in RUM-based Monitors Notifications, which began at 11:30am UTC.

2. 2025년 11월 18일 PM 1:57 UTCresolved

   This incident has been resolved. Notification delays were only affecting our internal monitoring and were due to the ongoing Cloudflare incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7/.

1. 2025년 10월 23일 AM 5:50 UTCinvestigating

   We are investigating user login issues with the web application. Please note that data processing and alerts are not affected by this incident.

2. 2025년 10월 23일 AM 6:39 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 10월 23일 AM 6:51 UTCresolved

   This incident has been resolved.

1. 2025년 10월 16일 AM 11:03 UTCinvestigating

   We are actively investigating elevated error rates for Resource Catalog views As a result of this issue, some users may see errors with Resource Catalog on the web application

2. 2025년 10월 16일 AM 11:06 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 10월 16일 AM 11:14 UTCresolved

   This incident has been resolved.

1. 2025년 10월 2일 AM 5:13 UTCinvestigating

   We are investigating increased latency processing Metrics. As a result of this issue, some users may see delays or gaps for metrics on graphs. To prevent spurious alerts, we have temporarily disabled monitors based on this data.

2. 2025년 10월 2일 AM 5:49 UTCresolved

   This incident has been resolved.

1. 2025년 9월 18일 PM 3:12 UTCinvestigating

   We are investigating user login issues with the web application via Google SSO. Please note that data processing and alerts are not affected by this incident.

2. 2025년 9월 18일 PM 3:46 UTCmonitoring

   We are seeing recovery in Google SSO logins. We are continuing to monitor for issues.

3. 2025년 9월 18일 PM 4:24 UTCresolved

   This incident has been resolved.