[{"id":"IL-0150","title":{"en":"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-1","ko":"DynamoDB DNS 자동화의 경쟁 조건이 us-east-1 리전 엔드포인트의 DNS 레코드를 비워 DynamoDB 와 EC2 인스턴스 시작이 실패했고, 그 여파로 EKS, ECS, Fargate 의 컨테이너 시작과 클러스터 스케일링이 14시간 넘게 막혔다"},"org":"Amazon Web Services","org_slug":"amazon-web-services","date":"2025-10-19","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0150","shared_components":["dns-server"]},{"id":"IL-0250","title":{"en":"slack.com stopped resolving on some DNSSEC-validating resolvers for about 24 hours after DNSSEC signing was turned on","ko":"slack.com 에 DNSSEC 를 켠 뒤 일부 재귀 리졸버에서 slack.com 이름이 풀리지 않아 일부 사용자가 24시간 동안 Slack 에 접속하지 못했다"},"org":"Slack","org_slug":"slack","date":"2021-09-30","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0250","shared_components":["dns-server"]},{"id":"IL-0359","title":{"en":"Queries to Gandi LiveDNS timed out when two crashed anycast DNS nodes kept announcing all three name server addresses","ko":"Gandi LiveDNS 노드 두 대가 멈춰 그 노드로 간 DNS 질의가 타임아웃됐다"},"org":"Gandi","org_slug":"gandi","date":"2020-07-16","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0359","shared_components":["dns-server"]},{"id":"IL-0338","title":{"en":"Google Cloud HTTP(S) and TCP/SSL Proxy load balancers returned 502s or reset connections on 33% to 87% of requests","ko":"Google Cloud 의 HTTP(S) 로드 밸런서와 TCP/SSL Proxy 로드 밸런서가 32분 동안 요청의 33~87% 에 502 나 연결 재설정을 냈다"},"org":"Google Cloud","org_slug":"google-cloud","date":"2018-07-17","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0338","shared_components":["cdn"]},{"id":"IL-0388","title":{"en":"A Google Cloud live migration took a Discord Redis primary offline, and the failover broke API instances and then guilds","ko":"Redis 고가용 클러스터의 primary 노드가 내려간 뒤 Discord API 가 느려지고 길드 일부가 오프라인으로 보이며 접속이 실패했다"},"org":"Discord","org_slug":"discord","date":"2017-10-13","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0388","shared_components":["cdn"]}]