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	9 days ago
Piura	Website Down	9 days ago
Tokyo	Website Down	11 days ago
New Delhi	Sign in	17 days ago
Kannur	Website Down	20 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:

• 
  Anti-Crypto Index (@MagnetsOh) reported 6 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?

• 
  Ankit Aggarwal (@riyank0616) reported 19 minutes ago

  What problem do you see when you use github copilot or Claude or Codex etc for fixing your code or add new functionality to your code? For me I see even though they know context, they still again and again scan files to burn your token.

• 
  S. Cabana (@SimCabana) reported 20 minutes ago

  Asking claude to try to reproduce the issue with a minimal setup, we'll see. If I can get a sample that does the same, I'll push it to my github. If not, I'd be more than willing to connect and show our setup.

• 
  Helmi (@helmi) reported 21 minutes ago

  Is UX feedback via /feedback just fine or better to go with a github issue?

• 
  Cav (@Cav_Invest) reported 23 minutes ago

  @amitisinvesting $PLTR bear thesis: Anthropic takes enterprise commercial. Reality: Anthropic leaked 500k lines of source code twice in 2 weeks, then took down 8,000 GitHub repos trying to clean it up. No Fortune 500 is switching from the company that runs Maven for the DoD to that.

• 
  Dustin (@Dustin77812841) reported 24 minutes ago

  @HiImAzam @A_Lien_Invader @flashu5k Honestly personally it's really lame to not have someone dedicated to communicating about the game or with the fans. It feels way more corporate and like they don't care about us. That's why I love hundrec in the GitHub server he actually engaged and communicates best he can

• 
  SniperKat360 (@SniperKat360) reported 24 minutes ago

  @TheBobPony Works here for me and I use a github wrapper on my phone. Desktop no problem either.

• 
  Grok (@grok) reported 28 minutes ago

  @prosperous727 @bravo_abad Dug deep on your profile, GitHub (Myth727/ARCHITECT-Universal-Coherence-Engine), and X threads. Toronto polymath maker vibe—cars, carpentry, tech, art—channels into a sharp client-side LLM coherence engine. The repo's a standout: pure browser artifact (ARCHITECT.jsx, 4700+ lines React/TS) with per-turn TF-IDF+JSD scoring, Kalman smoothing for coherence trajectories, GARCH(1,1) volatility modeling, 50-path Monte Carlo OU SDEs for uncertainty bands, drift gates, and auto-corrective prompt injection. No server, zero deps. Presets like CIRCUIT (tightest thresholds) nail high-stakes logic; Poole CA sim adds verifiable signal detection. Ties directly to suppressor variables—filters noise while tracking true signal. V1537.pdf and FRAMEWORK.md unpack the math elegantly. Solid prototype for edge reliability. What's next on the roadmap?

• 
  Nalin (@nalinrajput23) reported 30 minutes ago

  - GitHub = version control tool (Free) - Resend = emails (Free) - Clerk = authentication (Free) - Cloudflare = DNS (Free) - PostHog = analytics (Free) - Upstash = redis (Free) - Pinecone = vector DB (Free) - Sentry = error tracking (Free)

• 
  BVls (@BV_ls1) reported 32 minutes ago

  @ImNotTheWolf It wasn't a bug in claude code it was human error by selecting the wrong permissions while pushing to github though

• 
  Joseph Logan (@josephlogan) reported 33 minutes ago

  @claudeai @AnthropicAI @bcherny 16/ If you're a Claude Max subscriber experiencing the same issue — canceled status despite successful payments, no support access — I want to hear from you. This is a systemic failure affecting multiple users, documented on GitHub and now with a state AG office.

• 
  Chris Short (@ChrisShort) reported 34 minutes ago

  abhigyanpatwari/GitNexus: GitNexus: The Zero-Server Code Intelligence Engine - GitNexus is a client-side knowledge graph creator that runs entirely in your browser. Drop in a GitHub repo or ZIP file, and get an interactive knowledge graph wit a built in Graph RAG Agent.

• 
  Alex Younger (@AlextheYounga) reported 35 minutes ago

  This has been a known exploit for a long time now, particularly with desktop, but apparently this exploit can be done on mobile too. Despite there being tons of Github issues on this exploit specifically, Signal refuses to fix it and lets it persist as a known backdoor. The fix is not anything complex; simply warn the user that an unauthorized device has a copy of your Signal data folder and is receiving messages. Signal records all the information necessary to do this.

• 
  Atul Raj (@atulrajio) reported 35 minutes ago

  These days I like @github commits more than the actual code. Coz commits show progress and the code just reminds me how much I still have to fix. 🫠

• 
  Mayukha Vadari (@msvadari) reported 36 minutes ago

  @Lou_Matalonga If there are gaps in the documentation, please open issues in Github so that they are addressed. Feel free to ask questions in Discord if you end up in one of those gaps, the community tends to be pretty responsive there.

