GitHub Incident with Webhooks, Actions, etc.

(githubstatus.com)

42 points | by jbredeche 55 minutes ago

13 comments

  • dgritsko 50 minutes ago
    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)
    • colechristensen 23 minutes ago
      I implemented my own, it was time well spent.

      The features I care about work as I want them to, the features I don't care about are kinda janky.

    • xyst 25 minutes ago
      self hosted forgejo and forgejo action runners for my homelab
      • huijzer 11 minutes ago
        Yup am running too for 2 years now and love it. It’s my favorite service. Uptime is basically 100% since it’s only down when I’m doing server maintenance (apt get update and reboot) and then I’m not pushing anyway.
    • x86a 46 minutes ago
      We switched to self-hosted GitLab several outages ago
      • Riemer 32 minutes ago
        Just don't expose them to the internet. They have a lot of CVEs latey, some even allowing full control
        • sandeepkd 11 minutes ago
          How would that work out for remote workers and agents?
      • Aaronstotle 45 minutes ago
        Yeah, switched over to self-hosted Gitlab back in mid-June and feels like the right choice
  • plasma 4 minutes ago
    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.
  • OptionOfT 45 minutes ago
    I visit https://status.github.com it is the second suggestion, after https://github.com/ itself.
  • tosser811 40 minutes ago
    Dead in the water for actions that are merge requirements here.
  • Riemer 30 minutes ago
    Codeberg has been pretty stable for me
  • omegaSigma95 21 minutes ago
    [dead]
  • beredon 49 minutes ago
    [dead]
  • Vosporos 0 minutes ago
    Great day to be on Codeberg
  • hrpnk 27 minutes ago
    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.

    • colechristensen 21 minutes ago
      I'm not saying bots/LLMs aren't making GitHub's job harder but I saw an uptime graphic with a pretty stark and obvious change pre/post acquisition by Microsoft.
    • deadbunny 23 minutes ago
      If you believe Twitter "weed[ed] out the bots" I have a bridge to sell you.
  • mtremsal 38 minutes ago
    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.

  • saejox 42 minutes ago
    i have githubstatus.com on my bookmarks. Maybe i should make it my homepage?
  • bpiroman 9 minutes ago
    Yet everyone still uses GitHub lolz
  • mococa 31 minutes ago
    Another, another incident