Live data from Hacker News

Incident with Actions and Pages

githubstatus.com

21–30 of 407 posts

Re: Incident with Actions and Pages

#21
post #10

I think we should start betting if GitHub will be down on Polymarkets or something at this point.

The future of SRE will be the company putting some amount of money on a prediction market against the site going down and you get to take home the winnings as long as the site stays up.

Re: Incident with Actions and Pages

#25
post #16

Why do they go down so often? Is it true that the reason is that they've incorporated too much AI without human review?

It's (a) they're under massively increased load because everyone's vibing up new projects these days, (b) they've been in a weird frankenstein "on azure but also we have our own control plane" state for years and they're pushing to no longer have that be the case.

I don't think vibecoding at Github has much to do with it.

Re: Incident with Actions and Pages

#26
Are there any GitHub Actions-compatible CI services out there that don't rely on their infrastructure? I know of depot's but no others; are these resilient to these outages or do they still lose functionality? I imagine the latter but I don't know.

Re: Incident with Actions and Pages

#27
post #16

Why do they go down so often? Is it true that the reason is that they've incorporated too much AI without human review?

It's (a) they're under massively increased load because everyone's vibing up new projects these days, (b) they've been in a weird frankenstein "on azure but also we have our own control plane" state for years and they're pushing to no longer have that be the case. I don't think vibecoding at Github has much to do with it.

Ah, yes. A lot more repos, commits, and most importantly huge PRs.

That makes sense. Thank you!

Re: Incident with Actions and Pages

#28
post #14

Insane, 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...

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 from a single machine with an omnibus package that handles everything to a full blown autoscaling Kubernetes deployment.

Re: Incident with Actions and Pages

#29
post #14

Insane, 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...

Same thoughts - we use an action to ship to production, its builds an image, pushes it to ECS which triggers a deployment.

We can't be blocked here. Seems silly what we settled on this, but for a long time GitHub had been reliable enough for many years, but things are sliding down the pan as of late.

Re: Incident with Actions and Pages

#30
post #16

Why do they go down so often? Is it true that the reason is that they've incorporated too much AI without human review?

GitHub had a blog post about this recently. They reported a significant uptick in volume (repos created, PRs, etc.), which they attribute to AI usage and tooling.
Post reply on HN