What I find problematic, especially for teams that rely on GitOps and GitHub being (relatively) stable, is the fact that GitHub's status page can't be relied on. You arrive at the conclusion, "this must be GitHub," but the status page rejects the notion, and so you go digging. That can lead to a lot of toil and wasted time, in addition to sideways looks paired with comments like, "but status shows green."
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.
Extremely high level, and mainly merely "is the site accessible". However, github having issues with "issues" or "pull requests" is a functionality, not an accessibility, degradation, which can often only be discovered by actually trying to perform the action/use the functionality and comparing the result to he expected result.
Github is fast in updating their status compared to other companies. Amazon has to be bombed, on fire, and in the news before their status page shows anything about any ongoing issues.
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.
Me and a colleague were just ranting about how there's no way in hell Actions has 99.6% uptime but yet that's what their status page says. Maybe it's just bias and I am only remembering the minutes that it's down what feels like every week or multiple times a week. But I'm suspicious of their stats, even if they declare an incident on the status page.
I would suggest every enterprise customer that is not keeping track of github downtime and it's effect on their systems and workforce independently for presentation to their sales team every billing cycle for discounts is leaving a lot of money on the table.
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".
Gotcha, that's what I figured but I was still curious. I've got a side-project that was originally designed for traditional GitOps but got OCI support as a feature submission from a user. I've been seeing more usage of the OCI backend these days and originally figured it was a side-effect of the project domain (Podman Quadlets) but maybe it is an over all field shift.
In the last couple of weeks, I've been moving a deployment stack off ArgoCD pointing at Git, and ended up settling on Flux fetching OCI artifacts from ECR. The artifacts are built and pushed by GitHub Actions. It seems like a nice way to "have GitOps" without needing GitHub to be up all the time.
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.