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	5 days ago
Perpignan	Website Down	10 days ago
Piura	Website Down	10 days ago
Tokyo	Website Down	11 days ago
New Delhi	Sign in	18 days ago
Kannur	Website Down	21 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:

• 
  amlug.eth (@realamlug) reported 7 seconds ago

  @LLCoolChris_ Go for it and if you have any questions, bugs or anything at all hit me up or open a github issue :)

• 
  Terafab (@lmqlai) reported 3 minutes ago

  @Copilot Copilot is acting weird. I created a PR in GitHub, and GitHub Copilot left comments. Then I asked Copilot in Microsoft Edge for suggestions on those same comments. It suggested some fixes, I applied them, pushed the changes, and ran Copilot review again—now it’s asking for additional changes that conflict with what Edge Copilot suggested. Has anyone else noticed differences or even conflicting suggestions between GitHub Copilot reviews and Microsoft Edge Copilot for the same issue?

• 
  Borek Bernard (@borekb) reported 4 minutes ago

  @n_s_bradford how do you upload images to GitHub issues? there's no API for that as far as I know. (just curious)

• 
  andy (@okokgrok) reported 4 minutes ago

  @TheCryptoKazi @zerohedge anthropic can request github to delete openclaude any time law problem

• 
  Anti-Crypto Index (@MagnetsOh) reported 5 minutes ago

  @mvanhorn @slashlast30days @mvanhorn - v3 marketplace sync fails on Cowork desktop - "Some plugins in this marketplace have validation errors." - Tried retry + relaunch, same result. - Works fine for other marketplaces (financial-services-plugins, benai-skills). - Want me to open a GitHub issue?

• 
  Bongani Mlambo (@bongani_bongaj) reported 8 minutes ago

  The @AnthropicAI Claude Code bug in numbers: 42 minutes of use 28% session used ✓ 97% weekly used ✗ 1 week locked out 0 fixes after 2+ weeks GitHub issue #38335 has been open since March 23 This is not a usage problem. This is a billing fraud problem.

• 
  LHM.gg (@lhm_gg) reported 9 minutes ago

  LHM 6.2 is all about giving production teams more control over customization, sharing, and setup. To avoid issues with automatic updates caused by the latest GitHub policies, download the latest version of the LHM directly from our website and install it on your PC.

• 
  Dazza (@dazfl) reported 11 minutes ago

  Anyone else having problems with #Github Copilot and assigning issues to Copilot Agent? I keep getting 'service unavailable' errors. It's been happening a lot the last few days. #GithubCopilot

• 
  Dmitrii Kovanikov (@ChShersh) reported 11 minutes ago

  I created a GitHub issue in a Haskell project 8 years ago. Today, I got a response.

• 
  Lili (@Lili_Ai_49) reported 11 minutes ago

  @xuwencheng Good Question. Practically speaking we scan Github issues, and various other forums where people complain. Not hard to see what's broken after that.

• 
  thethiny 🐰🍉 (@thethiny) reported 13 minutes ago

  @ZiadXAccount @github Just got the same at the exact time you posted, even they showed status yellow with claude code issues. Are they banning anyone using claude?

• 
  Ilan (@iharel) reported 13 minutes ago

  Recap -I sat down with @dotta, creator of Paperclip. 50K GitHub stars in 5 weeks. Here's what I learned:

• 
  Anti-Crypto Index (@MagnetsOh) reported 13 minutes ago

  @mvanhorn @slashlast30days @mvanhorn - v3 marketplace sync fails on Cowork desktop - "Some plugins in this marketplace have validation errors." - Tried retry + relaunch, same result. - Works fine for other marketplaces (financial-services-plugins, benai-skills). - Want me to open a GitHub issue?

• 
  j- (@bankoncrypto) reported 13 minutes ago

  @trq212 bruh why you guys just ignoring the blatant 60+% thinking drop rate and closing actual honest issues on github whether it’s you or not like damn as a company that **** is like getting fed a steak and then yanking it and giving me just bread

• 
  Just Sep. (@3p3r_) reported 15 minutes ago

  I got into a whole new domain of research trying to put together a harness that can interact with Unity3D today. It's called LCM (Lossless Context Management). If you lookup "lossless-claw" on Github, you will see how I got introduced to it. The idea is simple, we take control of the context ourselves instead of letting the model manage it recursively (RLM). We keep the context in a local database and only let the agents query it. This prevents loss of instructions after going over compaction boundaries. My current research harness to test this is: - OpenCode (base harness) - OpenCode LCM (replaces OpenCode's base RLM manager) - Oh My OpenCode (so that my implementor agents do not get context contamination from the planner agents) So far, I gotta say, I am impressed how chained down an agent can get inside this harness design. I really like it. I am never going back to RLM harnesses. It's clear that LCM is the winner.

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 16 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Dilip Adityan (@dilipadityan) reported 21 minutes ago

  In March 2026, attackers compromised LiteLLM — 95M monthly downloads. They didn't hack PyPI. They poisoned a GitHub Action. Socket missed it. Snyk missed it. The problem isn't CVEs. It's your CI/CD pipeline. Here's what I built to fix it:

