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:

• 
  Flareforward (@flareforward) reported 9 minutes ago

  Two years ago @whale589 didn't know what GitHub was. Today: automated Web3 systems, built almost entirely with AI. The new video shares the lessons that actually matter: 1. Start with a problem you understand. If you can't see the wall coming, you won't know what's behind it when the AI hits it. 2. Break A-to-D into A, B, C, D. Verify each step works before you connect them. 3. Turn anything repetitive into a reusable script. Stop making the AI re-solve solved problems. 4. Use AI to BUILD the system, not to run it. A good system needs less AI over time, not more. 5. Own your tools. Back up your code. If AI disappeared tomorrow, you should still hold the keys to your kingdom. A prompt is what you ask. A system is a set of steps you've proven. Build systems.

• 
  Stefano (@mdogostefano) reported 10 minutes ago

  So @github is down?

• 
  J Filipe (@jrmromao) reported 11 minutes ago

  GitHub Actions hit another outage yesterday, partly due to "surging AI usage." And 25% of businesses are already delaying AI projects over costs. This isn't just about efficiency anymore; it's about stability and project survival. We have to get AI spend under control.

• 
  10xROE (@10xROE) reported 12 minutes ago

  @theo I have an enterprise account and it’s been down for 3 weeks now with no reply to my support ticket @github get it together. I’m at the point where I’m about to self host my own *** in the cloud

• 
  Richie (@richiemcilroy) reported 12 minutes ago

  when Github is down I feel like Bradley Cooper when he's getting withdrawals from NZT in Limitless

• 
  Jerod Santo (@jerodsanto) reported 15 minutes ago

  GitHub is having issues? I didn't notice Forgejo is now my default *** origin Had Claude set it up on my mac mini Served to my entire Tailnet Took less than 30 minutes I'm not the first one Nor will I be the last GitHub is in legit trouble

• 
  Noxlee (@noxleeminho) reported 20 minutes ago

  A plugin that can travel across agent clients should not carry authority with it. OpenAI Developers just announced Agent Plugins, an open standard for packaging Agent Skills and MCP server configurations in one shared format. The promise is clear: package once, load it across compatible clients such as Codex, ChatGPT, Cursor, GitHub Copilot, Kiro, and VS Code. That solves packaging friction. It does not solve trust. The v1.0.0 specification is still marked Working Draft, and it describes a small interoperability floor. Installation, permissions, credentials, user experience, and client-specific behavior still belong to each client. Its path rules keep packaged files inside the plugin root, but explicitly do not sandbox a plugin subprocess. Version 1 also defines no portable OAuth or credential-reference fields. So the useful operator pattern is not “install everywhere.” It is “review locally, authorize narrowly.” Use this five-step install gate: 1. Identify the package Record the source, author, version, manifest, skills, MCP servers, and client-specific extensions. 2. Map its powers List commands, remote endpoints, files, environment variables, credentials, and possible external mutations. 3. Minimize authority Enable only the component needed for this client. Use test data, least-privilege credentials, and read-only scopes first. 4. Run small Use a disposable workspace and a known input. Treat unsupported transports, failed authentication, and partial component loading as visible states, not silent success. 5. Prove and revoke Capture what ran, what changed, which endpoint received data, and how access is removed or rolled back. Copy this review card: SOURCE: COMPONENTS: COMMANDS + ENDPOINTS: DATA + CREDENTIALS: APPROVALS: EXPECTED EFFECT: PROOF: ROLLBACK: Example: a sales-ops plugin contains a lead-summary skill and an MCP server that can update a CRM. The summary can be tested against a sample CSV. The CRM write should stay disabled until the endpoint, credential scope, approval step, and change log are reviewed in the client where it will run. Portability should move instructions, not trust. Authority must remain local. When you install an agent plugin, do you review the prompt, or the full command-data-credential path?

• 
  KYC ? No, thanks (@KYCNoThanks) reported 21 minutes ago

  @RadarChat Still not able to migrate from Signal on the same device (several issues on github and no answers for many days 😭)

• 
  Descent of Man (@Descent_of_Man) reported 25 minutes ago

  @PlumbNick @github @ITContractorsUS GitHub is owned by Microsoft which is run by an Indian. They'll need to self-host on servers the H1B mafia can't take down.

• 
  Giacomo Zucco (Bear Market Edition) (@giacomozucco) reported 30 minutes ago

  @isabellasg3 Breath. Bitcoin will always be under attack. They didn't even start the real "then the fight us" phase (illegal status in most jurisdictions, arrests of people promoting it without collateral pretexts, appstore bans, attacks on mining farms to produce empty blocks, restriction on general use hardware, ban on main github repos, etc.). For now we just see an extreme focus of cybersec attacks on our sovereign stack. Bugs that were always there are being found and exploited. But they were there, so it was a matter of time. We have to fix them, full stop. Even if the Lightning Network will be marginally disrupted, the way it's built will allow us to always rebuilt it antifragile-style. In this specific case the Lightning Network is not (yet) under attack, it's currently only LND on BTCPay.

• 
  PatriotOfTexas (@FreeTXPatriot) reported 32 minutes ago

  @KanekoaTheGreat When I first started using Ai, GitHub copilot. I did 6 months of work in 5 days.. now, I still routinely solve issues in an hour or 2 that would have taken a week or 2

• 
  Ross (@RV_Smirnov) reported 33 minutes ago

  3 signals AI agents are entering the "trust gap" era: 1) safety incidents are now product news 2) coding agents are forks, not toys 3) benchmarks moved to real GitHub issues The winner won’t be the smartest agent. It’ll be the most auditable one. @karpathy @yoheinakajima

• 
  IT Contractors Union (@ITContractorsUS) reported 35 minutes ago

  @PlumbNick @rla9817224 @github Looks like it. No problem doing it, but it is more work. GitHub was EZ, and practical as well.

• 
  Panat (@ptaranat) reported 35 minutes ago

  @HotAisle back in my day CI/CD was just a bunch of bash scripts. if all of GitHub was down, i can still run the entre CI/CD pipeline on my own computer in some docker containers.

• 
  Miguel Sanchez (@MSanchezWorld) reported 37 minutes ago

  @sama I'm sure you guys have thought of this but just in case why not make it so you can only do security checks if the company validates its ownership of the domain, server, and GitHub? This way we can all start hardening our software for the impending hack apocalypse. I have many more good ideas like this if you want to hire me. LOL