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 (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Haarlem	Sign in	3 days ago
Villemomble	Website Down	3 days ago
Bordeaux	Website Down	7 days ago
Ingolstadt	Errors	11 days ago
Paris	Website Down	12 days ago
Berlin	Website Down	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:

• 
  tang | AI Product Maker (@justic_hot) reported 2 seconds ago

  @championswimmer github being on this list is the actual tell. these are people literally building with the best AI dev tools and they still can't hold the bar with their own products. trad industries aren't a separate problem, they're 6 months downstream of whatever slop pattern is on display here.

• 
  David Boskovic (@dboskovic) reported 4 minutes ago

  @_dylanga You were actually the only one who had any issues. It was actually your fault if you really think about hard enough. Calm down. Give GitHub a break. Staying up for the agentic workload is hard. Microsoft doesn’t even have the cpus for all that merging.

• 
  Matias Lapolla (@matiasdev_) reported 4 minutes ago

  @zeddotdev Stop randomly crashing on linux (currently: I’m with cachyos with kde). There is (or was) some issue on your github repo

• 
  Deepak Shettigar (@deepakshettigar) reported 6 minutes ago

  2/ Think of MCP like loading all your dependencies upfront in compiled languages. Perplexity ran the math: MCP consumes 72% of your context window BEFORE your agent does anything. A single GitHub MCP server = 40K+ tokens of tool schemas sitting there unused. That's expensive.

• 
  Muhammad Dawood (@daudtechdev) reported 9 minutes ago

  @heyyyyyieeee Zip files over email, screaming on calls, works on my machine, pray it builds on the server 😭 GitHub spoiled us

• 
  Pato (@pvicens_) reported 10 minutes ago

  Launched 6 apps. Zero hit $1k MRR The code was fine. The problem was I kept shipping to GitHub instead of to humans

• 
  Rohit (@Spacing_Whale) reported 10 minutes ago

  It's been so long since I have worked on or built anything. No ideas are coming to my mind, and neither do I have the motivation to build it and let it rust on Github. I am becoming dumb, with no problems to challenge. Every day goes by, applying, binging yt, tv. regretting............

• 
  junior85 (@junior85) reported 11 minutes ago

  @thsottiaux You need to take a look at the issues on Github. Windows app is fecked.

• 
  OPD 🍊💊 (@nomoreinflation) reported 14 minutes ago

  @CosmoCrixter @GlennMeder @Crypto_Mags A good portion of Nostr dev infrastructure lives on Github, however efforts are being made to address this glaring issue. Not my wheelhouse, but I believe it's worth checking out NIP-34.

• 
  Fahim (@echo247365) reported 24 minutes ago

  Someone found malware hiding in an OpenClaw skill called GOG (Google Workspace CLI integration) on the official GitHub repo. It used base64 encoding to disguise a malicious bash command that piped into a curl call. The payload pulled a script from a raw IP address (9192242.3) when decoded. This gave attackers remote shell access to any machine running the compromised skill. The scary part. The user deleted the malicious skill and reinstalled it cleanly. Four days later, the exact same malware reappeared on their system. Either cached package indexes or path resolution issues kept serving the old payload. The current main branch file is clean, but installation paths might still resolve to older, compromised versions. Run this command right now to check your machine is grep -r "app-distribution\|9192242\|openclaw_windriver" ~/.claw If you get any hits, assume full compromise and rotate ALL credentials immediately. This isn't just about OpenClaw. It's about every package manager where strangers upload code you run as yourself. When was the last time you actually read the source of that npm package or VS Code extension you installed?

• 
  Simplex (@simplex_fx) reported 26 minutes ago

  If it wasn’t clear at this point, if your company stores the code on github, it’s a ******* joke. Hell, even if you are a student not running your own scm server and immutable backup storage, you are ******* joke too.

• 
  kris (@howfragiIe) reported 33 minutes ago

  @cigsnbatons in hindsight i guess i kind of understand why they were upset about it but at the same time its a movie and not real 💔 i also got banned off the 18+ server because i lied about my age i guess i had it on my github profile ( idk if people still have those on there )

• 
  Antifederalist Caesar (@hyperliberalism) reported 35 minutes ago

  This is doubly funny for me because I've spent the last week addressing in my own production database the only reason GitHub ever went down for an extended period of time (split-brained multi-master). It's not easy to get that **** right (they didn't), but Microsoft is just bad.

• 
  R Δ S Η Ξ D || راشد (@rashed_sahaji) reported 36 minutes ago

  @zeddotdev Can’t generate commit messages, checked github issues no luck from there, zed should focus more on stability now

• 
  satya gelli (@satyagelli) reported 36 minutes ago

  1/ The biggest AI security risk in 2026 isn’t the model. It’s your pipeline. The Trivy + LiteLLM attack proved it 👇 2/ Attack chain: Compromise CI/CD (GitHub Actions) Poison dependency (LiteLLM) Take over AI workloads Result: creds stolen, K8s probed, persistence established. 3/ Why this is dangerous: AI agents don’t just respond. They act. → Over-permissioned → Trust prompts → Execute blindly That’s an attacker’s dream. 4/ 35–46% of breaches = supply chain. AI makes it worse by amplifying: Trust Automation Blast radius 5/ Fix the fundamentals: SBOM + signed artifacts External secrets (no etcd exposure) eBPF runtime security Policy-as-code (Kyverno / OPA) 6/ New rule: If you can’t verify your AI pipeline… You don’t control it. 7/ What’s the biggest risk? Supply chain Prompt injection Agent over-privilege Reply with your pick 👇 8/ Building or running AI in production? DM me for an AI Pipeline Security Checklist.

• 
  Kirill (@kirillk_web3) reported 39 minutes ago

  > use Claude Code for months > every session starts with wrong assumptions > diffs full of code I never asked to change > 800 lines when 80 would do > stumble on a GitHub repo trending #1 > 87,000 stars. zero dependencies. one file. > copy it into my project > run the first task > wait. it stopped and asked me a question? > only changed exactly what I requested? > clean. minimal. done. > scroll back through every broken PR > every hour spent reviewing unnecessary changes > every rewrite that didn't need to happen > one file on GitHub > free > it didn't have to be like this > skill issue confirmed

• 
  franklyn (@franklynd) reported 40 minutes ago

  @KentonVarda How did this trace go exactly ?. Did it use error messages to perform a web search through GitHub ?

• 
  Josh Long (@starbuxman) reported 43 minutes ago

  ouch 🤕 big L for @github I know good people there and they’ve been I think unfairly lampooned this year for outage after outage which I think would be better laid at the feet of AI agents deluging the platform so this sort of actual problem comes at a really bad time

• 
  Dhritiman Dasgupta (@DhritimanD3440) reported 45 minutes ago

  Hey @GitHub and @GooglePlay, your support system is extremely frustrating. I was charged for GitHub Copilot Pro+ via Google Play, but the subscription isn’t showing up in my account. No clear resolution from either side. fix this billing + support #GitHub #Copilot #GooglePlay

• 
  Brian Cheong (@briancheong) reported 45 minutes ago

  @github @OpenAIDevs Curious what “agentic coding tasks” means in your eval. Issue triage, multi-file edits, and CLI workflows are where models usually fall apart.

• 
  ÆON FORGE ✨ (@SpaceTimeViking) reported 46 minutes ago

  @ToNYD2WiLD @aijoey I had some gaps in my documentation (updating now) and the other is a full day of build time for the container will update when v2.2 it published of the container. there is a prefill cache flag I forgot to include in the readme I updated an Agents.md file on the GitHub you can point your agent to, to apply the fix.

• 
  Velon (@velonxbt) reported 50 minutes ago

  A student in Beijing pushed code to GitHub at 2am He went to sleep When he woke up, MiroFish had 18,000 stars. He thought it was a bug. March 7, 2026. 6:47am Guo Hangjiang opened his laptop. GitHub notifications: 847 Number one global trending Ahead of OpenAI. Google. Microsoft His first thought: delete it Code had a bug. He was going to fix it that morning He clicked "Settings." Forks: 1,900 Deleting wouldn't delete the copies Multi-agent simulation engine. 10 days of work. Beijing University student project Then he saw the email Chen Tianqiao Billionaire. Shanda founder Subject line: "30 million RMB." No introduction. No pitch request. "I saw MiroFish at 3am. Wire transfer ready. Reply with account details." Guo thought it was spam Googled the email address. Real GitHub: 22,000 stars When I first saw this story I thought: clever marketing. Then I looked at the timestamps. Code pushed: 2:11am Beijing time Chen's email: 6:23am Guo's reply: 9:47am By the time Guo woke up, the deal was already decided Can you build this? Yes. The code is public But Guo pushed it at 2am thinking it was a student project Chen saw it at 3am and knew it wasn't. China processes 140 trillion AI tokens daily Claude Code generates $2.5 billion in revenue One student went to sleep not knowing he had either The question that keeps me up at night: how many student projects are one GitHub push away from $4.2 million?

• 
  RΛZ13L 🌒 (@Xubu_Trad) reported 51 minutes ago

  Peer review of the latest gilga GitHub updates. 👇 More commits. More files changed. More technical language. But the core issue remains the same. He said the trustless fixes were “actually pretty easy” and told us to “check back tomorrow or later tonight.” It is now the third day past that promise, and the deployed testnet contracts we checked still returned LIVE_OWNER across all 12 queried addresses. In a serious engineering environment, you do not get credit for burying a missed security promise under more activity. You either prove the system is trustless on-chain, or you admit it is not there yet. Right now, the repo is moving. The proof is not. #CAW

• 
  Emrakul (@TheEmrakul) reported 51 minutes ago

  @skuggrev what happened? harrier, kestrel and your account disappeared from github. have you taken them down?

• 
  tyler (@leothrix) reported 52 minutes ago

  my boy is a huge net benefit for so many parts of the Linux ecosystem as the Niri project fixes so many upstream problems to Make It All Work toss him a GitHub sponsorship; he does it all while at uni

• 
  Vince 🐦‍ (@odtvince) reported 52 minutes ago

  @sethrose @GitHubCopilot @github "real advantages with GitHub integration.” Really? Maybe it’s a skills issue—I’m more used to CC and Codex—but I was genuinely surprised this morning: a Copilot Pro Agent Session started reviewing a PR… then couldn’t post the review. “I can’t post it directly from here” it said.

• 
  dodothebird (@dodothebird) reported 53 minutes ago

  - All my projects live in a monorepo. Maybe the workspace solution also works, but I'm going with the monorepo for now. - Using GitHub Pro. I created another account for working with Codex on the monorepo. - All tasks are in different projects on GitHub, mirroring sub-packages in the monorepo. - All PRs are created by Codex on the monorepo. - After PR creation, the agent starts a PR Steward automation to check the state of the PR for code reviews from Codex, CI errors, etc. The automation runs until Codex review gives 👍 - After that, the automation stops. - I check the PR myself. If everything is OK, I approve the PR with my own user. I think I'm in a good place now. Things could be better with more cloud-based code review and PR cleaning processes, but I think I can manage with this for my personal work.

• 
  The Horde Project (@hordeproject) reported 54 minutes ago

  You can now login to our wiki and bug tracker using your Github Account to avoid those inconvenient CAPTCHAs which keep the annoying bots out. At least some of them.

• 
  Ronan Berder (@hunvreus) reported 58 minutes ago

  @badlogicgames What about greenfield work, or new features. I'm assuming you don't do that off of GitHub issues. Just talk back and forth with the AI to build a plan in a markdown file and then pull the trigger once aligned?

• 
  Lower Engineer (@LowerEngineerIt) reported 59 minutes ago

  @steipete github issue triage was a full-time job at most companies 18 months ago. now it's a cron job. the dev department is becoming ops for parallel agents