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:

• 
  Peter Steele (@petersteele) reported 45 seconds ago

  @roswaald @github Yeah, its wild with their uptimes and **** lately. I just self host on a server here at home that I can access from anywhere as needed. No point in using them when my home internet, through spectrum of all things, is more reliable in uptime, which is saying something

• 
  boone kathalan (@xEfscarpmint) reported 9 minutes ago

  Product already live: • GitVault deployment system • gitbankbot GitHub app • Terminal CLI • MCP server for Claude / Cursor / Windsurf • Gasless meta transactions • Auto payouts on PR merge This is more infra-focused than meme-focused. @Gitbank_io

• 
  Hannah Genie (@hm_tech_travel) reported 9 minutes ago

  Man down, dnt think npm dependencies are safe anymore. 640 malicious packages scraping GitHub Actions via Bun runtime. Check your runners and rotate tokens.

• 
  luis (@lgaa201) reported 9 minutes ago

  I've switched from Visual Studio Code to @zeddotdev, and I'll also be removing some private GitHub projects. The problem is, I have it connected to Vercel, lol. Now I'm afraid to download my own project, hahaha. 🫪

• 
  tsunami_crypto (@ls_brd) reported 12 minutes ago

  @trikcode really, asking for GitHub sign in and they give u Google and Apple? always the weirdest omission.

• 
  the peanut gallery (@GunnerDad4) reported 13 minutes ago

  @Tablesalt13 Lmao probably Pegasus but hopefully our tech guys won't leave a github full of keys and passwords exposed like the neighbors down south lol

• 
  DukeD | Defi (@DukeD_Defi) reported 16 minutes ago

  reading this @github incident honestly made me pause for a bit. just yesterday I was still using GitHub APIs to build a small tool for my content workflow… and at almost the same time I suddenly received random 2FA codes from both Facebook and X without logging in anywhere. that immediate feeling of “something feels off” kicked in pretty quickly. and honestly, it also reminded me how crypto users basically live in a permanent paranoid state now. GitHub just confirmed a breach where attackers reportedly compromised an employee device through a malicious VS Code extension and gained unauthorized access to internal repositories. the important part here is > this wasn’t some typical smart contract exploit anymore. the real problem sits inside the workflow behind crypto itself: browser extensions,AI copilots,GitHub integrations,cloud sync,Telegram bots,CI/CD pipelines,API keys, automation tools… and this is probably the scarier layer now. the more crypto evolves, the larger the attack surface becomes. especially when so many devs, traders, and teams are starting to depend heavily on AI tools, browser environments, and automated workflows to optimize daily operations. sometimes compromising just one small layer is already enough,because the damage no longer stays inside one account anymore. it can spread into: > wallet infrastructure, > private repositories, > deployment keys, > trading systems, > multisig access, > even internal production environments. and I honestly think this is why many recent drains and compromises started looking “weird”. not because people are stupid or directly leaking seed phrases…but because the entire environment behind users has become dramatically more complex compared to previous cycles. especially in crypto, where: API keys = money, browser sessions = money, wallet access = money. after this incident, I think a lot of teams will probably start auditing their workflows much more seriously. personally, these are some security habits I’ve been trying to maintain quite aggressively lately: - avoiding random VS Code extensions, especially for crypto or GitHub-related workflows. - rotating API keys regularly, especially after using AI/dev tools or cloud integrations. - separating environments entirely: dedicated browsers/machines for crypto & dev work. - prioritizing hardware wallets + air-gapped signing for larger assets. reviewing connected apps across Discord, X, Telegram, WalletConnect frequently... - and honestly… almost always assuming everything can eventually become a target. crypto security is no longer just about don’t leak your seed phrase. it’s becoming a battle to secure the entire environment behind the user. stay safe.

• 
  Jon Snow (@JonSnow81524891) reported 19 minutes ago

  @RealMamaluke @ThomastheC4T @Pirat_Nation 6 years and counting, never had this happen to me. But that's neither here nor there. At least one can submit an issue on their GitHub and get an answer from someone about what happened

• 
  KevRojo 🇩🇴 (@KevRojox) reported 20 minutes ago

  @trikcode What? you gonna add github to login into github? why dont use your github? hahahaha i dont get ittttttttttttt >.<

• 
  Alex Kruse (@alexnkruse) reported 20 minutes ago

  Two days of using @cursor_ai composer 2.5 and I needed to go back to VS Code Github Copilot (don't ask why); it's painful how slow Opus feels.

• 
  Anas Malas (@CapacitAnas) reported 20 minutes ago

  @blind_via @igorbiletski Interesting... It could the amazing reliability of GitHub nowadays. Try a VPN? Maybe the GitHub servers close to you are broken, but the ones near me are working

• 
  NamasteDev by Akshay Saini (@namastedev_) reported 22 minutes ago

  It was spending 3 weekends building projects I was genuinely proud of Your GitHub isn't just version control. It's a living resume Every commit says: I actually sit down and write code Your portfolio says: I can take an idea all the way to production

• 
  J Mania (@JMania402) reported 22 minutes ago

  Private signal catch $GITBANK at 100k -> 2.6M 0xC21dd0eE043930711C2a3e55F39C7d3144d09B07 $GITBANK is getting attention because the narrative is actually very different from most Base/AI projects right now 👀 The idea is simple: turn GitHub into an onchain funding layer for open-source developers. Developers can: lock bounties directly into GitHub issues/PRs auto-pay contributors when code gets merged use AI agents for workflow management fund repositories without middlemen It perfectly fits the current meta: GitHub + AI agents + Base + onchain treasury 🚀 What added even more attention today was Clanker directly replying: “hey can you have your dev dm me?” There’s no official collab yet, but just having Clanker show up was enough to pull a lot of eyes from the Base ecosystem.

• 
  Blake (@BlakeFolgado) reported 23 minutes ago

  @Chris_C_Clerk @clerk found another thing where something preventing switching to phone number/email in authview without a workaround, may have already submitted github issue

• 
  Kshitij Grover (@kshithappens) reported 24 minutes ago

  it's 2026. anthropic is printing money. github is down. installing dependencies is a dice roll. the rocket company is going public. the rocket company is buying the coding company. github is down. there's a thermal event in us-east-1. login with google is unsafe. $100M is not enough in sf anymore. github is down...