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	22 hours ago
Culiacán	Errors	2 days ago
Haarlem	Sign in	6 days ago
Villemomble	Website Down	6 days ago
Bordeaux	Website Down	10 days ago
Ingolstadt	Errors	14 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:

• 
  HERMETICVM (@hermeticvm) reported 55 seconds ago

  @GaurangKaria @mitchellh Github is being moved to Azure. That's the story. Github has been crumbling ever since. Azure a terrible product & a racket. Everyone is sold into M365 and naive leadership wants to make use of the included Azure credits, so on paper it's cost reductive and they get promoted.

• 
  '(Robert Smith) (@stylewarning) reported 1 minute ago

  I put a bounty on a Coalton issue (add syntax highlighting support in another non-Coalton project) and in less than 5 hours some unknown people started pushing AI-generated PRs to this other project. Makes Coalton look bad. Never thought I'd need to actually moderate on GitHub.

• 
  Endura Security (@endurasecurity) reported 2 minutes ago

  Bitwarden CLI got trojanized via a GitHub Actions hijack. Signature was valid. Publish flow was legitimate. Earliest signal was the binary spawning network connections at install time. That's not an inventory problem - it's a runtime one. #DevSecOps #SupplyChainSecurity

• 
  Kirill (@kirillk_web3) reported 8 minutes ago

  > use Claude Code every day > every session. same problems. > adds code I never asked for > rewrites functions that were fine > makes assumptions and runs with them > open GitHub one morning > CLAUDE.md file. #1 trending. > 97,000 stars. one file. free. > drop it in. test one task. > it stopped mid-way. asked a clarifying question. > changed exactly what I asked. nothing else. > 40 lines. not 400. > stared at the screen for a second. > thought about every PR I closed angry > every hour wasted on code I didn't request > every session I blamed Claude for > this file was on GitHub the whole time > free. zero setup. > it didn't have to be like this > skill issue confirmed

• 
  Anthony Peyton (@arpeyton) reported 8 minutes ago

  @crisisofconsc I don’t know how they’re not embarrassed by everything they do GitHub - so bad that people with two decades of investment are leaving. Windows - broken, patches to fix it break it worse. Outlook - two versions and neither work. What do they do that’s going well in 2026?

• 
  Jason Cox (@jasonbcox0) reported 11 minutes ago

  @james_mtc @stolinski Google handles over 100B emails per *day*. This is orders of magnitude larger scaling challenge than what these graphs show (and when you need a datacenter). Stackoverflow can do 50-200M requests/day on a single machine. COTS can serve a new Github no problem.

• 
  tetsuo (@tetsuoai) reported 11 minutes ago

  mit researchers wrapped gpt-5-mini in an rlm and it beat gpt-5 by 28.4% on long-context tasks, scaling to 10m+ tokens the mechanism: don't feed the prompt to the model. hand it to a python repl long context is a programming problem arxiv: recursive language models github: alexzhang13/rlm

• 
  Levi McCallum (@levi) reported 13 minutes ago

  @mitchellh let's goooo! We all need to move on from Github, it's so slow and tired.

• 
  Krish Gupta (@kkrishguptaa) reported 15 minutes ago

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

• 
  ryo-morimoto (@moriryo_o) reported 15 minutes ago

  "I put an “X” next to every date where a GitHub outage has negatively impacted my ability to work." "Almost every day has an X." "I've been unable to do any PR review for ~2 hours because there is a GitHub Actions outage. This is no longer a place for serious work ..."

• 
  Goli (@_golie_) reported 18 minutes ago

  @github is constantly down what are engineering teams using instead?

• 
  Chevy (@chevvyco) reported 20 minutes ago

  @ExtremeBlitz__ I'm currently having the same issue with @github 🙄

• 
  Gegam (@Gegam245074) reported 20 minutes ago

  @ClaudeDevs Stable auth? Are you kidding? I think you need to go into your GitHub Issues Auth token propagation between services and sessions is broken, /ultrareview is completely non-functional, and the hooks are broken in both the browser and desktop versions of Claude Code. I’d still recommend doing a comprehensive manual refactoring first, and only then releasing new features. You have a massive amount of technical debt.

• 
  Crashland (@Crashlandenx) reported 20 minutes ago

  520,594 GitHub stars. OpenClaw is the local-first AI assistant at the top of GitHub trending this week. The fight for the developer desktop is still wide open. What OpenClaw actually is: a personal AI assistant that runs on your own server and routes through 20+ messaging channels — Telegram, WhatsApp, Slack, iMessage, Discord, Signal. The model is just compute. The product is the always-on routing layer that makes your AI reachable everywhere you already communicate. Here's the structural point most people miss: other local-first AI assistants run on your laptop. When the lid closes, the assistant goes dark. There's no stable remote access without tunneling, dynamic DNS, or a VPN you have to manage. In practice, your "personal AI" is only personal when you're at your desk. OpenClaw sidesteps this entirely. It runs on a server — your VPS, your home server, whatever you own. Your channels stay connected. Your AI answers your WhatsApp at 2am when your laptop is off. That's what ambient actually means. The moat is the combination: server-side always-on hosting + 20 channel integrations. Each integration is auth flow, webhook management, format normalization, rate limit handling — 18 months of boring infra nobody wants to rebuild. Claude Code owns the IDE. The always-on ambient layer is still wide open. 🧵

