I assume these companies have some kind of uptime guarantee in their contracts, because they seems to care more about covering their asses than about informing customers.
We have outages on our books that they never reported even after we ticketed them.
They cook the stats like an inner city police department.
Github's status page is incredibly slow in comparison to the status page Github themselves used to have, which had several key metrics of various systems that would update in real time, and when they did have a (comparatively rare) outage, would usually have at least one metric going "yeah, something is wrong".
Don't know about you but at this point I've learned to recognize and ignore GitHub issues even when they haven't admitted to it yet
Question 1: Is it github, or is it everyone:
Answer: https://downdetector.com/
(If everyone's having issues, then stop. Otherwise, continue below...)
---
Question 2: Is it github?
Answer 2: https://www.githubstatus.com/
Question 3: Why are you lying to me, is it github or not?
Answer 3: https://mrshu.github.io/github-statuses/
(If github is not having issues, then check your local environment. Otherwise, continue...)
---
Question 4: Why is it always github, surely they're not that bad right?
Answer: https://www.dayswithoutgithubincident.com/
(Perhaps its time to consider an alternative to github, or at least a mirror)
A sick person with symptoms is clearly sick, but sometimes they're asymptomatic. That's what the GitHub status page has become. When it's red and showing problems, you know you have problems. When it's all green? You know you MIGHT have problems.
That can make outages like this harder to triage, since reality is a black box.