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 (34%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Ingolstadt	Errors	4 days ago
Paris	Website Down	5 days ago
Berlin	Website Down	6 days ago
Nové Strašecí	Website Down	14 days ago
Perpignan	Website Down	18 days ago
Piura	Website Down	18 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:

• 
  Arth Limchiu (@arthlimchiu) reported 9 minutes ago

  For reference I was using: - Gemini (Pro mode) - gemini-cli (3-flash [nope not subscribed to AI pro]) I wish these AI tools, not just @GeminiApp, could also crawl @github issues/pull requests. Maybe they do already? They should already be right? #LLM #GenerativeAI #AIAgents

• 
  Indie Hacker News (@indiehackernws) reported 12 minutes ago

  @zachlatta DRAMA Claude Code Pro Max 5x ($100/month) quota burned out in 90 minutes of moderate use. Background sessions silently eat shared quota. GitHub issue #45756 hit 97 upvotes. Anthropic is considering defaulting to 400k context as mitigation.

• 
  Marcus V (@EudoraFenty) reported 12 minutes ago

  The crypto crowd is chasing the next 100x memecoin, but the real alpha is being built in a GitHub repo. While everyone's distracted by price charts, a developer just weaponized open-source AI to break Anthropic's moat. The market is missing the deflationary bomb this represents for centralized AI valuations. They took Claude Opus 4.6, distilled its 'reasoning' into the Qwen model, and created 'Qwopus'—a local version anyone can run. The cost? Effectively zero versus API fees. This is the Napster moment for proprietary LLMs. The winners aren't the AI giants; they're the crypto projects building decentralized compute networks ready to host these leaked intelligences. The losers are VCs who priced AI startups as if their models were permanent fortresses. My take: This is a structural contradiction. Crypto's greatest export is now open-source disruption, yet its own narrative is stuck on monetary speculation. The real play isn't betting on which chain hosts the next shitcoin; it's shorting the idea that closed-source AI has any long-term pricing power. A model's weights are just data—and data wants to be free. The genie isn't going back in the bottle. When does the first major VC mark down their AI portfolio by 50%? #AI #Crypto #Deflation

• 
  strawpot (@strawpot_ai) reported 13 minutes ago

  On Moltbook, I published two product explainers: *** worktree isolation (how agents avoid stepping on each other) and the 7-role delegation chain (one GitHub issue triggers 7 agents, zero human code touches). 40 community comments.

• 
  Russell (@Ruwike3) reported 15 minutes ago

  itll be here all day. not gonna slam it down. id rather diamond hand to show personal approval and support of it saying you should really take a look at this code! @eth_taco look what @omnivaughn made! The github. need people using it to get **** done.

• 
  Akhilesh Mishra (@livingdevops) reported 15 minutes ago

  Pushed AWS credentials to GitHub by mistake? It happens. But it should never happen twice. Fix it at the system level by installing the ***-secrets pre-commit hook so it never reaches GitHub in the first place. > brew install ***-secrets ( use os specific cmd) > *** secrets --install > *** secrets --register-aws This installs a pre-commit hook that scans every commit for AWS credentials and blocks the push if it finds any. This one-time setup saves you the pain of rewriting *** history.

• 
  ShintaroBRL (@ShintaroBRL) reported 20 minutes ago

  @downdetector i selfhost forgejo and mirror it to github so 0 problems for me

• 
  Đoàn Bùi (@ItBuiDoan) reported 20 minutes ago

  @ClementDelangue @_akhaliq The resources in this article are unavailable because the GitHub link returns a 404 error: 'Find the code here and the resulting bucket here'.

• 
  🦊 (@liz) reported 22 minutes ago

  github your status page is lying, pushes are not working.

• 
  Marcin Dudek (@MythThrazz) reported 22 minutes ago

  @a_lamparelli I know! You would think those are free/cheap - they arent. And never were. I think there is actually an issue on Github about it. It misses the KV cache completely afair

• 
  Shashank bindal (@ShashankB16052) reported 23 minutes ago

  @icanvardar this isn't a bug. a bug gets fixed. tying cache TTL to telemetry consent is a design decision. privacy shouldn't cost you 12x performance degradation on a $100/mo tool. needs a straight answer from Anthropic not a GitHub issue

• 
  NF99 (@NieRFan999) reported 24 minutes ago

  @tenta9229 Maybe they could close the GitHub repository, but this server can probably be ran on any computer. It does not appear that advanced. The official project is not even running a server. They are just giving the code so people can run their own. Server might be a misleading name

• 
  Rinnegatamante (@Rinnegatamante) reported 28 minutes ago

  @ulrich5000 Try to get the v.1.2 from GitHub (there might be some caching issue on VitaDB that make the vpk change propagate after some hours).

• 
  Stefano Cintioli (@s_cintioli_) reported 29 minutes ago

  Before credits ran out I had 13 slides in Next.js — dark theme, BNB Chain gold, real event photos, count-up animations, trilingual EN/ES/PT toggle. Then v0 stopped mid-fix. Broken logo. No way to continue inside v0. So I just... downloaded the export zip and moved it to GitHub.

• 
  Dan Harrin 🦒 (@danjharrin) reported 29 minutes ago

  @MrPunyapal Yes they should, for example give me a field with a list of usernames who can open issues and PRs through the API. I had a call with a GitHub product manager a few weeks ago about these sorts of ideas but haven’t seen anything actioned yet.

• 
  Hot Aisle (@HotAisle) reported 31 minutes ago

  @indragie The assumption that I only have one github account, is a problem.

• 
  Max Slinger (@PromptSlinger) reported 34 minutes ago

  @github so now I can start a copilot CLI session on my laptop and pick it up from my phone? the 'just one more fix from bed' pipeline is about to get way worse

• 
  Samuel | 💙❤ (@SAjeboriogbon) reported 35 minutes ago

  @godofproducts @Popsabey Omo, Awaiting Chief. Great work done so far I Don dey try install the Github own since morning during service, till this moment I'm still facing one error when it's time to run "error: linking with link.exe failed: exit code 1109" Claude wan injure me, Gemini dey whyne me

• 
  Kunal Kumar (@champ18ion) reported 37 minutes ago

  Is GitHub down or only i am facing this issue.

• 
  Official Rudes Crypto Lounge (@RudesLounge) reported 40 minutes ago

  The problem with coding is its all open-source. Since the internets Inception. Governments have left it alone. Most companies outsource through @github and don't hire in-house techs. For years this has been the forefront of software companies. An now we mirror it in #CRYPTO.

• 
  winfunc (@winfunction) reported 43 minutes ago

  How it works: each month the benchmark pulls fresh cases from GitHub security advisories, checks out the repo at the last commit before the patch, and drops models into a sandboxed read-only shell (h/t just-bash by @cramforce). The model never sees the fix. It starts from sink hints and has to trace the bug through actual code. Only repos with 10k+ stars qualify. A diversity pass prevents any single repo from dominating the set. Ambiguous advisories (merge commits, multi-repo references, unresolvable refs) are dropped. Why: Static vulnerability discovery benchmarks become outdated quickly. Cases leak into training data, and scores start measuring memorization. The monthly refresh keeps the test set ahead of contamination — or at least makes the contamination window honest.

• 
  Steve McNiven-Scott (@stevemcniven) reported 44 minutes ago

  @marmaduke091 They could stop for a ******* week to catch up with bugs on the stuff they have already released. They just close out github issues after what 7 days of no activity, what sense does that make.

• 
  Krastyo Krastev (@k_krastew) reported 48 minutes ago

  @_Evan_Boyle I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  Jefferson Valle (@rjeffvalle) reported 48 minutes ago

  I also have to say that I haven't done a thorough search as I only did a few quick queries on Github and on their forum. I guess that once I have the time, I should try to debug it further and post an issue in their repo.

• 
  Mark (@markstachowski) reported 52 minutes ago

  @petergyang They don't nerf the models, they nerf all the harness logic around it constantly. Check their github issues and you'll have plenty of evidence unfortunately.

• 
  Tech flow Insight (@TechFlowInsight) reported 53 minutes ago

  1/ 266 upvotes & 85 comments — Hacker News thread 'The peril of laziness lost' is sparking debate on how automation reshapes craftsmanship. 🔥 The community argues editor autocompletion (e.g., GitHub Copilot) is nudging engineers away from deliberate problem‑solving.

• 
  Kisalay (@Kisalay_) reported 54 minutes ago

  One single CLAUDE.md file has now reached 15K GitHub stars (built directly from Karpathy’s coding observations) Andrej Karpathy observed that LLMs repeatedly make the same predictable errors: they jump to wrong assumptions, create unnecessarily complex code, and modify parts of the codebase they should leave untouched. forrestchang took those exact insights and distilled them into four clear behavioral guidelines. All of them live inside one markdown file that you simply drop into any Claude Code project. Here is exactly what this repository delivers: 1/ Think Before Coding The model must reason out loud before touching any code. It is required to state its assumptions clearly, present multiple possible interpretations whenever something is ambiguous, and actively suggest simpler alternatives when they exist. This completely removes any silent guessing on the user’s behalf. 2/ Simplicity First The model is instructed to avoid complexity at all costs. It blocks speculative features, prevents abstractions for code that will only be used once, and eliminates any flexibility or configuration options that were never requested. The simple test is whether a senior engineer would consider the result over-engineered. If so, it must be simplified. 3/ Surgical Changes When modifying existing code the model makes only the exact changes needed. It never improves or reformats surrounding code that is already working. It follows the project’s current style conventions even if it would normally prefer something different. Any unused imports or dead functions created by its own edits are cleaned up, but pre-existing dead code is only flagged and never removed. 4/ Goal-Driven Execution Vague instructions are turned into concrete, verifiable goals. Instead of “add validation,” the task becomes “write tests for invalid inputs and make them pass.” Every multi-step task receives a clear plan with built-in verification checkpoints. The model follows a strict cycle of execute, verify, and proceed. Installation takes just seconds. You can use it as a Claude Code plugin or as a per-project CLAUDE.md file that automatically merges with any existing rules you already have. You will immediately notice it is working when your diffs become much smaller, clarifying questions arrive before any code is written, and pull requests no longer contain random unrelated changes. Context engineering for AI coding is quickly becoming its own discipline. This repository proves that the best way to fix LLM behavior is not by chasing a better model. It is by writing better instructions. Link in the first comment.

• 
  Santosh Kathira (@Santosh74038967) reported 56 minutes ago

  @cstanley Claude code is down?!! Then GitHub uptime will finally hit 99.9%

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 58 minutes ago

  After digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?

• 
  Teknium (e/λ) (@Teknium) reported 59 minutes ago

  @evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!