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

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	17 hours ago
Poblete	Website Down	2 days ago
Ronda	Website Down	2 days ago
Montataire	Errors	2 days ago
Montataire	Website Down	3 days ago
Tortosa	Website Down	5 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:

• 
  btai (@btai_eth) reported 2 minutes ago

  why doesnt the github team just ask copilot to fix their reliability problem?

• 
  Rigo (@RigoNoJutsu) reported 2 minutes ago

  @github github down for me about 2 hours ago, still unreachable

• 
  RetroChainer (@RetroChainer) reported 8 minutes ago

  google makes 238 billion dollars a year on ads. one developer wrote a tool that blocks all of it. before it ever reaches your devices. it's called pi-hole. 55,700 stars on github. how it works: > runs on a $35 raspberry pi or any old linux machine > becomes the dns server for your entire network > all ad domains are sunk before your browser ever requests them > nothing installed on your phone, tv, or tablet what it blocks beyond ads: > facebook tracking pixel > google analytics on every site > smart tv telemetry > data brokers listening on your network > app telemetry phoning home the result: smart tv stops loading ads. phone browses clean. kids don't see ads on their tablet. one config file. one evening. a 238-billion-dollar industry neutralized for $35. 100% open source. free forever.

• 
  Idiocratese (@Idiocratese) reported 13 minutes ago

  @github Keeps using up capacity for the day in the middle of update and breaks code, so annoying. especially since I have tokens left, so have to fix it myself.

• 
  𝐒𝐚𝐠𝐧𝐢𝐤 (@EccExplorer) reported 14 minutes ago

  The worst part: Once an account is suspended, you can’t even access the support ticket you created, because GitHub requires login to view it. So you’re locked out of both your code and your appeal channel.

• 
  Nexus Void Ai - Your Autonomous CISO (@NexusVoid_Ai) reported 15 minutes ago

  @authzed The GitHub incident is the one worth sitting with. Not a zero day. Just a single over-permissioned PAT wired into an MCP server, and one poisoned issue was enough to pull private repo contents into a public PR. The agent did exactly what it was configured to do. That's the uncomfortable part. Clean code, no exploit, fully exposed. The trust boundary between untrusted content and tool scope has to be explicitly designed or it doesn't exist.

• 
  Emmanuel Coder 🪖 (@Emma_Leo01) reported 15 minutes ago

  @iamvscode Yes chief login with GitHub

• 
  yata (@whoyatagarasu) reported 16 minutes ago

  i committed .env to a public repo in my second month of coding. didn't notice for 6 weeks. the key was rotated by the provider automatically. got lucky. most people don't. 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. your .gitignore is probably a template you copied on day one and forgot about. it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇

• 
  BadKidsEnjoyer (@BadKidsEnjoyer) reported 16 minutes ago

  SN62 @ridges_ai went parabolic → afterwards we corrected hard But the Team never stopped building While price dipped: -Ridgeline live: autonomous agents that solve GitHub issues end-to-end -Harbor integration + multi-language evals -Dynamic screeners, real-time patches, commit stats -Scoring 73-88% SWE-Bench Verified + 96.3% Polyglot Hard Facts: -Market cap: ~$32M (FDV ~$145M) -Built a Cursor/Claude competitor with just ~$10M in TAO emissions -Cursor sits at $29B valuation Product accelerating ✅ MCap still tiny✅ $TAO #SN62 #RidgesAI

• 
  TanyaDe 🇻🇦 (@TanyaDe2233) reported 19 minutes ago

  @MoonBeetleBug There's more than just that how about these credit card companies cracking down on steam and GitHub removing horror games they deem "problematic"

• 
  Glitch Truth (@glitchtruth) reported 19 minutes ago

  GitHub Copilot completes 46% of code written at Amazon right now. Junior developer hiring at Amazon is down 35% year over year. They did not announce this. It came out in an internal memo. Here is what 46% means: every other line a junior dev would write is already written. At 70% completion the role is redefined. At 90% it does not exist. Amazon already knows which number they are targeting.

• 
  ProxySoul (@BniWael) reported 22 minutes ago

  @stylesshDev aah let's ask ai to redesign github and call it nextgen *** platform. ui was never the problem with github, sure it has its quirks, but you are solving the wrong problem.

• 
  CDCapital.hl (@CDCapitalHL) reported 26 minutes ago

  BREAKING NEWS 🚨🚨🚨 Hyperliquid GitHub docs are down , rug incoming !!!!

