Live data from Hacker News

Incident with Actions and Pages

githubstatus.com

141–150 of 407 posts

Re: Incident with Actions and Pages

#141
free 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

#142
post #61

Someone said GitHub is racing to the mythical "zero nines of availability" and I love it

Hmm... 88.8888888%? Jesus, that's both horrible and seems within reach.

Yep, they just need to improve their reliability by 2%!

https://mrshu.github.io/github-statuses/

Re: Incident with Actions and Pages

#143
post #55

Earlier 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

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

#146

free 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)

There are plenty of paying enterprise users that are also affected.

Re: Incident with Actions and Pages

#147

free 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)

We pay github quite a bit of money and it's down for us too

Re: Incident with Actions and Pages

#148
post #83
post #62

Earlier 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

forget it, Jake; it’s Azure

Re: Incident with Actions and Pages

#150
I've been against self hosting internal tools for a long time mainly because of the devops and other overhead. But AI based devops makes it so easy now to spin up whatever you want now that I'm reconsidering that. I use a lot of ansible for several of our deployments. At this point, most of that is managed via codex.

For Git, all you technically need is ssh access and some backup strategy for your server. It would be bare bones but workable. And there are of course plenty of OSS things that are a lot nicer than that.

I'm still using gh and gh actions and we are mostly below the freemium layer with that. But it is kind of slow and honestly a dedicated vm plus some high CPU/memory workers we can spin up on a need to have basis might be a lot faster. With GH outages becoming more common, my hand might be forced a bit.

In recent weeks, I've spun up listmonk (mailing list solution), matrix (as a slack alternative), and a few other things specific to our software stack. A github alternative would be more of the same. We don't need a lot.

The main objection is that with more moving parts to worry about, the workload for me also increases. Things need updating, monitoring, backups, alerting (and responding to alerts), etc. That sucks up my time and that is scarce.

Another reason for self hosting these days is that with agentic AI tools, self hosted things are a lot easier to integrate into agentic systems. If it is self hosted, you don't have to worry about API limitations, rate limitations, walled gardens, etc. All the traditional SAAS silos are becoming a problem from that point of view. The more locked down it is, the bigger the motive for moving away from it. That's why we ditched Slack for Matrix. Slack is hopelessly locked down and tedious to deal with. Matrix is super easy for this.

Post reply on HN