[{"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":["cloud-load-balancer"]},{"id":"IL-0352","title":{"en":"Heroku Router 2.0 spread HTTP requests unevenly across dynos for four days, causing latency and timeouts","ko":"Router 2.0 을 쓰는 앱에서 HTTP 요청이 web dyno 에 고르지 않게 나뉘어 지연과 타임아웃이 늘었다"},"org":"Heroku","org_slug":"heroku","date":"2025-07-18","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0352","shared_components":["cloud-load-balancer"]},{"id":"IL-0131","title":{"en":"A new kind of GenerateContent request made Vertex AI prediction API servers segfault, and once enough of them restarted at the same time the serving fleet could not carry the load","ko":"새로운 형태의 GenerateContent 요청이 Vertex AI 예측 API 서버에 세그폴트를 일으켰고, 동시에 재시작하는 서버가 늘자 서빙 용량이 모자라 여러 리전에서 오류가 치솟았다."},"org":"Google Cloud","org_slug":"google-cloud","date":"2024-06-12","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0131","shared_components":["cloud-load-balancer"]},{"id":"IL-0529","title":{"en":"New Google Cloud VMs and other instances came up without network connectivity in all zones after VPC controllers stopped","ko":"모든 Google Cloud 존에서 VPC 컨트롤러가 꺼져 새로 만든 VM 과 여러 제품의 새 인스턴스가 네트워크 없이 올라왔다"},"org":"Google Cloud","org_slug":"google-cloud","date":"2024-05-16","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0529","shared_components":["cloud-load-balancer"]},{"id":"IL-0243","title":{"en":"Google's global External Proxy Load Balancing returned 404 errors for most HTTP/S endpoints for 33 minutes","ko":"Google External Proxy Load Balancing 뒤의 HTTP/S 엔드포인트가 전 세계에서 Google 404 오류를 냈다"},"org":"Google Cloud","org_slug":"google-cloud","date":"2021-11-16","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0243","shared_components":["cloud-load-balancer"]},{"id":"IL-0106","title":{"en":"A malformed Traefik IngressRoute triggered a Traefik v2 bug once a node rollover restarted every Traefik pod, and all Kubernetes services returned 404","ko":"잘못된 IngressRoute 매니페스트가 Traefik v2 버그를 건드려 Traefik 파드가 모두 재시작된 뒤 Kubernetes 의 모든 서비스가 404 를 냈다"},"org":"DFDS","org_slug":"dfds","date":"2021-09-06","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0106","shared_components":["cloud-load-balancer"]},{"id":"IL-0493","title":{"en":"Netlify's Google Cloud TCP load balancer stopped serving about 5% of global traffic as all backends failed health checks","ko":"Google Cloud TCP 로드 밸런서의 백엔드 노드가 상태 검사에 모두 실패해 Netlify 전체 트래픽의 약 5%가 처리되지 않았다"},"org":"Netlify","org_slug":"netlify","date":"2021-03-25","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0493","shared_components":["cloud-load-balancer"]},{"id":"IL-0345","title":{"en":"Many Render services in the Oregon region returned 503 errors for about four hours","ko":"Render Oregon 리전의 많은 서비스가 4시간 동안 503 오류를 평소보다 많이 냈다"},"org":"Render","org_slug":"render","date":"2020-12-06","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0345","shared_components":["cloud-load-balancer"]},{"id":"IL-0030","title":{"en":"Most nodes of a cluster went NotReady together for 15 minutes while the API server sat behind an AWS ELB","ko":"쿠버네티스 v1.7.4 클러스터에서 노드들이 한꺼번에 NotReady 가 되어 쓸 수 있는 노드가 20% 미만으로 줄었다."},"org":"Zalando","org_slug":"zalando","date":"2019-02-11","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0030","shared_components":["cloud-load-balancer"]},{"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":["cloud-load-balancer"]},{"id":"IL-0395","title":{"en":"Google Cloud HTTP(S) Load Balancer gave 502s on 25% of requests for 22 minutes after reverting to a stale configuration","ko":"Google Cloud HTTP(S) Load Balancer 가 한참 오래된 구성으로 되돌아가 요청의 25%가 22분 동안 502 오류로 실패했다"},"org":"Google Cloud","org_slug":"google-cloud","date":"2017-04-05","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0395","shared_components":["cloud-load-balancer"]},{"id":"IL-0396","title":{"en":"New or live-migrated GCE instances, VPN tunnels and network load balancers were unreachable on public IPs for over 2h","ko":"새로 만들거나 라이브 마이그레이션한 GCE 인스턴스, Cloud VPN 터널, 네트워크 로드 밸런서가 2시간 8분 동안 공인 IP 주소로 연결되지 않았다"},"org":"Google Cloud","org_slug":"google-cloud","date":"2017-01-30","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0396","shared_components":["cloud-load-balancer"]}]