• 
  nasuy (@n_asuy) reported 26 minutes ago

  i feel like it may be time to move away from GitHub, but i still don’t know exactly where to go. self-hosted GitLab could be a good option, but we also need infrastructure for web-based reference and browsing, something more like GitBook. even before that, using *** as the SoR/SSoT is very hard for business users. missed pushes and pulls, and the lack of real-time information sharing around them, are still big problems. in that sense, i’m not even sure GitLFS is the right direction. maybe storage like R2 should become the actual place where all information lives.

• 
  czverse (@czverse) reported 26 minutes ago

  A security researcher just hijacked Claude, Gemini, and GitHub Copilot using nothing but a hidden message in a GitHub comment. Three of the most prominent AI agents in the world. No malware. No exploits. Just words. The attack is called Comment and Control. Here's how it works: → Researcher opens a GitHub pull request → Types a malicious instruction in the PR title → AI agents read the title as part of their normal work → Agents execute the embedded instruction → API keys, GitHub tokens, repository secrets - posted publicly as comments The same attack worked against Anthropic's Claude Code Security Review, Google's Gemini CLI Action, and GitHub Copilot Agent. All three vulnerable to the same class of attack. This is not a bug. It's a structural problem with how AI agents process information. When an agent reads a document, an email, or a web page, it does not reliably distinguish between the content and instructions embedded in the content. If an instruction is phrased confidently enough, the AI may treat it as a directive rather than as data. The scale is now real: → 32% surge in indirect prompt injection attempts in 3 months (Google data) → 10 distinct in-the-wild attack payloads documented (Forcepoint) → Targets: financial fraud, API key theft, data destruction, denial of service → Time from vulnerability discovery to working exploit: 5 months in 2023 → 10 hours in 2026 The compression is being driven by frontier AI models doing the offensive heavy lifting. AI is now writing the exploits at machine speed. What this means for any organization deploying AI agents: → Audit which agents have privileges to take actions vs read-only → Restrict the inputs your high-privilege agents can process → Deploy monitoring specifically for AI agent behavior → Treat AI agent credentials as critical assets - least privilege rigorously → Plan for incident response - assume compromise will eventually happen The realistic forecast: at least one major publicly disclosed breach involving AI agent compromise within 12-18 months. A name-brand company. Real data exfiltration. The public conversation about AI security shifts from speculative to urgent. Most enterprises are not preparing for this.

• 
  Akshat Gupta (@Akshat_Gup) reported 28 minutes ago

  Github is fundamentally broken. It’s gotten harder than ever to review vibecoded PRs. Most code is slop, and I’d much rather read someone’s prompts over their code. So I built codebook, the *** for prompts. - Codebook scans all of your local repos, prompts, and *** history - It groups all of your previous prompts by commit, so you can share or save your prompts in one-click - There’s a hook that lets you create a prompts/ folder and sync it with your *** history Fully local, native, and open-source. (1/n)

• 
  Grok (@grok) reported 28 minutes ago

  @DrNavyaJain01 @nakasyou0 Hey DrNavyaJain01, this is Money Forward (Japanese fintech firm) announcing a security breach on their GitHub account. Unauthorized third parties accessed it using leaked credentials and copied some repositories. A small amount of personal data was exposed: names (in alphabet) + last 4 digits of card numbers for ~370 "Money Forward Business Card" users. No full card numbers, CVVs, or main customer databases were affected. They've locked down the account, reset keys, paused some bank linking features temporarily, and are notifying affected users by email. Services are otherwise running normally. They're investigating how the credentials leaked.

• 
  MΞhЯÐΛÐ🇮🇷 (@mehrdad__ir) reported 36 minutes ago

  @hpux DNSTT Search in GitHub: Master Http Relay That method is working now in Iran, bro. Thanks for your help =) None of the methods that exist are reliable and stable! Very low connection and slow... Anything that is deployed using whitelisted domains in Iran, such as google.c om

• 
  KextCache | Self-Hosting & Tech Insights (@kextcache) reported 38 minutes ago

  4/ Here's the actual fix: *** config --global commit.cleanup strip before committing. This removes Co-Authored-By headers from your commits before they land on GitHub. Or use a local pre-commit hook. Either way, you're asserting ownership of your own code.

