[{"id":"IL-0310","title":{"en":"An Aurora PostgreSQL failover to an upsized reader reversed twice and backend writes failed in read-only transactions","ko":"Aurora PostgreSQL 의 수동 장애 조치가 스스로 되돌아가 원래 writer 가 남고 백엔드의 쓰기 쿼리가 실패했다"},"org":"Hightouch","org_slug":"hightouch","date":"2025-10-23","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0310","shared_components":["failover-manager"]},{"id":"IL-0376","title":{"en":"A maintenance update set off needless full syncs between Upstash Redis replicas in eu-west-1, slowing the databases","ko":"AWS eu-west-1 의 Upstash 리전 Redis 데이터베이스가 CPU 부하로 몇 시간 동안 느려졌다"},"org":"Upstash","org_slug":"upstash","date":"2025-02-25","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0376","shared_components":["cache"]},{"id":"IL-0216","title":{"en":"Wikimedia on-wiki search was slow or rejected after a datacenter switchover overloaded one Elasticsearch node in codfw","ko":"데이터센터 전환 직후 CirrusSearch Elasticsearch 지연이 치솟아 위키 검색이 일부 사용자에게 늦거나 안 됐다"},"org":"Wikimedia Foundation","org_slug":"wikimedia-foundation","date":"2023-09-20","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0216","shared_components":["cache"]},{"id":"IL-0217","title":{"en":"Honeycomb's main MySQL database locked up under cache-miss reads and ran out of connections, a 68-minute total outage","ko":"스키마 캐시가 데워지지 않아 주 MySQL 데이터베이스가 내부 교착에 빠지고 Honeycomb 전체가 68분 동안 멈췄다"},"org":"Honeycomb","org_slug":"honeycomb","date":"2023-07-25","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0217","shared_components":["cache"]},{"id":"IL-0213","title":{"en":"Roblox was down for 73 hours because key-value writes on its single Consul cluster slowed from under 300 ms to 2 seconds","ko":"Consul 클러스터의 KV 쓰기가 느려지고 리더가 뒤처지며 Roblox 전체가 73시간 동안 멈췄다"},"org":"Roblox","org_slug":"roblox","date":"2021-10-28","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0213","shared_components":["cache"]},{"id":"IL-0241","title":{"en":"A database shard could not elect a new primary, and the Stripe API failed most requests in two periods on one day","ko":"데이터베이스 shard 하나가 primary 를 뽑지 못해 Stripe API 요청 대부분이 두 차례 실패했다"},"org":"Stripe","org_slug":"stripe","date":"2019-07-10","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0241","shared_components":["failover-manager"]},{"id":"IL-0279","title":{"en":"One failed Redis Cluster replica left only about 1 in 21 calls to Grab's Apollo service succeeding for a minute","ko":"Redis Cluster 의 슬레이브 노드 하나가 죽자 파이프라인 읽기가 실패해 Grab 의 운송 예약 서비스 Apollo 호출이 1분 동안 21번에 1번꼴로만 성공했다"},"org":"Grab","org_slug":"grab","date":"2019-02-15","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0279","shared_components":["cache"]},{"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":["cache"]},{"id":"IL-0303","title":{"en":"GitHub's MySQL master failed over to a node with a cold buffer pool during a schema migration and GitHub.com went down","ko":"GitHub 의 새 3노드 MySQL 클러스터에서 자동 페일오버가 잘못 일어나고 클러스터 상태가 갈라져 GitHub.com 이 두 번 멈췄다"},"org":"GitHub","org_slug":"github","date":"2012-09-10","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0303","shared_components":["failover-manager"]}]