Incident Library?

API · MCP 한국어

Incident Library?

API · MCP 한국어

Component ?

Authoritative DNS servers and records

DNS 서버와 레코드 · dns-server

2 cases · 2025

Root cause ?Dependency failure 1 Software defect 1

Contributing factor ?Automation amplification 1 No runbook 1 Retry storm 1

Symptom ?DNS resolution failures 2 Scale-up failure 1 Control plane unresponsive 1 High error rate 1 High latency 1 Intermittent connection failures 1

Cases, by severity

IL-0150 A latent race condition in DynamoDB's DNS automation left an empty DNS record for dynamodb.us-east-1.amazonaws.com, and the DynamoDB and EC2 launch failures that followed caused EKS, ECS and Fargate container launch failures and cluster scaling delays in us-east-1Amazon Web Services · 2025
Root cause Software defect
IL-0162 LKE users could not reach their cluster control planes or the LKE Dashboard because an earlier database update made the internal LKE DNS service hangLinode · 2025
Root cause Dependency failure

View on the graph