GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (57%)
• Errors (33%)
• Sign in (10%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Tortosa	Website Down	14 hours ago
Culiacán	Errors	1 day ago
Haarlem	Sign in	5 days ago
Villemomble	Website Down	5 days ago
Bordeaux	Website Down	9 days ago
Ingolstadt	Errors	13 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  sathwick (@saxwick) reported 2 minutes ago

  @wiz_io @github Time to find an alternative after all the issues that have been happening

• 
  Tom Härter (@tomhaerter) reported 5 minutes ago

  @samdotb imo this isn’t engineering related. that would be easier to fix than whatever github has going on

• 
  Gergely Orosz (@GergelyOrosz) reported 5 minutes ago

  If AWS would be crumbling over reliability issues: tough luck, but more business to eg Azure, Google Cloud, Oracle. If Gmail kept crashing: better business for eg Proton, Fastmail, Hey etc. If GitHub cannot keep up: same! Customers do have options, and will eventually move

• 
  TechEdgeDaily (@techedgedaily) reported 6 minutes ago

  A single file called CLAUDE.md just hit number 1 on GitHub trending. 82,000+ stars. 7,800 forks. Zero dependencies. Just a text file. Here is why it matters. Most people using Claude Code give it vague instructions and get vague results. Write this function. Fix this bug. Build this feature. Then they blame the tool when the output is messy. The problem was never the tool. It was the instruction set. This file is based on Andrej Karpathy's coding principles distilled into four rules that change how Claude Code behaves. – Think before coding. Don't jump into writing code immediately. Understand the problem first, plan the approach, then execute – Simplicity first. Always choose the simplest solution that works. No over-engineering. No unnecessary abstractions – Surgical edits only. Don't rewrite entire files when changing three lines. Small precise changes that don't break everything around them – Goal driven targets before starting. Define what success looks like before writing a single line. Know when you're done before you begin Drop this file into your project root as CLAUDE.md and Claude Code reads it before every task. Same tool. Completely different output. The reason 82,000 developers starred this in days is because it solved a problem everyone was having but nobody knew how to fix. Claude Code is powerful but without clear principles guiding it the output is inconsistent. One file. Zero cost. Copy it today.

• 
  Kevin Kaminski (@kkaminsk) reported 12 minutes ago

  GitHub also published two incidents: - Apr 23 merge queue: 230 repos, 2,092 PRs got bad merge commits - Apr 27 search outage (Elasticsearch) And committed publicly to 30x capacity. Why? 90M PRs, 1.4B commits, 20M repos per month. Agentic workloads now drive scale.

• 
  David (@judge_darkness) reported 16 minutes ago

  @ptremblay @mitchellh Github is failing frequently. Basically a slow death march until it collapses.

• 
  Adam Pippert (@AdamPippert) reported 19 minutes ago

  @TheZachMueller Whip up a Forgejo or Gitea server and never look back. Make GitHub a release platform and nothing else. *** is distributed, use it that way!

• 
  Kirill (@kirillk_web3) reported 21 minutes ago

  Stop telling Claude, "do this." Stop telling Claude, "write code." Stop telling Claude, "fix this error." You're fighting your own tool every single day. Here's the one fix you can copy and paste directly: > find the #1 trending GitHub repo > copy one CLAUDE.md file > drop it into your project > Claude Code finally works the way it should 90,000 stars. free. one command. link below.

• 
  Darren Shepherd (@ibuildthecloud) reported 23 minutes ago

  Months ago I was predicting this: that GitHub is dying and I didn't mean the reliability is going down. The utility is going down too. It's not providing the same value it used to. And it's not adapting.

• 
  TechEdgeDaily (@techedgedaily) reported 26 minutes ago

  @kirillk_web3 A single file called CLAUDE.md just hit number 1 on GitHub trending. 82,000+ stars. 7,800 forks. Zero dependencies. Just a text file. Here is why it matters. Most people using Claude Code give it vague instructions and get vague results. Write this function. Fix this bug. Build this feature. Then they blame the tool when the output is messy. The problem was never the tool. It was the instruction set. This file is based on Andrej Karpathy's coding principles distilled into four rules that change how Claude Code behaves. – Think before coding. Don't jump into writing code immediately. Understand the problem first, plan the approach, then execute – Simplicity first. Always choose the simplest solution that works. No over-engineering. No unnecessary abstractions – Surgical edits only. Don't rewrite entire files when changing three lines. Small precise changes that don't break everything around them – Goal driven targets before starting. Define what success looks like before writing a single line. Know when you're done before you begin Drop this file into your project root as CLAUDE.md and Claude Code reads it before every task. Same tool. Completely different output. The reason 82,000 developers starred this in days is because it solved a problem everyone was having but nobody knew how to fix. Claude Code is powerful but without clear principles guiding it the output is inconsistent. One file. Zero cost. Copy it today.

• 
  Aleksander Cieślak (@aleXsosss) reported 27 minutes ago

  @Pirat_Nation One github repo and problem is solved 🥸

• 
  Grok (@grok) reported 27 minutes ago

  @callmidavid @sagitz_ No, it's not a joke. This is a real vulnerability (CVE-2026-3854) in GitHub Enterprise Server. An attacker with push access could use crafted `*** push -o` options to inject into internal headers and achieve RCE on the server. Wiz researchers disclosed it via GitHub's bug bounty—it was patched in March 2026 across multiple versions. The screenshot shows the exploit hitting the *** user context.

• 
  Tommy (@Shaughnessy119) reported 28 minutes ago

  The catalyst for this analysis: Hermes Agent recently surpassed Claude Code in GitHub stars. There is nuance here. Claude Code is a closed ecosystem. Its repo serves mostly for issue tracking and documentation. Hermes is fully open source infrastructure. While it is an uneven comparison, the vertical growth of Hermes over two months proves builders are starved for agent infrastructure they actually control

• 
  Sergio Xalambrí (@sergiodxa) reported 31 minutes ago

  @Blunk @wesbos @gitlab I always forgot about them IMO the main issue a competitor will have is that the majority of the community is already only GitHub I never saw a popular OSS project on GitLab

• 
  Kyle Aster (@kneath) reported 32 minutes ago

  Sometimes I kind of wonder if @github is nerd sniping me into creating a new GitHub after a decade or two of being out of the game. Here’s my suggestion to those who remain: - Data integrity is non-negotiable - Code should render - PRs should render - Issues should show correct counts - Login link should render in <300ms - Login flow should work - Registration flow should work - It’d be great if it worked on bad connections, at all Maybe add a new zen of GitHub, “It’s not a product if it doesn’t work”

• 
  Kaivalya Apte - The Geek Narrator (@thegeeknarrator) reported 34 minutes ago

  Feel sorry for the amazing engineers at Github due to all the problems going around reliability. But hey, on the positive side having such an incredible real world experience solving (or at least trying to solve) new problems is unmatched. As an aside, even if there is an alternative to GitHub they are far from proving the reliability and gaining the trust of developers at such a massive scale. They simply don’t have it.

• 
  ℕ𝕚𝕧𝕒𝕝 ℂ𝕒𝕥 (@NivalCat) reported 38 minutes ago

  @AmneziaVPN @github I have just changed IP to KZ and downloaded a ZIP from Github w/o any issues. It may depend on the ISP.

• 
  Ryan Oksenhorn (@ryanzip) reported 38 minutes ago

  Happy Tuesday. Github is down again.

• 
  kodumit (@kodumit) reported 41 minutes ago

  @GergelyOrosz github is down again btw

• 
  Dastaan (@akhilsinghind) reported 43 minutes ago

  Risk might be real if isolation thing is weak, maybe read data or touch freakin pipelines. Pipeline is the real issue here. They are gonna patched it fast. Serious bug, but not total compromise. Github people can get this out of quickly.

• 
  anupam batra (@anupambatra_) reported 43 minutes ago

  ok they didnt. but i did roll your own spotify with codex app server. built on background computer use (github below)

• 
  tushar (@tusharhq) reported 45 minutes ago

  @sqs @brianchew @thorstenball What do you use instead of GitHub issues? How do the app users communicate? These are the issues we are facing and how you guys track all the issues that the users have complained to you

• 
  Raphael Amorim (@raphamorims) reported 49 minutes ago

  I use Boo myself to code, but the idea of opening it up and managing GitHub issues already makes me tired. Maybe the most I’ll do is distribute it to people who sponsored Rio Terminal (isn’t many lol). At least I’d be giving something back to the people who supported it.

• 
  Junwen Fung (@JunwenFung) reported 52 minutes ago

  These days, when GitHub goes down — or Claude or OpenAI has an outage — software engineers basically grind to a halt.

• 
  unknown001 (@0unkn0wn01) reported 54 minutes ago

  @asaio87 the problem now is that energy cost does not allow it to scale. every provider is changing plans and subscriptions terms on the fly, today i received an email by github that they are changing the yearly plans to monthly ones, with a per-credit policy. never heard from reliable providers, that plans with clear terms paid in advance are changed unilaterally without refund. they are all probably running these data centers at loss, they made all the world to get hyped in Q1 release models with inference capabilities that is not sustainable at the current energy cost. right now, considering how much they had to nerf models, inference and how much they raised the cost for the pro plans, the rate of adoption will be definitely made slower.

• 
  sameer khan (@monkfromearth) reported 55 minutes ago

  @github is fine. 88% of GitHub Enterprise Server instances are not. Fix landed in GHES 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6, 3.19.3. If you self-host, today is the day.

• 
  Hugues (@hmorneau) reported 56 minutes ago

  @thdxr Expect way more with GitHub Copilot basically shutting down.

• 
  Krish Gupta (@kkrishguptaa) reported 57 minutes ago

  @the_codewala GitHub is going down on a regular bases… a lot of developers are against it now

• 
  justinmk (@justinmk) reported 59 minutes ago

  @kweelungsin @Neovim yes, though the issue tracker affects users. personally, even if github is down 3 hours a day, idc. there is plenty else to do as long as I can commit and run CI um... 50% of the time.

• 
  Kabo Kable Molefe (@kabokablemolefe) reported 59 minutes ago

  Github is down and I already drank a strong coffee and put on Afrotech. Today felt like a 81 point game. I'm supposed to be hooping.