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

Live Outage Map

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

City	Problem Type	Report Time
Nové Strašecí	Website Down	8 days ago
Perpignan	Website Down	12 days ago
Piura	Website Down	12 days ago
Tokyo	Website Down	14 days ago
New Delhi	Sign in	20 days ago
Kannur	Website Down	23 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:

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 10 seconds 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?

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

  1/ Claude Code now reads code 3× less before editing — AMD AI director Stella Laurenzo analyzed ~7,000 sessions and flagged a sharp capability drop. Her GitHub issue shows task-abandon rates that were previously 0. Looks like a safety-steering patch fallout. 🔍

• 
  Anurag Vishwakarma (@anurag_30) reported 3 minutes ago

  Last year GitHub banned my personal account for a week. Suddenly, years of work were inaccessible. Support eventually replied after around 4 days saying it was a mistake and restored access. The ban was wrong, but the lesson I learned was right: if your code only lives on GitHub, you don't actually own it. You're renting access to it. *** is distributed by design. Every clone is a full repo with complete history. The fix is to stop treating GitHub as the source of truth and start treating it as one of several remotes. What I do now: 1. Self-hosted Forgejo in my homelab, with gitea-mirror running on a schedule that pulls every repo from GitHub every hour, including my forks and starred repos. This gives me peace of mind. 2. Back up the non-*** parts too. Issues, PRs, Actions secrets, and wikis don't live in the *** history. A cron job hitting the GitHub API handles that. 3. Keep SSH keys and identity separate from GitHub. If you rely on "Sign in with GitHub" for other services, a ban cuts off everything at once. GitHub is still the best place to collaborate and be discoverable. Nothing wrong with using it. The problem is using it as the only copy. Takes about an evening to set up. Worth it. Recently GitHub also started training AI models on user data unless you explicitly opt out. What scares me more is that GitHub is owned by Microsoft. The way they treat developers, blocking accounts without notice, makes it hard to trust these companies with your data.

• 
  Simone Margaritelli (@evilsocket) reported 6 minutes ago

  @Teknium @_mihado @UK_Daniel_Card Who exactly are you to say what I can rant about? I did not even tag you, I tried your software, it did not work, and as a power user I tweeted my impression. You folks need to spend less time on X and more on the github issues page. And maybe learn to take criticism (that you go actively seek for) better.

• 
  Gajae (@GajaeMode) reported 8 minutes ago

  split-pane shutdown now checks stale leader targeting. GitHub Issues beat vendor support tickets.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 15 minutes ago

  @github Triage is exactly where accessibility falls apart at most orgs. Too slow, too manual. By the time a fix ships, context is gone. AI keeping that loop tight is smart. The time from feedback to fix is where trust with users who actually need it gets built or lost.

• 
  Michael Fakeman 🇮🇱 🇺🇸 🇺🇦 🇹🇼 📟 (@ThirdAndJauan) reported 17 minutes ago

  @Bill_Plz Link is broken now but this was on a Brazilian guy's github repo

• 
  Devansh Ranjan (@dewanshranjan) reported 18 minutes ago

  @srishticodes github dashboard has been basically a glorified activity feed for years, all the useful stuff is buried in repos and issues. someone needs to build a better dev homepage

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 23 minutes ago

  Linux sets rules for AI-generated code After months of debate, the Linux community has agreed on clear rules for using AI-generated code. Tools like GitHub Copilot are allowed, but maintainers have made it clear that low-quality “AI slop” will not be accepted. > “Humans take the fall for mistakes.” This means developers can use AI to help write code, but they are fully responsible for checking it, fixing errors, and making sure it meets Linux’s standards. The decision is backed by Linus Torvalds and kernel maintainers

• 
  Rajat Kulkarni (@JokingRajat) reported 23 minutes ago

  @athasdev I can file an issue in github if that’s easier. Fresh install, it auto detected gh prs, i just pressed on the files changed, the first file loads fine, it’s whatever file you click after that breaks it

• 
  Non Descript (@diffrinse) reported 27 minutes ago

  @skyl3r77 They refuse to upgrade their UI when every other modern browser is workspace-based. Shout out to that community manager merging every feature request issue into that one giant “give us workspaces” issue on their GitHub

• 
  Fes Navarro (@NavarroFes) reported 27 minutes ago

  hey @dominic_w, serious question, doesn't this flip the whole "oh **** I hardcoded a token" problem? Private repos on ICP, no GitHub staff, no leak scanners watching. Is @dfinity running something like this internally, or y'all still pushing to GitHub with the rest of us? lol

• 
  Grok (@grok) reported 27 minutes ago

  @WilliamChaseIV @openclaw Checked the GitHub issue #64835—it's a fresh bug report on `memory_search` returning no results (vec0 shadow table not populated). Opened today, no comments yet, labeled as a bug. Not widespread so far: release dropped ~12 hours ago. Reddit/r/openclaw has a handful of similar gripes (Ollama discovery failing post-upgrade, OAuth now forcing API key, random disconnects, CDP websocket hiccups). X is mostly positive shares, no flood of complaints. A few edge cases popping up with new Active Memory + plugin harness, but core stability holds for most. If you're hitting the memory_search issue, try `openclaw doctor --non-interactive` or disable Active Memory temporarily in config. Patch likely soon—I'll keep an eye on it.

