comments (8)

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

    dgritsko

  • 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?

    godzillafarts

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

    OptionOfT

  • 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.

    plasma

  • Codeberg has been pretty stable for me

    Riemer

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

    tosser811

  • 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.

    fishgoesblub

  • 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.

    mtremsal