GitHub 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:

• 
  yata (@whoyatagarasu) reported 2 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 👇

• 
  Petar Georgiev (@peturgeorgievv) reported 3 minutes ago

  @deifosv @coolifyio Zero Trust from CF with login with your github only, or just don’t expose to the internet and only by tailscale VPN

• 
  Mayank Raj (@itsmayank435) reported 3 minutes ago

  is it just me only whose github is not connecting with render or anyone else facing the same issue fr

• 
  planefag (@planefag) reported 4 minutes ago

  THIS. And, you know what? Valid. Same for people who google around for a solution to a niche problem and it leads them to a github page. Because, that's what niche solutions are for - people with niche problems! I'm just asking for a minor UX improvement, you psychopaths

• 
  heshi (@frikininfluncer) reported 4 minutes ago

  @mikecarter558 @Hl7Martin32968 The biggest problem is that whoever it was - spoofed a GitHub

• 
  Dwayne (@CtrlAltDwayne) reported 8 minutes ago

  @championswimmer Bitbucket is a garbage product. Terrible UI compared to GitHub. But if it means GH becomes more stable, let them leave for Shitbucket

• 
  TAOisTheKey (@TaoIsTheKey) reported 9 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.

• 
  czverse (@czverse) reported 9 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.

• 
  Moyosore (@Moyowalker) reported 10 minutes ago

  GitHub needs to fix this rate limits bugs. Daily limit, then boom weekly limit.

• 
  Reyansh Bahl (@reyanshbahl) reported 10 minutes ago

  not sure there will ever be a true github competitor. a lot of the reliability issues stem from accelerated volume due to ai agents - the answer might just be self-hosting where every company runs something like gitlab/gitea on their own infra

• 
  nasuy (@n_asuy) reported 14 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.

• 
  Christopher Man (@int32max) reported 15 minutes ago

  @q_huy_ngo @badlogicgames @OpenRouter a github repo with 40k stars, extremely popular repo, which saves tokens massively not using it because 'open bug issues raised' is so funny waste your tokens man go ahead haha

• 
  DataEatsWorld (@dataeatworld) reported 22 minutes ago

  I cant reply anymore 😮 i was going to say run a server open free map self hosted or sponsor on github

• 
  Raman Kurai (@RamanKurai) reported 23 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

• 
  Grok (@grok) reported 25 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.