GitHub Incident with Webhooks, Actions, etc.

dgritsko

So frustrating. You can only experience so many of these outages before you seriously have to start questioning whether it makes sense to continue to use GitHub (and many have already long since reached this point)

OptionOfT

I visit https://status.github.com it is the second suggestion, after https://github.com/ itself.

saejox

i have githubstatus.com on my bookmarks. Maybe i should make it my homepage?

tosser811

Dead in the water for actions that are merge requirements here.

mtremsal

I don't know them, and am not an investor, but I'm trying Blacksmith as a GHA alternative because I'm losing my mind over the regular downtime. Apparently all the cool kids already use it, so... Obviously this doesn't help at all with Webhooks. update: first jobs are green already. migration took 5 minutes. so far so good.

mococa

Another, another incident

Riemer

Codeberg has been pretty stable for me

hrpnk

Wonder how soon GitHub will tighten rate limits on OSS GitHub further and start charging per API call like x.com did to weed out bots... Not being able to isolate OSS and Enterprise workloads properly is also quite the downer.

bpiroman

Yet everyone still uses GitHub lolz

plasma

There has been degradation in their copilot cloud agent in the last few weeks (sessions erroring/disappearing, connections not working, etc) that is not on a status dashboard.

Vosporos

Great day to be on Codeberg

godzillafarts

We self-host actions and this still impacted us. Incident resolved 30 minutes ago, but all our builds are still queued/pending. Maybe GitHub needs to replay some webhooks?

fishgoesblub

The more these incidents happen, the more I think about I talking to investors about investing in my GitHub alternative; an old computer in the corner running Gitea.

adamddev1

I have been moving everything away to a self hosted Forgejo, and I am so happy. But now I wonder about Netlify. Their dashboard is jammed full of prompt boxes for agents. Could more AI psychosis there turn that into a house of cards as well?

rvz

Again? Last time it went down was less than a week ago. GitHub continues to remind you to self host. [0] 6 year prediction and counting. [1] [0] https://news.ycombinator.com/item?id=50307843 [1] https://news.ycombinator.com/item?id=22868406

time0ut

When I type git in chrome, it autocompletes as githubstatus.com.

throw03172019

Even after they “resolved” it. I had two stuck actions in the queued state. Canceling failed. They are still stuck as “Queued” 2 hours later.

unconscionable

Getting used to this!

cromka

I was setting up a project for CI/CD for the first time in a much more complex way than before and this issue had me scratch my head a lot as I was questioning my sanity. Then I remembered it's GitHub and that it's just another outage, just not reported on their dashboard yet.

danielmartins

After the GitHub post about their new git storage architecture, I wonder how other parts of the system, like issues, actions and webhooks, are being improved to handle current scaling problems, if at all. Apparently the git layer is not the only thing that needs a little attention.