Good luck to the engineers at GitHub as I know how stressful it can be, but hope everyone else is enjoying a nice break and some socializing
edit: Nevermind, they just reported "degraded performance" for GitHub Actions, Issues, and Pull Requests.
By the way, I don't know of a single place where this isn't the case, where a human signs off on and updates the status page during large events (at least at the final decision.) Some of it will be automated, sure, like red flags being raised to operators. But at a certain point it is not possible to automate this in some level to achieve second-level accuracy or whatever; the system is rarely (if ever) in a binary state of "working perfectly" or "not working", but somewhere in between. You can't just fire off a big red error bar every time a blip occurs at a place like GitHub. The system is constantly "in motion". The logical conclusion is to just expose your 50+ Grafana dashboards publicly to every user. Isn't that the most honest "overview" of what is happening with your product? Except this often can't tell them useful things either.
People on here will also mumble about SLAs but if a customer wants a kickback or is seriously worried about events like these, they're generally talking to account managers, not posting on internet forums. That said, a lot of them get weaselly about that stuff unless you're already negotiating prices with an AM in the first place...
> We are investigating reports of degraded performance for GitHub Actions, Issues, and Pull Requests.
Their freaky homepage is borked: https://github.com/ yields a 500 error haha.
EDIT: it's updated now.
EDIT EDIT: github.com is back up and running, apologies for the disruption :(
Source: GitHub employee
Is it time to use a self-hosted backup like what GNOME is using? [1]
Edit: it's back.