[{"id":"IL-0550","title":{"en":"Bitbucket Cloud's database slowed until connection pools saturated and requests timed out, leaving Pipelines pending","ko":"Bitbucket Cloud 의 웹사이트와 API 가 6시간 동안 느려지고 Pipelines 빌드가 밀렸다"},"org":"Atlassian","org_slug":"atlassian","date":"2024-02-22","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0550","shared_components":["database","autovacuum"]},{"id":"IL-0456","title":{"en":"Inflearn went down six times during a January 2022 free-course event as slow queries piled up on Aurora PostgreSQL","ko":"100% 할인 이벤트 기간에 인프런 서비스가 Aurora PostgreSQL 병목으로 여섯 번 멈췄다"},"org":"Inflab","org_slug":"inflab","date":"2022-01-03","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0456","shared_components":["database","autovacuum"]},{"id":"IL-0211","title":{"en":"A Mandrill PostgreSQL shard shut down at transaction ID wraparound and email sending was impaired for about 40 hours","ko":"Mandrill 의 PostgreSQL 샤드 하나가 트랜잭션 ID 랩어라운드를 막으려고 쓰기를 멈춰 약 40시간 동안 메일 발송이 줄었다"},"org":"Mailchimp","org_slug":"mailchimp","date":"2019-02-04","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0211","shared_components":["database","autovacuum"]},{"id":"IL-0450","title":{"en":"Oracle RAC commits behind order APIs kept waiting over 0.1 s on log file sync while average host CPU had headroom","ko":"주문과 체결 API 뒤의 Oracle RAC 에서 커밋이 log file sync 대기로 0.1초 넘게 밀리는 일이 반복됐다"},"org":"Toss Securities","org_slug":"toss-securities","date":"2026-10-19","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0450","shared_components":["database"]},{"id":"IL-0379","title":{"en":"InfluxDB Cloud queries in Azure West Europe slowed and timed out as storage pods fell behind and kept restarting","ko":"Azure West Europe 의 InfluxDB Cloud 에서 9월 27일부터 30일까지 쿼리가 느려지고 타임아웃됐다"},"org":"InfluxData","org_slug":"influxdata","date":"2026-09-27","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0379","shared_components":["database"]},{"id":"IL-0471","title":{"en":"GitHub Actions runs failed or sat queued for 9 hours after a routine deployment's pod replacement saturated capacity","ko":"GitHub Actions 워크플로 실행이 대량으로 실패하거나 큐에서 오래 기다렸다"},"org":"GitHub","org_slug":"github","date":"2026-08-06","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0471","shared_components":["ci-system"]},{"id":"IL-0309","title":{"en":"Preset's RDS PostgreSQL 14.7 to 17.9 upgrade in US East 1 ran out of storage and took Superset down for six hours","ko":"RDS PostgreSQL 메이저 버전 업그레이드가 점검 시간을 훨씬 넘겨 실패하면서 us2a 배포가 약 6시간 멈췄다"},"org":"Preset","org_slug":"preset","date":"2026-04-13","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0309","shared_components":["database"]},{"id":"IL-0435","title":{"en":"Error rates rose as Aurora MySQL killed connections and declined queries to avoid OOM while load metrics stayed flat","ko":"Aurora MySQL 이 OOM 을 피하려고 커넥션을 끊고 쿼리를 거부해 애플리케이션 오류율이 올랐다"},"org":"CyberAgent","org_slug":"cyberagent","date":"2026-04-02","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0435","shared_components":["database"]},{"id":"IL-0497","title":{"en":"Buttondown's database ran out of connections twice in one day and requests failed while health checks mostly passed","ko":"Postgres 가 설정된 최대 연결 수에 닿아 하루에 두 번 새 요청이 연결을 얻지 못하고 실패했다"},"org":"Buttondown","org_slug":"buttondown","date":"2026-03-31","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0497","shared_components":["database"]},{"id":"IL-0288","title":{"en":"ZooKeeperWait rose to thousands of seconds on three redundant ClickHouse instances, degrading a CDN77 data pipeline","ko":"CDN77 의 ClickHouse 데이터 파이프라인에서 이중화된 인스턴스 세 곳의 ZooKeeperWait 가 수천 초로 치솟아 복제가 한 시간 넘게 느려졌다"},"org":"CDN77","org_slug":"cdn77","date":"2026-03-09","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0288","shared_components":["database"]},{"id":"IL-0350","title":{"en":"Hosts in an IONOS TXL cluster lost connectivity when an InfiniBand fabric resweep failed on a full multicast table","ko":"TXL 클러스터 한 곳의 호스트 네트워크가 끊기고 프로비저닝 대기열이 밀려 여러 서비스가 오래 나빠졌다"},"org":"IONOS Cloud","org_slug":"ionos-cloud","date":"2026-03-03","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0350","shared_components":["database"]},{"id":"IL-0305","title":{"en":"Replicas of one Intercom Vitess shard hit 100% CPU and fell up to 2.2 hours behind, serving stale inbox data","ko":"Intercom 의 PlanetScale 샤드 하나에서 복제본이 CPU 100% 로 주 데이터베이스를 따라가지 못해 받은편지함에 최대 2.2시간 전의 데이터가 보였다"},"org":"Intercom","org_slug":"intercom","date":"2026-01-27","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0305","shared_components":["database"]},{"id":"IL-0390","title":{"en":"PostHog US Cloud event ingestion slowed to delays of up to 2 days as writes to the Persons Postgres table stalled","ko":"PostHog US Cloud 의 Persons Postgres 데이터베이스 쓰기가 크게 느려져 이벤트와 persons 수집이 최대 2일 지연됐다"},"org":"PostHog","org_slug":"posthog","date":"2025-11-11","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0390","shared_components":["database"]},{"id":"IL-0100","title":{"en":"PostHog's feature flags pods were packed onto Kubernetes nodes that were too small for their CPU requests, and CPU saturation above 90% caused three outages in ten days through Redis overload, connection pool exhaustion and slow queries","ko":"노드가 파드의 CPU 요청에 비해 작아 CPU 가 포화되면서 PostHog 기능 플래그 서비스에 열흘 사이 장애가 세 번 났다."},"org":"PostHog","org_slug":"posthog","date":"2025-10-21","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0100","shared_components":["database"]},{"id":"IL-0287","title":{"en":"One overloaded shard of MongoDB's internal monitoring database delayed Atlas metrics, alerts and cluster operations","ko":"Atlas 와 Cloud Manager 의 모니터링을 받치는 내부 데이터베이스 클러스터의 샤드 하나가 과부하되어 지표 수집과 클러스터 작업이 늦어졌다"},"org":"MongoDB","org_slug":"mongodb","date":"2025-10-07","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0287","shared_components":["database"]},{"id":"IL-0557","title":{"en":"Database transaction locks piled up on Storj's US1 satellite, and uploads and downloads failed with timeouts for 2 hours","ko":"같은 객체에 몰린 동시 업로드가 데이터베이스 트랜잭션 경합을 일으켜 Storj US1 satellite 의 업로드와 다운로드 요청이 실패했다"},"org":"Storj","org_slug":"storj","date":"2025-08-07","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0557","shared_components":["database"]},{"id":"IL-0551","title":{"en":"Bitbucket Cloud's overloaded primary database failed over, and the website, API and Pipelines were slow for almost a day","ko":"Bitbucket Cloud 주 데이터베이스가 과부하로 장애 조치된 뒤 하루 가까이 지연과 간헐 오류가 이어졌다"},"org":"Atlassian","org_slug":"atlassian","date":"2025-05-08","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0551","shared_components":["database"]},{"id":"IL-0298","title":{"en":"Wikimedia edits failed for 38 minutes when sessionstore Cassandra nodes in both data centres crashed on full disks","ko":"Wikimedia sessionstore 의 Cassandra 노드가 디스크가 가득 차 잇따라 죽고 쿼럼을 잃어 편집이 실패했다"},"org":"Wikimedia Foundation","org_slug":"wikimedia-foundation","date":"2025-03-31","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0298","shared_components":["database"]},{"id":"IL-0312","title":{"en":"Gadget's main Postgres did not start again after a restart to raise max_connections, and the platform went down","ko":"max_connections 를 올리려고 재시작한 주 PostgreSQL 데이터베이스가 다시 올라오지 않아 Gadget 의 모든 앱 요청이 멈췄다"},"org":"Gadget","org_slug":"gadget","date":"2024-12-13","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0312","shared_components":["database"]},{"id":"IL-0544","title":{"en":"Wasabi's database cache stopped responding when its queueing service filled up, and S3 failed in all regions","ko":"Wasabi 전 리전의 S3 와 사용자 서비스에 이틀에 걸쳐 세 차례 장애가 났다"},"org":"Wasabi","org_slug":"wasabi","date":"2024-08-06","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0544","shared_components":["database"]},{"id":"IL-0447","title":{"en":"An every RDS for MySQL instance slowed badly when its gp2 EBS BurstBalance ran out and IOPS fell to the baseline","ko":"RDS MySQL 인스턴스의 EBS BurstBalance 가 바닥나 IOPS 가 기준 성능으로 묶이고 데이터베이스 성능이 크게 떨어졌다"},"org":"every","org_slug":"every","date":"2024-06-24","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0447","shared_components":["database"]},{"id":"IL-0375","title":{"en":"MongoDB Atlas cluster changes and alerts lagged for hours after a control plane metadata migration congested a database","ko":"MongoDB Atlas 컨트롤 플레인이 느려져 모든 상용 리전에서 클러스터 변경과 알림이 몇 시간씩 늦었다"},"org":"MongoDB","org_slug":"mongodb","date":"2024-06-03","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0375","shared_components":["database"]},{"id":"IL-0110","title":{"en":"A Grafana Agent pod's high memory use and crash-looping Hangfire pods drove a Kubernetes node into system OOM and NotReady, twice in one day","ko":"Grafana Agent 파드가 메모리를 많이 쓰던 노드에 Hangfire 파드가 함께 올라가 시스템 OOM 으로 CrashLoopBackOff 를 반복했고, 노드가 응답을 멈추고 NotReady 가 됐다."},"org":"DFDS","org_slug":"dfds","date":"2024-03-13","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0110","shared_components":["database"]},{"id":"IL-0270","title":{"en":"Discord's ScyllaDB authentication cluster overloaded during an OS upgrade, and logins failed for about 50 minutes","ko":"인증용 ScyllaDB 클러스터가 과부하로 조회를 처리하지 못해 Discord 에서 약 50분 동안 접속과 로그인이 되지 않았다"},"org":"Discord","org_slug":"discord","date":"2023-11-06","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0270","shared_components":["database"]},{"id":"IL-0202","title":{"en":"A burst of queries and database writes exhausted connection pools and memory on Honeycomb's ingest hosts, and Kubernetes crash-loop back-off kept failed hosts offline so ingest capacity stayed too low to recover","ko":"갑자기 몰린 쿼리와 데이터베이스 쓰기로 Honeycomb 수집 호스트가 메모리 부족으로 죽었고, 쿠버네티스 CrashLoopBackOff 가 용량 회복을 막아 US1 이벤트 수집이 한 시간 넘게 불안정했다"},"org":"Honeycomb","org_slug":"honeycomb","date":"2023-11-05","severity":"sev1","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0202","shared_components":["database"]},{"id":"IL-0386","title":{"en":"After a move to Google Cloud, Postgres connection timeouts and memcached i/o timeouts spiked on GKE nodes","ko":"Google Cloud 로 옮긴 뒤 GKE 노드에서 Postgres 연결 타임아웃과 memcached i/o timeout 이 간헐적으로 튀었다"},"org":"incident.io","org_slug":"incident-io","date":"2023-09-26","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0386","shared_components":["database"]},{"id":"IL-0326","title":{"en":"A retention clean-up job filled the disk of MailPace's managed Postgres, which stayed offline for just over two hours","ko":"MailPace 의 관리형 Postgres 데이터베이스 디스크가 가득 차 데이터베이스가 두 시간 넘게 내려갔다"},"org":"MailPace","org_slug":"mailpace","date":"2023-08-11","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0326","shared_components":["database"]},{"id":"IL-0546","title":{"en":"Buildkite jobs could not go to newly connected agents once agent IDs passed a 32-bit integer foreign key's limit","ko":"Buildkite 에 새로 연결한 에이전트가 잡을 받지 못했다"},"org":"Buildkite","org_slug":"buildkite","date":"2023-07-22","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0546","shared_components":["database"]},{"id":"IL-0500","title":{"en":"UToronto JupyterHub logins and server starts returned 500 errors when the hub's sqlite database disk filled up","ko":"UToronto JupyterHub 의 데이터베이스 디스크가 가득 차서 로그인과 서버 시작이 500 오류로 실패했다"},"org":"2i2c","org_slug":"2i2c","date":"2022-10-31","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0500","shared_components":["database"]},{"id":"IL-0301","title":{"en":"Basecamp 3's primary database went into total gridlock at the top of the hour and Basecamp 3 went down twice","ko":"Basecamp 3 의 주 데이터베이스가 정시 부하에 락 경합으로 30초 만에 완전히 막혔다"},"org":"37signals","org_slug":"37signals","date":"2022-06-27","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0301","shared_components":["database"]},{"id":"IL-0206","title":{"en":"Consul agents in GitLab.com's GKE pods were repeatedly OOM-killed, so the Rails pods lost database replica discovery and sent every query to the primary","ko":"GKE 파드 안의 Consul 에이전트가 메모리 급증으로 거듭 OOM kill 되어 Rails 파드가 데이터베이스 복제본을 찾지 못했고, 모든 쿼리가 primary 로 몰려 GitLab.com 이 느려졌다."},"org":"GitLab","org_slug":"gitlab","date":"2022-04-25","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0206","shared_components":["database"]},{"id":"IL-0302","title":{"en":"Peak load on GitHub's mysql1 MySQL cluster maxed out its database proxy's connections and stopped writes in March 2022","ko":"GitHub 의 공용 MySQL 클러스터 mysql1 이 최대 부하 시간대에 연결이 바닥나 쓰기 작업이 네 번 멈췄다"},"org":"GitHub","org_slug":"github","date":"2022-03-16","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0302","shared_components":["database"]},{"id":"IL-0212","title":{"en":"Many Slack users could not connect because a Vitess keyspace for channel membership was overloaded by cache-miss queries","ko":"캐시 적중률이 떨어지며 채널 멤버십 Vitess 키스페이스가 과부하에 빠져 많은 사용자가 Slack 에 접속하지 못했다"},"org":"Slack","org_slug":"slack","date":"2022-02-22","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0212","shared_components":["database"]},{"id":"IL-0321","title":{"en":"GCP snapshots on all Patroni nodes stalled GitLab.com's primary PostgreSQL disk, Patroni failed over and 5xx spiked","ko":"GitLab.com 의 Patroni 주 데이터베이스 노드가 멈춰 장애 조치가 일어났고 쓰기 요청에서 5xx 오류가 튀었다"},"org":"GitLab","org_slug":"gitlab","date":"2021-01-16","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0321","shared_components":["database"]},{"id":"IL-0496","title":{"en":"Ably's Cassandra hit 100% CPU in every region and queries timed out globally, and the load returned on two more evenings","ko":"전역 복제 Cassandra 클러스터에서 모든 리전의 인스턴스 CPU 가 100% 로 치솟아 쿼리가 타임아웃됐고, 같은 부하가 이틀 저녁 더 찾아왔다"},"org":"Ably","org_slug":"ably","date":"2020-06-11","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0496","shared_components":["database"]},{"id":"IL-0443","title":{"en":"A Repro Aurora MySQL reader restarted unexpectedly and writer insert latency rose about sevenfold for a day or more","ko":"Aurora MySQL reader 가 이유 없이 재시작한 뒤 writer 의 insert latency 가 7배쯤 오르고 replication lag 가 하루 넘게 이어졌다"},"org":"Repro","org_slug":"repro","date":"2019-11-11","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0443","shared_components":["database"]},{"id":"IL-0002","title":{"en":"CI builder pods could not get AWS IAM credentials because kubelet fell minutes behind its API rate limit","ko":"빌더 파드가 노드 한 대에 몰리자 kubelet 이 기본 API QPS 한도에 막혀 파드 상태를 늦게 갱신했고, CI 빌드가 AWS IAM 자격 증명을 받지 못해 실패했다"},"org":"Zalando","org_slug":"zalando","date":"2019-06-11","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0002","shared_components":["ci-system"]},{"id":"IL-0401","title":{"en":"Prow jobs on the k8s-prow-build GKE cluster failed and merges stalled as nodes hit IOPS throttling and kernel panics","ko":"Kubernetes 프로젝트의 Prow 빌드 클러스터 노드가 GCP 디스크 IOPS 스로틀링에 걸려 테스트가 이상하게 실패하고 PR 머지가 몇 시간 멈췄다"},"org":"Kubernetes project","org_slug":"kubernetes-project","date":"2019-05-30","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0401","shared_components":["ci-system"]},{"id":"IL-0037","title":{"en":"Image registry rate-limited a whole region after a crash-looping DaemonSet with imagePullPolicy Always pulled through three NAT instances","ko":"imagePullPolicy가 Always인 DaemonSet이 크래시 루프를 돌며 이미지를 계속 받아, NAT 세 대를 같이 쓰던 리전 전체가 이미지 레지스트리에서 429로 막혔다"},"org":"Datadog","org_slug":"datadog","date":"2019-05-23","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0037","shared_components":["database"]},{"id":"IL-0297","title":{"en":"Mezmo users could not sign in and log indexing lagged after the auth cache's Redis servers were OOM killed","ko":"Mezmo 의 인증 캐시 Redis 서버가 OOM 으로 죽고 다시 뜨지 못해 로그인이 막히고 로그 색인이 늦어졌다"},"org":"Mezmo","org_slug":"mezmo","date":"2019-05-15","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0297","shared_components":["database"]},{"id":"IL-0064","title":{"en":"CPU-heavy pods packed onto one Google Cloud node drove it to kernel panics, and the crash moved from node to node until the site was down","ko":"CPU 를 많이 쓰는 파드가 Google Cloud 노드 하나에 몰려 노드가 커널 패닉으로 죽었고, 다시 배치된 파드가 다음 노드를 또 죽이며 웹사이트와 API 가 멈췄다."},"org":"Moonlight","org_slug":"moonlight","date":"2019-01-18","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0064","shared_components":["database"]},{"id":"IL-0300","title":{"en":"Basecamp 3 went read-only for almost five hours when its events table reached the ceiling of 2,147,483,647","ko":"Basecamp 3 의 events 테이블이 데이터베이스 한도에 닿아 서비스가 다섯 시간 가까이 읽기 전용이 되었다"},"org":"37signals","org_slug":"37signals","date":"2018-11-09","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0300","shared_components":["database"]},{"id":"IL-0334","title":{"en":"Instapaper's RDS MySQL bookmarks table hit the 2TB ext3 file size limit, inserts failed and the service went down","ko":"RDS MySQL 의 bookmarks 테이블이 2TB 파일 크기 한도에 닿아 INSERT 가 실패하고 Instapaper 가 31시간 동안 멈췄다"},"org":"Instapaper","org_slug":"instapaper","date":"2017-02-09","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0334","shared_components":["database"]},{"id":"IL-0333","title":{"en":"A downsized RDS PostgreSQL database maxed out its CPU at US peak and failing ELB health checks took buildkite.com down","ko":"사양을 낮춘 RDS PostgreSQL 인스턴스가 피크 부하를 못 버텨 헬스 체크가 실패하고 Buildkite 대시보드가 몇 시간 동안 내려갔다"},"org":"Buildkite","org_slug":"buildkite","date":"2016-08-22","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0333","shared_components":["database"]},{"id":"IL-0282","title":{"en":"DynamoDB in US-East reached about 55% request errors as storage servers overloaded its metadata service","ko":"US-East 리전의 DynamoDB 스토리지 서버들이 멤버십 정보를 받지 못해 스스로 요청 처리에서 빠지면서 고객 요청의 약 55% 가 실패했다"},"org":"Amazon Web Services","org_slug":"amazon-web-services","date":"2015-09-20","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0282","shared_components":["database"]},{"id":"IL-0383","title":{"en":"PagerDuty's shared Cassandra cluster degraded during a repair, delaying notifications and losing incoming events","ko":"PagerDuty 알림 파이프라인이 이틀 연속 장애를 겪어 이벤트를 받지 못하고 알림이 늦거나 가지 않았다"},"org":"PagerDuty","org_slug":"pagerduty","date":"2014-06-03","severity":"sev1","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0383","shared_components":["database"]},{"id":"IL-0320","title":{"en":"Postmark's primary MySQL disk filled but MySQL kept running, so MySQL-MMM never failed over and sending was delayed","ko":"주 MySQL 서버의 디스크가 가득 차 메일 발송, API, 웹 화면이 지연됐다"},"org":"Postmark","org_slug":"postmark","date":"2011-10-20","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0320","shared_components":["database"]}]