HN

Comments (171)

• Menu

  udave
  Hope it survive the next few years of codification of all of humanities unfinished cheap ideas.
• Menu

  datsci_est_2015
  Still getting Internal Server Error despite githubstatus claiming “All Systems Operational” and the incident as “Resolved”.Premature declaration of Resolution is pretty bad user experience, if I’m being honest…
• Menu

  openscript
  Does 89.99% count as "three nines availability"?
• Menu

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

  rapind
  Based on the comments in this thread, you'd think that Reddit was down.
• Menu

  freakynit
  So, "git push" is down ... how are github engineers gonna push the fix now?
• Menu

  nevir
  Definitely not resolved yet.
• benlivengood
  Forgejo/Gitea are pretty easy to set up and compatible with GitHub Action syntax. PRs work almost identically. The mildly annoying part is that Kaniko got deprecated by Google and the company that forked and maintains it doesn't publish binaries so you'll have to build it from source yourself if you want isolated non-root builds in your runners. Any of the major LLMs will get it running pretty solidly without much trouble, though.I combined it with Zot for an OCI registry but there are quite a few choices there.
• Menu

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

  gabeyaw
  https://mrshu.github.io/github-statuses/
• wreath
  Silver lining is that this slows down the all the crappy half baked vibe coded crap from being shipped.
• Menu

  bob1029
  The biggest challenge I have with this is that the outages are still not bad enough to justify the suffering of self-hosting everything or adopting an enterprise account manager. The Pareto front is really annoying here.My clients would need to experience a proper multi-day outage (e.g. Monday thru Wednesday) to force the real conversation. Executive leadership is generally not interested in risking a migration to an alternative solution unless the current solution is actively and unambiguously engulfed in flames with a non-zero # of casualties involved.Hosting it yourself is a nightmare if you are trying to cover issues, pulls, project boards, actions, pages, etc. If it were so easy to self-host the GitHub experience, I don't think we'd be in threads talking about how a billion dollar company is fucking it up every week. Self-hosting just the git front end with a web shell is not GitHub. That is a pretty severe case of moving the goal posts. Now, whether or not your business only needs the git SCM piece is a separate conversation. Maybe you shouldn't have been using GitHub in the first place and moving off would be trivial.The value of GitHub for me descends in roughly this order: 0. The ability for non-developers to interact with the system 1. Issues 2. Pull requests 3. Notifications 4. Enforcement of process over PRs 5. Project management 6. Actions 7. Git SCM If I didn't care about the first six things I would still be rocking Jenkins and TFS.
• Menu

  knowknow
  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?
• MaoSYJ
  We need the opposite at this point, make an article when they had an entire week without incidents
• Menu

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

  balanceiskey15
  GitHub added new webhook IP ranges this morning, curious if that's related.
• sidharthkmenon
  honest question - has anyone moved to cursor origin after outages like this? why / why not?
• time0ut
  Well it is a Wednesday.I noticed because SSO was down. They don't even report on that as far as I can tell.
• Menu

  cowlevel
  gitea, forgejo, gitlab CE, and ssh still working fine
• projectescape
  GH reliability has been a regular question mark lately, and many time issues are not reported publicly too.In the past 2 months I've seen 3+ instances where GH action were not triggered on commit pushes, leading to silent workflow failures, and seeing GH merge queue being stuck for 3+ hours for production product facing repos
• colek42
  We kept pushing to GitHub. Pushgate.dev is a gitproxy. It forces your agents to run tests and validates them. We keep the happy path as fast as possible and use Cloudflare's infrastructure for high resilience. Full disclosure: I am the founder of TestifySec; Pushgate is a new product.
• zer0x4d
  My self hosted Gitlab still at 99.9% uptime since the last time github/gitlab were down.
• Menu

  geooff_
  Actions being down is one thing - I can't even land a PR.
• franey
  I'm still having trouble pushing to my repo although the issue. is marked as resolved. Maybe the fix needs some time to seep through various servers.Edit: 4 minutes later and I can push again
• aleqs
  GitHub is now one of the least reliable services in my stack, I'm in the process of moving everything off and keeping it for public/open projects for discoverability/discussion purposes only.I've also noticed a meaningful decline in the quality and reliability of several other major software/apps and services - notably Google maps, Spotify, codex. (Is this because of AI?)Codex, especially, is a strange one - initially I added it beside Claude code thinking it would actually be a higher quality, faster alternative (even if the model/harness is not quite as good at coding as Claude code/opus), and it seemed that way for the first few weeks. At this point though, codex is completely unusable for me - the contexts from different sessions are polluting/mixing with each other, prompt history is mixing/polluting each other. Codex randomly enters safe sandbox mode or whatever multiple times a day per session - it just starts seeing everything as read-only and loses tool and MCP access. It also randomly gets interrupted all the time for no apparent reason - 'your session has been interrupted' - so much for 'autonomous'. And holy shit codex is sooo slow, I'm guessing there are both server side and client side rate-limits, I have the 20x pro plan and I can't even use it up (I use up my Claude code pro 30x in 2-3 days, though to be fair Anthropic usage limits are arbitrary and low), because it is so slow plus all of the issues and constant random stops/blockers that prevent any kind of long-running autonomous work.Opened a couple codex issues on GitHub for these things - all closed as duplicates. I look at the existing issues - all closed as resolved.What a horrendous shitshow.
• bitlad
  It started after I removed my primary email in the profile.Did I break this? Making me insecure about changing anything on github.
• Menu

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

  pixelesque
  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"
• Menu

  alexellisuk
  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.
• anon
  undefined
• acclay
  I'm tired, boss.
• Menu

  shevy-java
  We need a decentralized github-like git system.
• Menu

  pullshark91
  Was GitHub always like this?
• tripleee
  Three days in a row now right?
• iercan
  first time seeing "git push" on github throwing an "Internal Server Error"
• rvz
  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.
• uptownhr
  I still cannot push :(
• hdgvhicv
  Must be a Y in the day
• x3n0ph3n3
  They claim it's resolved, but I'm still seeing issues.
• nharziro
  this is getting ridiculous.
• Menu

  esafak
  This is such an opportunity for competitors. I hope they don't squander it.
• acedTrex
  Im so grateful that coding is solved
• honeycrispy
  Funny, yesterday git operations had an unreported outage too. I couldn't pull changes for ~10 minutes.
• sleepybrett
  i see they started letting the github engineers ship code again after that shitshow last month.
• anon
  undefined
• Menu

  bossyTeacher
  This is becoming way more frequent than a monthly event. Does anyone know why GitHub keeps having incidents?
• mococa
  Again?
• MadrasTh0rn
  Love it
• Menu

  oslem
  Color me shocked
• coliveira
  That's what you get when the bulk of open source is now depending on Microsoft.
• throw03172019
  Just another day.
• Brian_K_White
  holy crap push is a new low
• HenkieTenkie
  Another case of tactical downtime.
• aleksandrm
  "Rewrite GitHub in Rust. Make no mistakes."
• Menu

  caaqil
  Who even runs GitHub at this point?
• jeremyjh
  codefloe.com is still up
• anon
  undefined