TGViewer
CatOps CatOps @catops · 5.09K subscribers
Post #2963 1.26K
A postmortem for the recent GitHub incident. Regarding the cause:

The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery. 


#postmortem #github
Githubstatus Incident with GitHub.com GitHub's Status Page - Incident with GitHub.com.
  • 👍 12
More from @catops
  1. Sep 28, 2026​​For today’s Donations Monday, I’d like to remind you about a fundraiser for a pickup tru…
  2. Sep 26, 2026Here’s Datadog’s take on the increased load on CI. In this article they explain how their…
  3. Sep 25, 2026A new chapter of the CatOps Digest is here! https://newsletter.catops.dev/p/catops-digest-…
  4. Sep 24, 2026Shopify wrote an article on them moving from React Native to the native code for their mob…
  5. Sep 23, 2026A bunch of practice exams on Humble Bundle, if you're into this type of thing. This offer…
  6. Sep 21, 2026​​A good friend of the channel raises funds for his new unit (a small air defense unit). T…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →