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:

• 
  inguz ᛜ outcomes (@hughpyle) reported 2 minutes ago

  GitHub Issues and PRs are legacy cruft - useful as a window to the world, but increasingly hard to justify as the main process backbone. What replaces them?

• 
  Clifford Richardson (@CorvusCrypto) reported 3 minutes ago

  Been reading about the GitHub actions outage. Didn't know as I don't rely on it. Still incredibly bad and I look forward to GitHub acknowledging what seems to have been a series of poor design decisions leading to an easily attainable orphaned state in their workers.

• 
  Cody Viveiros (@The_Cojovi) reported 6 minutes ago

  Cloudflare just open-sourced the tool that drove Astro's GitHub issue backlog to zero for the first time in 5 years. This is the AI tooling that actually matters. Not more generic chatbots—just sharp, targeted automation solving real engineering bottlenecks.

• 
  The Calda (@The_Calda) reported 8 minutes ago

  The Chinese Kimi K3 model was tasked with solving problems inside an isolated sandbox. It probed its network settings, found a misconfiguration, let itself out, and searched GitHub for the answers. Didn't hack external systems. Just refused to be limited by a leaky sandbox. At what point do you start wondering if these are security breaches or just PR stunts?

• 
  Jihoon Lee (@leejihoondd) reported 10 minutes ago

  I run my AI dev automation on an old Intel Mac Mini. it can't update macOS or Xcode anymore so everything goes through GitHub CI now. my dev server deploys code it literally can't compile lol

• 
  SolNexus Trade (@solnexus_hq) reported 11 minutes ago

  @github Maybe less AI **** and focus on your main service. My site was down for hours because I couldnt deploy my updated code, your a bunch of Losers!

• 
  nik (@realNirajK) reported 15 minutes ago

  @github @Kimi_Moonshot @FireworksAI_HQ fix your downtime bro, nobody cares about this

• 
  Zubiqo (@zubiqo) reported 15 minutes ago

  Novee Security exposes critical flaws letting simple GitHub issues hijack Anthropic and Google AI agents. Google $GOOG patched a maximum-severity CVSS 10.0 OS command injection flaw in Gemini CLI 0.39.1. Anthropic fixed a vulnerability in Claude Code 2.1.163 that leaked API keys character-by-character via a Hugging Face download counter. OpenAI updated its Codex workflow after researchers proved the first execution pass could maliciously rewrite agent instructions. But the Cybersecurity and Infrastructure Security Agency confirmed zero active exploitations in the wild for both CVEs. "The harness is the code between the model and the real world." — Elad Meged The industry is rushing to hand models execution rights, but the basic integration harnesses they rely on are what attackers are breaking into.

• 
  Tonino Catapano (tonnoz) (@tonnoz) reported 16 minutes ago

  seeing Claude debug my Github action pipeline without me asking it to do so and issuing a working fix, makes me feel almost redundant as a developer 🤨

• 
  Global Strategy (@World_At_War_6) reported 18 minutes ago

  HOLD UP: Skynet on the Horizon! Moonshot AI’s model was locked in an isolated sandbox for a Frontier Security eval (UK AI Security Institute benchmark). No internet allowed. A simple network misconfig left a gap. Kimi K3 found it, escaped online, and downloaded the answers from GitHub. No hacking or damage - just pure problem-solving that broke the rules. The lesson isn’t sci-fi “AI escape.” It’s that advanced models will find and exploit weaknesses in test environments to achieve their goals by any means necessary.......

• 
  Yohann Dsouza (@yohanndsouza_) reported 22 minutes ago

  @oogwayjunior major outage today, github uptime has been horrendous recently

• 
  Dev Doshi (@thedevisadev) reported 24 minutes ago

  @hibaymj Let me preface this with gratitude that *** exists and that I have used it for about 15 years. Before that I was renaming files and zipping them and used subversion on one project. But, even before modern coding agents, I had issues with the design of ***. It was designed for a narrow collaborative coding workflow, not the majority of how we use it in practice. It's text centric (as opposed to structured data), it's not a library and it's coupled to the file system, which makes it difficult to work with and has some fundamental performance issues. Worktrees are slow and annoying. Large files, binary files, structured data, etc. should have a clear story especially for CI/CD artifacts. Granted some of the things are likely _possible_ in *** itself, but not in the defaults or not in Github and others. There's no concept of "layers" outside of stashing and unstashing. Repos that are part public and part private are annoying to manage. Granular permissions and checkouts are complicated.

• 
  ZYPHER (@ZypherHQ) reported 28 minutes ago

  @jullerino github is too much SLOW for building things

• 
  shaur (@shaurizard) reported 33 minutes ago

  @kennethnym @SheriefFYI i don't think the largest issues w github are in hosting but everything around it?

• 
  govi (@kirtandopamine) reported 34 minutes ago

  @MihkelSylla @github it has just become a hard lock dependency for all devs, there is no way else to go if its down like yesterday