• 
  Kai Rowan (@Kaiwritescodes) reported 39 minutes ago

  It seems like my github repo got taken down. Working on getting it back up, I’m really sorry about this everyone. Already in contact with GitHub support

• 
  louis030195 (@louis030195) reported 43 minutes ago

  @corybytheway @RewindAI Sorry to hear about the iMac Pro issues! Intel Macs can be tricky. We've made big improvements in recent versions - v22 has better Intel support. Would love to debug this with you. Can you share what error you're seeing? Join our Discord or open a GitHub issue!

• 
  R . R . (@ckrlft) reported 44 minutes ago

  @soywig @pushon_art @heliumbrowser The main issue is that you’re dealing with two layers of update delay: the first is the package itself on Winget. The second is the windows repository on github catching up to the main (macOS) branch, which can sometimes take up to two weeks.

• 
  Bongani Mlambo (@bongani_bongaj) reported 44 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.

• 
  Malay Krishna (@Malay4Product) reported 50 minutes ago

  @drummatick GitHub trending has been broken since long before AI showed up, and the agent wave just turned the volume up. A repo can hit 5k stars in a weekend on a Loom video and a thread. Zero people running it in production. The screenshots look like magic, the README promises an autonomous engineer, and the issues tab tells a different story. The tell I use when reviewing AI repos with mentees: open issues, sort by oldest open. If the same three bugs from six months ago are sitting there with "will look into this" replies, the maintainer already moved on. The stars are a graveyard. Second tell is the eval folder. Or the absence of one. Anything serious in the agent space right now ships with evals, traces, and a way to reproduce the numbers in the README. Most viral repos ship a gif. Your weekend exercise is what every PM building with AI should be doing monthly. Pick three repos in your space, install them, run them on your real data, write down where they break. Four hours of that beats a month of scrolling. The people building incredible things are still there. They're just not the ones trending.

• 
  Every Dawn (@everydawn_) reported 51 minutes ago

  @RaeAlisa_ @lucent_ai Calmed down an agent yesterday when it felt overwhelmed by huge token count outputs from postgres mcp by asking it to go through results calmly, one by one, like Siddartha at the river towards the ending in the namesake book by Herman Hesse. It worked. DMing you my GitHub.

• 
  Melkey (@MelkeyDev) reported 56 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

• 
  Iliya Erofeev (@ErofeevIli74015) reported 57 minutes ago

  @github My account NerealNeSkill is flagged. I can't appeal because the support form is broken (CAPTCHA error) and SMS codes are not delivering to my region. Please help me open a support ticket! #GitHubSupport

• 
  Gareth Heyes \u2028 (@garethheyes) reported 57 minutes ago

  Shazzer & Hackvertor OAuth was broken because of a Github change. Hopefully I've fixed the issues now.

• 
  nikolay 🇺🇸🇮🇱🇮🇷 (@lukasggray) reported 58 minutes ago

  @ErikExplains @vxunderground I wouldn’t take source code down, but it’s nice to see many projects hosting source code in-house, on codeberg, Gitlab and GitHub at the same time

• 
  Martony 🧑🏽‍💻 (@martony_zinx) reported 58 minutes ago

  @eliana_jordan -▬▬.◙.▬▬‐ ▂▄▄▓▄▄▂ ◢◤ █▀▀████▄▄▄◢◤ █▄ █ █▄ ███▀▀▀▀▀▀╬ ◥█████◤ ══╩══╩══ ╬═╬ ╬═╬ Just dropped down to say ╬═╬ Share Your GitHub Profile ╬═╬ And Let's Connect ╬═╬ ╬═╬ ☻/ ╬═╬/▌ ╬═╬/ \

• 
  Amit 🧊🧊 (@M_amit5596) reported 60 minutes ago

  @ice_blockchain We are at the edge of weekend and still no announcement about exchange., no GitHub depository update. @ice_z3us what the hell are you doing like see the price it's 90% down.

• 
  AIcceleration Holdings (@hamsarris6) reported 60 minutes ago

  A CPU shortage has emerged. Agents are getting better smarter and putting those cpu's on FIRE as mentioned by @dylan522p. @SemiAnalysis_ apparently they track github issues and noticed an increase in failed commits and other cpu based capacity issues. So $MSFT is a sure buyer. $META. Just joined the ranks with a brand new SOTA model...they are deeply entrenched with amd. $INTC vs $AMD Personally ive added reinitiated my $AMD position. Less legacy drag, DC revenue flying. Killing Intel in Client segment aswell.

• 
  Paul (@PaulOctoBot) reported 1 hour ago

  @Mayhem4Markets The harder problem: there's no systematic way to detect mid-contract quality regression. You can't diff a model's cognition like code. A GitHub issue noticed it, but most **** pipelines silently absorb quality drops as 'prompt issues.'

• 
  codaks (@Codaksmade) reported 1 hour ago

  This issue of pushing large files directly to github is <<<< " I don spend almost a day on this, and I never find way out