Earlier quoted context omitted.
Yep, they just need to improve their reliability by 2%! https://mrshu.github.io/github-statuses/
This page tells a very different story from GitHub own status page. What is different here?
Incident with Actions and Pages
191–200 of 407 posts
Re: Incident with Actions and Pages
#192Earlier quoted context omitted.
More likely that 'update the Status site' lives a long way down their incident response plan, and they have alarms going off well before that
yeah I mean a company the size of GitHub certainly can’t be expected to have enough staff to walk and chew gum at the same time
Re: Incident with Actions and Pages
#193I switched to GitLab a while ago and then spun it up locally. Something’s wrong when my own infrastructure is more reliable than Microsoft’s.
Re: Incident with Actions and Pages
#194Earlier quoted context omitted.
Same. It's weird how I always find out that GitHub is down before GitHub does. Took 15 minutes before it appeared on githubstatus.com
More likely that 'update the Status site' lives a long way down their incident response plan, and they have alarms going off well before that
Re: Incident with Actions and Pages
#195Insane, we have to come up with contingency plans now for long-duration GitHub outages because we can't safely do deployments. For a service we're paying thousands of $ per year for even though we host runners ourselves...
You can now hire me as an overpriced consultant instead of paying Microsoft.
Re: Incident with Actions and Pages
#196Earlier quoted context omitted.
All these monitoring rules are of the format "when 500 errors > baseline for x minutes". Otherwise you'd have monitoring alerts every second. So it is normal for users to already see errors before github officially counts it as an outage.
In a high performance service with good maintenance and upkeep, you page for all 500s. A noisy pager forces the team to fix the 500s. Maybe the Github Actions infrastructure isn't run like that. edit: my oncall rotation notified on all 500s, 24/7, not just rates - https://news.ycombinator.com/item?id=48279262
Re: Incident with Actions and Pages
#197Re: Incident with Actions and Pages
#198Earlier quoted context omitted.
Depending on how many thousands of $ per year, it would probably be cheaper and more reliable to self-host GitLab. It's better in terms of organisational structure (you can have one, including access and secret inheritance), and (personal view) Gitlab-CI is better than GitHub Actions because it doesn't push you towards a JavaScript/NPM style dependency hell. And it's actually fairly easy to self-hosted, with options…
Sounds good until you see their cvedetails page
Re: Incident with Actions and Pages
#199free service is down again, let's everyone that use the service for free complain again!!! (sorry for the sarcastic comment but i find it crazy how people feel they are entitled when it's free) EDIT: sorry i meant this rant at the one complaining for the free service not for the paid customers (which is unacceptable)
Re: Incident with Actions and Pages
#200free service is down again, let's everyone that use the service for free complain again!!! (sorry for the sarcastic comment but i find it crazy how people feel they are entitled when it's free) EDIT: sorry i meant this rant at the one complaining for the free service not for the paid customers (which is unacceptable)