Episode Synopsis "GitHub’s 43 Second Network Partition"
In 2018, after 43 seconds of connectivity issues between their East and West coast datacenters and a rapid promotion of a new primary, GitHub ended up with unique data written to two different databases. As detailed in the postmortem, this resulted in 24 hours of degraded service. This episode spends a lot of time on […]
Listen "GitHub’s 43 Second Network Partition"
More episodes of the podcast The Downtime Project
- 7 Lessons From 10 Outages
- Salesforce Publishes a Controversial Postmortem (and breaks their DNS)
- Kinesis Hits the Thread Limit
- How Coinbase Unleashed a Thundering Herd
- Auth0’s Seriously Congested Database
- Talkin’ Testing with Sujay Jayakar
- GitHub’s 43 Second Network Partition
- Auth0 Silently Loses Some Indexes
- One Subtle Regex Takes Down Cloudflare
- Monzo’s 2019 Cassandra Outage
- Gitlab’s 2017 Postgres Outage
- Slack vs TGWs
- Introduction