34 comments

  • rapind 39 minutes ago
    Based on the comments in this thread, you'd think that Reddit was down.
    • DaSHacka 0 minutes ago
      I suspect it'll only become more common as Reddit enshittifies further and further. The platform is basically unusable for anyone, thus its suitability as a 'containment zone' for the redditor phenotype goes down with it.

      I hope BlueSky makes a Lemmy-style Reddit alternative, just something to satiate people's social media-ified forum fix.

    • iambenm 3 minutes ago
      "Please don't post comments saying that HN is turning into Reddit." [0]

      [0] https://news.ycombinator.com/newsguidelines.html

      • schrodinger 0 minutes ago
        This isn't that imo... do you think it violated the spirit of that rule?
    • icantevenhold 5 minutes ago
      Complaining that HN is becoming Reddit is imo even worse than posting Reddit-level comments - those are at least sometimes funny
  • freakynit 53 minutes ago
    Spent 5 minutes debugging why my builds were failing... then recalled github is not google when it comes to availability... checked status.github.com ... and voila.. there it is.
    • embedding-shape 33 minutes ago
      I'm surprised people still rely so much on GitHub. Anything I want to (have to*) be able to deploy on a moments notice, for hotfixes and what not, was moved away from Github like a year ago, because of the horrible uptime. Did others not get the memo yet?

      It's not getting better, if anything it's getting worse. Best time to get off GitHub was yesterday, the second-best day to get off is today. Tangled, Codeberg or self-hosted Forgejo (my approach) or Gitea are all good alternative solutions here.

  • udave 5 minutes ago
    Hope it survive the next few years of codification of all of humanities unfinished cheap ideas.
  • freakynit 44 minutes ago
    So, "git push" is down ... how are github engineers gonna push the fix now?
    • bearjaws 34 minutes ago
      rsync and sftp, like god intended
      • redanddead 26 minutes ago
        Like the olden days
        • ChuckMcM 19 minutes ago
          Nah in the olden days we'd load a tape with patches and the code would read a patch off tape, apply it, then read the next one. lol.
    • xydone 16 minutes ago
      git push --force. No time for the lease either
    • tripleee 35 minutes ago
      in vim over ssh of course.. agents can use vim right?
      • dodslaser 23 minutes ago
        Yeah, but they keep trying to use Emacs commands...

        C-x M-c M-unfuck-git

    • whalesalad 42 minutes ago
      sudo git push
    • Taurenking 40 minutes ago
      [dead]
  • gwbas1c 34 minutes ago
    What's frustrating is that:

    1: The status site says that pull requests are working,

    2: A PR I'm working on right now is missing commits,

    3: The contact support page errors out.

  • mococa 0 minutes ago
    Again?
  • user- 25 minutes ago
    I can attest to the outage starting around 11:05, as that’s when my GitHub auth for Tailscale SSH broke. Of course, the next 10 minutes of troubleshooting and checking GitHub’s status page showed “all systems operational,” so I assumed it was something on my end. Then, it started working again.

    And while I was typing this comment it just blipped again. Atleast this time I know why.

    I feel dumb for setting up tailscale like 7 years ago using the github auth, time to figure out how to just move to email on that account.

  • odo1242 14 minutes ago
    To be fair to GitHub, outages are pretty short (~40 minutes), and they rarely impact critical parts of the service, nor do they affect one’s ability to work (git offline)
    • slowin 8 minutes ago
      Not being able to push is pretty critical.
    • mococa 0 minutes ago
      In Mars, right?
    • m2ger 4 minutes ago
      git push ending up with Internal Server error is similar to save file ending up with disk full error. yes, it can work after 40 minutes, and one can go to lunch and retry later, but here in Europe the troubles started at the end of a (normal) workday.
    • OrderlyTiamat 4 minutes ago
      40 minutes is an eternity when you can't push to a gitops repo with a PRD issue.
      • mschuster91 3 minutes ago
        ... and that is (yet another example) why pipeline driven gitops is a really darn bad idea.
    • lenerdenator 8 minutes ago
      I'm not able to get code pushed, meaning I can't address PR feedback, meaning I can't get things approved, meaning code isn't getting merged to main and thus a ticket isn't getting closed. Sounds pretty critical to me.
  • hdgvhicv 5 minutes ago
    Must be a Y in the day
  • balanceiskey15 57 minutes ago
    GitHub added new webhook IP ranges this morning, curious if that's related.
    • gagan2020 55 minutes ago
      That might be the cause but let's see.

      There 4 updates contains webhook mention in 2 of the updates.

      "Webhooks is experiencing degraded performance"

  • cowlevel 54 minutes ago
    gitea, forgejo, gitlab CE, and ssh still working fine
    • user43928 28 minutes ago
      I never noticed downtime with public GitLab. It's also generally better than GitHub and Actions.

      A self-hosted enterprise GitLab instance in Azure, on the other hand, has had outages and performance degradation quite a few times.

      • cowlevel 19 minutes ago
        Of course. Azure is the reason GitHub is down so often, too.
    • hermannj314 30 minutes ago
      Exactly. I'm running forgejo in a container, pushing backups to a private S3 storage, and sent the forgejo team a small liberapay payment.

      Maybe 30 minutes to get it all setup and then I moved on with my life.

  • knowknow 37 minutes ago
    Embarrassing that a multi-billion dollar corporation that other billion dollar corporations depend on seems to be fine with breaking their clients workflows. Was github always this shoddy or has something changed to cause this many outages?
    • mjr00 29 minutes ago
      > has something changed to cause this many outages?

      AI coding. Which can be interpreted one of two ways:

      * The generous way, which is that Github is so overloaded with massive volumes of AI codebases and AI-driven automation that they're hitting a scale they never anticipated; or

      * The not-so-generous way, which is that Github itself was one of the first companies to push everyone to AI code as much as possible, which has lead to an eventual breakdown of the stability of the system, as the people responsible for it no longer understand how it actually works, leading to production outages once every few days.

      • cowlevel 22 minutes ago
        It also coincides with GitHub moving to exclusively Azure infrastructure. Azure is a terrible shit show for reasons that have nothing to do with AI.
        • nosefrog 8 minutes ago
          Haha I hope this is true, it fits my experience on Azure. 0 machines available. If someone from GitHub wants to chime in.
        • franktankbank 5 minutes ago
          Azure sucks balls. Its support has no clue whats going on.
    • o_m 25 minutes ago
      Give them some slack. Their core product is AI, not version control
    • ainar-g 23 minutes ago
      > Was github always this shoddy or has something changed to cause this many outages?

      The data speaks clearly: https://damrnelson.github.io/github-historical-uptime/

    • embedding-shape 31 minutes ago
      They used to run their own data centers, and while the unicorn (their error page back in the day) was visible sometimes, it wasn't nearly as bad as things are today.

      And of course, Microsoft is saying that none of this downtime is at all related to them moving everything to Azure, and also at the same time they'll fix all this downtime by finishing moving everything to Azure.

      I wouldn't hold my breath here.

    • TavsiE9s 36 minutes ago
      I mean... they got acquired by Microsoft.
      • cowlevel 22 minutes ago
        Almost 10 years ago
  • time0ut 39 minutes ago
    Well it is a Wednesday.

    I noticed because SSO was down. They don't even report on that as far as I can tell.

  • geooff_ 59 minutes ago
    Actions being down is one thing - I can't even land a PR.
    • gagan2020 58 minutes ago
      Same here. I wanted to push something on Github and its was giving 500. This is most severe issue in recent times.
    • vitosartori 58 minutes ago
      PR? I can't even push haha
      • laurent123456 58 minutes ago
        I can't even create issues (error 500)
  • pixelesque 51 minutes ago
    One of the PRs I eventually managed to open 8 mins ago had a page flash up a generic error page containing a badge error of: "Unexpected token '<', "<!DOCTYPE "... is not valid JSON"
    • aarestad 49 minutes ago
      99% of the time, this is a server returning a generic 500 HTML response to an HTTP call that was expecting a JSON response.
  • acclay 42 minutes ago
    I'm tired, boss.
  • alexellisuk 54 minutes ago
    I thought it was odd that we'd not had one of these for a few weeks.

    A few hours ago GH pages just would not publish at all.. and the status page showed as fine, I guess it's now cascaded into a proper event.

    • malfist 17 minutes ago
      Not had one for a few weeks? There was an outage on Monday (as usual)
    • cowlevel 20 minutes ago
      There was one yesterday.
  • rvz 39 minutes ago
    The last time GitHub went down was...yesterday.

    GitHub is never going to improve and at this point. You might as well say that the AI chatbots, Tay and Copilot are maintaining the platform and are running it into the ground. No CEO of GitHub to go to as well.

    It is time to self host instead of using something as broken as GitHub as I predicted 6 years ago.

  • iercan 56 minutes ago
    first time seeing "git push" on github throwing an "Internal Server Error"
  • esafak 11 minutes ago
    This is such an opportunity for competitors. I hope they don't squander it.
  • acedTrex 12 minutes ago
    Im so grateful that coding is solved
  • tripleee 31 minutes ago
    Three days in a row now right?
  • honeycrispy 20 minutes ago
    Funny, yesterday git operations had an unreported outage too. I couldn't pull changes for ~10 minutes.
  • bossyTeacher 33 minutes ago
    This is becoming way more frequent than a monthly event. Does anyone know why GitHub keeps having incidents?
    • cowlevel 21 minutes ago
      Because it's vibecoded and because it's running on Azure
    • christophilus 31 minutes ago
      It’s mentioned on most threads, but their traffic and usage is way up due to AI / agentic programming.
  • MadrasTh0rn 34 minutes ago
    Love it
  • sleepybrett 30 minutes ago
    i see they started letting the github engineers ship code again after that shitshow last month.
  • aleksandrm 48 minutes ago
    "Rewrite GitHub in Rust. Make no mistakes."
  • coliveira 38 minutes ago
    That's what you get when the bulk of open source is now depending on Microsoft.
  • HenkieTenkie 31 minutes ago
    Another case of tactical downtime.
  • oslem 43 minutes ago
    Color me shocked
    • nstott 31 minutes ago
      This is so frustrating. I wish it were easier to migrate away from this tool
  • Brian_K_White 42 minutes ago
    holy crap push is a new low
  • caaqil 53 minutes ago
    Who even runs GitHub at this point?
  • jeremyjh 47 minutes ago
    codefloe.com is still up