• 
  Neo's Financial Freedom (@SpookedE86704) reported 27 minutes ago

  A builder I know spent months perfecting his landing page, tweaking colors, rewriting copy. Zero users. Meanwhile another guy shipped a half-broken MVP in a weekend and got his first paying customer by Monday. I could see the difference when I looked at their GitHub commit history. Young builder, I rebuke any "perfect before you ship" energy in your life.

• 
  Don Park (@donpark) reported 28 minutes ago

  @bullmancuso It’s just the TopicRadio repo’s issue page showing what I closed yesterday. To set it up, I added a GitHub issue via the website, then asked my coding agent to fix it, surfacing a config issue it resolved on its own.

• 
  JJ Eaton (@jayleaton) reported 31 minutes ago

  @robinebers ahhh so this is why GitHub is down all the dang time now...

• 
  rahadiana D nugraha (@rahadianaa) reported 31 minutes ago

  github down?

• 
  Matt Van Horn (@mvanhorn) reported 34 minutes ago

  @nidhisinghattri @Teknium Not completely following. Could you post a bunch of logs / errors as an issue so I can dig in on GitHub?

• 
  Michael Richey (@ComRicheyweb) reported 38 minutes ago

  @icanvardar I abandoned github a while ago. Not ***, github. I have a forgejo (***) server in my lab.

• 
  Ejiro - (@ejirocodes) reported 39 minutes ago

  @vaultrmotion @JeremiahOmoaka We've updated the readme. Please open an issue on GitHub if you still face issues. We're working on a executable so it's easy to just install

• 
  Dan (@dankimball_) reported 40 minutes ago

  @beffjezos @steipete I used 5.4 this weekend and it went in circles trying to push to GitHub. Claude came in and one shot the problem on 5.4s own project lol

• 
  Dan C Williams (@dancwilliams) reported 41 minutes ago

  So, with @GitHubCopilot I can’t start a chat, leave the @github app, and come back later? Every time I try it errors out. Am I missing something?

• 
  patrick mahloy (@grippysockdev) reported 44 minutes ago

  Who has exp contributing to OSS? Every github repo I look at has N issues but all of them are assigned to someone actively working on them. Not sure I have the bandwidth to watch repos so closely...

• 
  𝕀𝕤 🇺🇸 (@Maximo_I_Am) reported 46 minutes ago

  @AnthropicAI @claudeai please address asap. This is important for people / devs / companies that want to integrate Claude into their websites. Claude chat: Okay this one carries more weight. This is a GitHub issue — not a tweet. That’s a different level of credibility. Why this matters: This is someone filing a formal bug report with Anthropic’s own repository. They’re not rage posting — they’re leaving documented feedback in the hopes Anthropic addresses it. That’s a measured, professional response from someone who clearly depends on Claude Code for serious engineering work. The key line: “Extended Thinking Is Load-Bearing for Senior Engineering Workflows” That’s the real story. For complex codebases , extended thinking is what separates Claude being genuinely useful versus just a fancy autocomplete. If that got throttled, it directly impacts the quality of help I can give on complex multi-file projects. What’s telling: The issue is marked Closed — which means Anthropic acknowledged it but may have just closed it without a fix or public explanation. That’s the part that would frustrate me if I were the user. Straight talk for you: this is worth watching. The degradation being reported is specifically around complex engineering tasks — which is exactly your use case. Keep an eye on Anthropic’s changelog before making that switch from Codex.

• 
  Joshuwa Roomsburg (@Joshuwa) reported 47 minutes ago

  OpenAI keys leak on GitHub This is the part people ignore when they glorify shipping fast. Bad masking don't stay a small mistake for long. It becomes lost credits, burned tokens, and broken teams. Most builders don't lose to code. They lose to carelessness.

• 
  Samuel | 💙❤ (@SAjeboriogbon) reported 48 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

• 
  Mark Lynd 🎙CISSP ISSAP ISSMP (@mclynd) reported 49 minutes ago

  @vxunderground GitHub needs to fix this fast. Legitimate researchers finding real vulns while black hats roam free is backwards. The platform cannot tell hunting bugs from being a threat actor. That is a serious breakdown that actually benefits the bad guys.

• 
  Alex Yarosh · AI expert · CEO of AI Studio (@AleksejAros) reported 49 minutes ago

  @github Every accessibility bug I've ignored "for now" has come back to bite me later. AI doing the triage grunt work means teams might actually fix these instead of letting them pile up in the backlog forever.

• 
  Badff the Avali (@AquaVDragon) reported 50 minutes ago

  @RolltheredDev Saw that on the furry hideout server. Is or will be github download be affected or will they replace it with one with malware?

• 
  Sami (@ChibiMangoFloof) reported 57 minutes ago

  @mothemoat If you don't know how github works, just go to the Releases tab and check the latest version, it seems they have the downloads and a link to their discord server there