Oh you're right, I misread. They're actually blaming their customer's vibe coding on their problems. I which case I call BS

In our internal metrics you can see a clear increase in PRs and CI runs in general that tracks with agentic coding adoption, and it's significant, so I absolutely buy that GitHub would be struggling to take the brunt of that without big changes

But GitHub's postmortems are usually related to internal rollouts rather than traffic load

A charitable view might be that changing which fingers you're using to plug the holes in the dike is a lot harder when the volume of water on the other side is increasing exponentially.