Github is owned by Microsoft, so this is a pretty small time indie operation, you need to give them a break.
PS: None of our 40+ engineers felt anything, our self hosted Forgejo is as snappy as ever.
Or whatever else, software services going down is going to happen in some capacity, eventually. Real question is what is acceptable
I however prefer to acknowledge the nature of the business, which is there will be an inevitable untimely failure in some way you did not prepare for despite being the most well read, well practiced and researched to the problems at hand.
There were so many severe Github Actions outages (10+ ?) in the past year. Cause: Migration to the disaster zone also known as Azure, I assume. Most of them happened during (morning) CET working hours, as to not inconvenience the americans and/or make headlines.
Money doesn't buy competency. It's a long-term culture thing. You can never let go on maintaining competency in your organization. It rots if you do. I guess Microsoft did let go.
GitHub as a whole, including the previously non-Azure bits, does seem flakier than a few years ago though, for sure.