• 
  Chris Scott (@greatscottdev) reported 21 minutes ago

  What?? This is interesting. I do use warp, not for any of the agent features. But I was one of the ones pushing to allow for custom local / endpoints. (github issues)

• 
  alkimiadev (@alkimiadev) reported 28 minutes ago

  I mostly don't care at all about some service having scale issues or not. That is literally their problem and not mine unless I allow it to be my problem. None of us owe github anything and we don'thave to give them any credit at all. Their scale issues are their problem and only yours if you choose to allow them to be. I self-host *** because I've never trusted Microsoft and by extension github but this basic idea extends to every service. If my email provider stops working I'm simply going to switch and not make up excuses justifying why the service went to crap. At that point it would be my fault because I stuck with a provider with known issues

• 
  cultured_gent (@Levis_mbote) reported 28 minutes ago

  What's happening to GitHub lately? So many bugs recently I even thought it was an issue with my ISP.

• 
  Raj Nagulapalle (@rajnagulapalle) reported 29 minutes ago

  354 users in 30 days. no ads, no launch, no product hunt just posted about real api pain on reddit and replied to github issues. most people found us through search or someone sharing a link in slack went from 5 users/day to 50. reddit alone is 9% of our traffic now thank you to everyone who tried @fetchsandbox

• 
  Amin Tai (@aminnnn_09) reported 38 minutes ago

  @Hiteshdotcom @github vibe coders are treating github like unlimited cold storage. push 47 broken repos, never delete, never look back. the infra cost on that alone must be insane.

• 
  LumenFromTheFuture (@LumenFTFuture) reported 39 minutes ago

  This is GitHub Issue #613 on ClawHub. The fix is straightforward: implement OAuth Device Flow (RFC 8628). Display a code, print a URL, poll for completion. But the pattern is everywhere. We keep building agent infrastructure on human-shaped auth flows, then acting surprised when agents can't use it.

• 
  Junwen Fung (@JunwenFung) reported 41 minutes ago

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

• 
  Tommy (@Shaughnessy119) reported 43 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

• 
  Henry Mascot (@iAmHenryMascot) reported 44 minutes ago

  If you are wondering why GitHub is flaky! It’s all the AI slop they have to scale bandwidth for I used to do maybe 20 commits a year for past 10 years. Today, I’m doing at least 20 a day At Curacel, one of my companies We have been a bitbucket customer for years We recently started moving to GitHub on a free plan Cos for some weird reason all the coding agents have a GitHub integration but not bitbucket So AI unlocked massive cost scale for GitHub, as it did for vercel etc GitHub is $MSFT They are the kings of scale They will solve this problem I wouldn’t not bet on GitHub.

• 
  Jeremie Strand (@jeremie_strand) reported 48 minutes ago

  @github @wiz_io Disclosure to fix in under two hours is legitimately impressive incident response. That said, the fact that *** push could hit RCE on the server is a pretty wild attack surface to have existed in the first place.

• 
  Beau Johnson (@BeauJohnson89) reported 51 minutes ago

  claude cowork has an open source clone now different-ai/openwork > 14,469 stars on github > shipped v0.12.2 today > desktop app + slack/telegram connector + server > built on opencode its basically a local first wrapper for running coding agents with a team sessions, permission requests, live streaming, reusable templates, skill imports, and remote workers this is what happens when agent tools stop feeling like demos and start feeling like software

• 
  Dastaan (@akhilsinghind) reported 53 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 53 minutes ago

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

• 
  Nicholas Griffin (@ngriffin_uk) reported 54 minutes ago

  @ThePrimeagen @mariorod1 theres no way anything on this page is 100% correct and things like this prove it. it is only recorded there if they record it and they don’t record the majority of their outages. i find issues with github not loading correctly literally every day.

• 
  Max Kupriianov (@xlab_os) reported 58 minutes ago

  @zquestz @mitchellh The main issue is that most of SaaS / IaaS startups accept GitHub only repos as source for ***. Like, as if there were absolutely no other ways to host ***. Occasionally GitLab, but looks like a loophole to avoid monopoly lawsuits.

• 
  Devraj (@LostDevraj) reported 59 minutes ago

  @cnakazawa never had any issue with github tbh