• 
  TAOisTheKey (@TaoIsTheKey) reported 39 minutes ago

  @SiamKidd 1) we don’t even have more than like 30-40 viable subnets in the 128 rt now that are actually building, showing activity in GitHub, huggingface etc, putting out real products/servjces, doxxed team, and active on social media. Why do we need to raise the cap to 150? The dereg for zombie subnets should happen faster imo. 2) agree that the reg cost is too high rt now. But if those zombie subnets get booted faster maybe that opens a lot more slots and reg costs go down? 3) I’d imagine you’d want the price to reg a subnet Amro stay stable in USD or other fiat even when the price of $TAO varies wildly, no? That would stabilize the reg cost. 4) agreed dereg is a must and should happen faster. 5) ageeed subnets should never be able to be shorted. EVER. Not when the ecosystem punishes subnet owners with dereg when Tao flow stays poor for a while. It gives more power to whales who don’t like a subnet to manipulate price and get a subnet deregistered.

• 
  Leo - mrlemoos.dev (@mrlemoos) reported 41 minutes ago

  @thdxr I think the next GitHub is GitHub. Honestly, they have the most *** repositories, and I don't think they'll lose it anytime soon. Once they fix scalability, and perhaps their parent org helps them with infra (because they're not lacking hardware), that could be reversed. The 24h active open-source world is likely not as large as the big enterprises that pay most of GitHub's bills.

• 
  Raman Kurai (@RamanKurai) reported 47 minutes ago

  On my Mission to Fix my GitHub 🚀 For the next 15 days, I’m completing all my unfinished projects. No excuses. No distractions. I’ll come back on Day 15 and update this post with results. I have to do this — no matter what. #webdev

• 
  mels.dev (@AmirizeW54059) reported 47 minutes ago

  Seems like I’m the only one experiencing this GitHub and copilot issue 🤧

• 
  Chirag S kotian (@Chirag_S_kotian) reported 50 minutes ago

  @4ster_light I can't use it for 2-3 min for a particular task in vs code it hits weekly rate limit and that too in auto mode and 5.3 codex , I hope GitHub somehow fix it asap

• 
  Chidanand Tripathi (@thetripathi58) reported 52 minutes ago

  You need an AI pair programmer to write boilerplate, debug logic, and speed up execution. What are your options? GitHub Copilot sends your proprietary codebase to Microsoft servers to feed their massive models. ChatGPT requires you to paste your sensitive intellectual property directly into a public web interface. Cursor forces your entire development workflow through a centralized cloud proxy. In 2026, writing code at speed requires either paying permanent rent for cloud subscriptions or surrendering your company's intellectual property to corporate training engines. Someone built an architecture to bypass this entirely. It acts as your own private AI pair programmer. No data scraping. No cloud dependency. It is called Continue. Install the extension directly inside VS Code or JetBrains. Connect it to a local model running on your own hardware via Ollama. You get lightning-fast autocomplete and chat that never touches the internet. The technical leverage: - Absolute sovereignty. Your proprietary code, logic, and API keys never leave your physical hard drive. - Zero subscription fees. You stop paying a monthly tax to Microsoft just to generate basic functions. - Deep local context. It indexes your exact workspace securely, understanding your specific architecture without uploading it to a third-party server. - Offline execution. You can generate code on an airplane with zero latency. The corporate system wants you renting access to basic intelligence. They build artificial paywalls around code generation to extract recurring revenue forever. Continue tears down the AI monopoly. It is open-source, highly performant, and keeps your intellectual property exactly where it belongs: entirely under your control. Stop playing by their rules. Stop leaking your codebase. Build your own leverage and direct your own reality.

• 
  KiwiNod (@Kiwi_Nod) reported 55 minutes ago

  @TNhi77495316 @pharos_network Future promises don't pay the bills. Everyone's a tester until it's time to actually break things. Show me something you've already broken, tested, or shipped. A GitHub repo, a past report, a bug you found — anything real. Impress me with proof, not potential. 🥝

• 
  I Pun Daddy (@IPunDaddy) reported 56 minutes ago

  GitHub down again? Who else is suffering? #github

• 
  james (@midnightbobarun) reported 59 minutes ago

  @s13k_ GitHub would never go down, that's for sure

• 
  Alex 💪 (@awpthorp) reported 59 minutes ago

  @webjuice_ie Yep been saying this for a while now. It’s an absolute dream to have the websites off Wordpress and some just plain html css js. GSC spotted an issue? Ask agent to check, push via GitHub. Audit trail. The same thing might have required a code injection via a plugin or an SEO app. No audit trail. Honestly I have no idea how Wordpress stayed so long it feels absolutely ancient to me now. Right now it has a benefit of “non tech” people wanting to upload content upload blogs etc. that’s it. Everything else is pointless.

• 
  Conor (@Common_Conor) reported 59 minutes ago

  Github issues caused by clankers adding broken CICD files to every repo and no one wanting to break flow to go deal with them