It feels so wrong that there are so many blogs and websites that are based on GH Pages and they all died at once…
Seems like they’re back up though. Or at least the Rust blog is back up.
GitHub was down
191–200 of 288 posts
Re: GitHub was down
#192Maybe it's fixed already? Works for me.
Re: GitHub was down
#193I sure wish this had happened before I logged off from work for the day...
"Why isn't this project done yet?"
"Didn't you hear? GitHub is down!"
and I get to go out for a long lunch
Re: GitHub was down
#194Earlier quoted context omitted.
I think this is because logged-out Twitter now shows top Tweets of all time from a user, rather than most recent Tweets. Good reason why companies shouldn't be using Twitter/X for status updates anymore!
Thank you! I was wondering why all I could see was useless content there!
Re: GitHub was down
#195Earlier quoted context omitted.
I have to wonder how a company at the scale of GitHub can be so bad at keeping track of their status. Now 4 out of 10 services are marked as "Incident", yet most of the others are also completely dead.
It's because of the way most companies build their status dashboards. There are usually at least 2 dashboards, one internal dashboard and one external dashboard. The internal dashboard is the actual monitoring dashboard, where it will be hooked up with other monitoring data sources. The external status dashboard is just for customer communication. Only after the outage/degradation is confirmed internally, then the ex…
> The external status dashboard is just for customer communication. Only after the outage/degradation is confirmed internally, then the external dashboard will be updated to avoid flaky monitors and alerts. It will also affect SLAs so it needs multiple levels of approval to change the status, that's why there are some delays.
This defeats the purpose of a status dashboard and is effectively useless in practice most of the time from a consumers point of view.
Re: GitHub was down
#196Back online for me
Re: GitHub was down
#197for everyone complaining about the status page - status pages are normally operated by hand by design, and will rarely reflect things in real-time. give the poor github ops folks a second to get things moving.
Most status page products integrate to monitoring tools like Datadog[1], large teams like github would have it automated. You ideally do not want to be making a decision on whether to update a status page or not during the first few minutes of an incident, bean counters inevitably tend to get involved to delay/not declare downtime if there is a manual process. It is more likely the threshold is kept a bit higher than…
Nah, _most_ status pages are hand updated to avoid false positives, and to avoid alerting customers when they otherwise would not have noticed. Very, very few organizations go out of their way to _tell_ customers they failed to meet their SLA proactively. GitHub's SLA remedy clause even stipulates that the customer is responsible for tracking availability, which GitHub will then work to confirm.
Re: GitHub was down
#198A reminder of how centralized and dependent the whole industry has become on GH, which is ironic, considering that git itself is designed to be decentralized. Good opportunity to think about mirroring your repos somewhere else like Gitea or Gitlab.
It's not the whole industry, just some imprudent sections of the industry.
Re: GitHub was down
#199[flagged]
Re: GitHub was down
#200A reminder of how centralized and dependent the whole industry has become on GH, which is ironic, considering that git itself is designed to be decentralized. Good opportunity to think about mirroring your repos somewhere else like Gitea or Gitlab.
these things could happen anywhere though. Gitlab also `rm -rf`ed before remember
The odds of all services rm -rf / at the same time are pretty small to be honest. The point is to have your work in multiple places, such that you're not reliant on a single service.