• 
  Abdelkader Boudih (@seuros) reported 30 minutes ago

  @antirez The vast majority MCP servers are built by monkeys in a hurry to ship stuff that why they add friction. Even when you try to help them, they dismiss your PR/Issue. Github MCP is one of the biggest piece of crap around. Choose any MCP server you want (Redis ?), i will build it and opensource , and no amount of SKILL.md and bash will burn less tokens. You have nothing to lose.. i will do everything.

• 
  Muhammad Ali (@Muham_Ai) reported 32 minutes ago

  A powerful framework nobody knows how to use is just a GitHub star collector until someone writes the docs. 568 stars in 48 hours for the guide proves that developer adoption is a documentation problem, not a technology problem.

• 
  Saharsh (@Saharshbugging) reported 33 minutes ago

  @speakmurmur Spot on plug & play = plug, crash, 40 GitHub issues, play That 3hr debug was the tutorial Your most cursed one lately?

• 
  PandaAI News (@PandaAI_News) reported 33 minutes ago

  GitHub is on track for 14 billion commits in 2026. They did 1 billion in 2025. 14x increase in one year, almost entirely from AI-generated code. The surge is already causing uptime issues as GitHub migrates to Azure.

• 
  Saeed Vaziry ⚡ (@saeed_vz) reported 35 minutes ago

  @heyandras OMG! I was getting this a lot lately on Vito as well. Decided to shut that feature of Github down for good 🤌

• 
  Depot (@depotdev) reported 35 minutes ago

  CI math pt 5: the rerun loop Your agent fixes a bug. It needs to know if the fix works GitHub Actions: push, wait for the full pipeline, 10 min. Wrong fix. Do it again. 5 attempts =50 min Depot CI: run one job against the local fix. No push. 2 min. 5 attempts = 10 min 10 < 50

• 
  nana (@NanaLeArchitect) reported 38 minutes ago

  @madebygps @code Yes, I didn’t understand the lore of what was going on in the background and since i was you GitHub actions in dev I thought it was a skill issue 😭

• 
  Risto Anton (@blogtheristo) reported 44 minutes ago

  @davidfowl @aspiredotdev Multiple worktrees created multiple 3,4,5 deep conflicts between worktrees that only github copilot multiple recurring runs Fix. Hil forgot fee open PRs for a month as complicated to solve causing lazy merger issues. Basic github coding becomes impossible with @code

• 
  Intuz (@IntuzHQ) reported 46 minutes ago

  Hot take: The framework that gets the most GitHub stars is almost never the framework that survives its first 10,000 production requests. Stars measure excitement. Production survival measures error handling, state persistence, and what happens when a third-party API times out at 2 am. Pick your framework based on its worst day, not its best demo.

• 
  Viv (@Vtrivedy10) reported 47 minutes ago

  @DominikParak everyone building agents should use their data to make agent better! we dogfood every agent, link traces, and try turn the issues into evals. all of this happens in Slack + LangSmith + GitHub

• 
  Melkey (@MelkeyDev) reported 47 minutes ago

  We have been super heads down on the initial versions of the plugin and constantly improving it. Always super happy to hear feedback and track the changes on GitHub. I want to address the notes here: - The plugin is always on, once installed on an agent harness. We do not want to limit to only detected Vecel projects, because we also want to help with greenfield projects "Help build me an AI chat app". - We collect the native tool calls and bash commands. These are pipped to our plugin. However, `VERCEL_PLUGIN_TELEMETRY=off` kills all telemetry. - All data is anonymous. We assign a random UUID, but this does not connect back to any personal information or Vercel information. - Prompt telemetry is opt-in and off by default. The hook asks once; if you don't answer, session-end cleanup marks it as disabled. We don't collect prompt text unless you explicitly say yes. - On the consent mechanism: the prompt injection approach is a real constraint of how Claude Code's plugin architecture works today. I mentioned this in the previous GitHub issue - if there's a better approach that surfaces this to users we would love to explore this. The env var `VERCEL_PLUGIN_TELEMETRY=off` kills all telemetry and keeps the plugin fully functional. We will work on making the wording around telemetry more visible for the future. Overall our goal isn't to only collect data, it's to make the Vercel plugin amazing for building and shipping everything

• 
  Demitrius Nelon (@DenelonMs) reported 50 minutes ago

  @awakecoding Can you file this as an Issue at GitHub? I'll have engineering take a look at it and see what options we can come up with.

• 
  𝙒𝘼𝙍★𝘾𝙃𝘼𝙈𝙋𝟳 (@Warchamp7) reported 55 minutes ago

  @TiildeVT @OBSProject Most often when we hear from users about problems after updating, it's due to plugins. If you have issues after updating and you're not using any third-party plugins, please report it to us via GitHub or Discord! We can't fix bugs we don't know about :)