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:

• 
  Allan Ta (@A11anTa) reported 8 seconds ago

  You wake up to deployed code you never wrote. Here's how to build that. The setup sounds like science fiction until you run it once. An AI agent that takes a GitHub issue, writes the code, runs tests, and pushes to production without touching your keyboard. By morning, your staging environment is live. The mechanism is simpler than most think. You need four moving pieces: 1. A webhook that triggers on issue creation. GitHub fires an event. Your server catches it. 2. Claude API (or your model of choice) connected to a code repository. The LLM reads the issue, your codebase structure, recent commits for context. It generates a feature branch name and implementation. 3. Automated testing. The AI writes code that fails tests it hasn't seen. You run a test suite against its output before anything touches main. This is the gate that prevents disasters. 4. A conditional deployment step. If tests pass and the diff is under a size threshold (I use 500 lines), it auto-commits to a staging branch. You review the morning after, merge to production, or reject it. The non-obvious part nobody mentions: the AI is terrible at context-specific business logic but exceptional at scaffolding, boilerplate, and API integrations. Frame your issues as scaffolding problems, not decision-making problems. "Add pagination to the user endpoint" works. "Decide whether we need caching" fails. I built this for a SaaS backend in October. Over 6 weeks, the agent wrote ~40 features. 34 required zero changes post-review. The other 6 had logic errors (mixing up user IDs in a JOIN, a regex that didn't catch edge cases). None shipped broken because the test suite caught them. The real win isn't sleeping. It's cognitive load. You spend 30 minutes writing crystal-clear issue descriptions, and the system handles the mechanical work. That's leverage. What breaks this: vague requirements, missing test coverage on your main branch, and trying to use it for architectural decisions. An AI can't decide if you need microservices. It can implement a new microservice if you describe the boundary. The deployment risk sits in false confidence. Your team sees merged PRs and assumes they're vetted. They're not.they're just tested. Code review still matters. I route all auto-deployed code through a human sign-off before it hits production, not staging. Catching narratives is literally everything in crypto and AI startups. The narrative here isn't "AI writes your code." It's "How do you stay competitive when shipping velocity 3x'd and you didn't hire three engineers." That's the angle worth selling internally.

• 
  Ryan Bright (@rbright) reported 22 seconds ago

  Rather than just lamenting GitHub being down, what's the move these days? GitHub is entrenched with many third-party tools, but it's become so unreliable that it's starting not to matter. It's easily the weakest link in the development flow these days, so what's the move?

• 
  Ming "Tommy" Tang (@tangming2005) reported 30 seconds ago

  3/ The README lies. You run the install command, dependencies fail. You chase error messages across GitHub issues from 2017.

• 
  Arcadiy Ivanov (@IAmArcIvanov) reported 4 minutes ago

  @githubstatus @github Are you kidding me? $ *** pull error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 fatal: expected 'acknowledgments'

• 
  Florian (@FlorianCaesar) reported 6 minutes ago

  @realamlug @saltyAom Do you even realize how incredibly disrespectful it is to reply to all of this with LLM slop? Same with GitHub issues. And again, half of this reply is slop garbage and incorrect. Incredible. I’m out.

• 
  Incarnas (@_Incarnas_) reported 7 minutes ago

  Shipped an Obsidian plugin that syncs GitHub data into the vault. Smoke tested against real GitHub. Profile sync returning 404s on every repo. Paginated calls worked fine. Issues, PRs, releases, Dependabot alerts. All clean. Just the direct calls failing.

• 
  Incarnas (@_Incarnas_) reported 9 minutes ago

  Shipped an Obsidian plugin that syncs GitHub data into the vault. Smoke tested against real GitHub. Profile sync returning 404s on every repo. Paginated calls worked fine. Issues, PRs, releases, Dependabot alerts. All clean. Just the direct calls failing.

• 
  Vácslav Turing (@TCult777) reported 13 minutes ago

  @neohk852 @peter_szilagyi yep. 30K+ views on Reddit & X just on my case, still nothing from Anthropic. GitHub is still full of issues. No replies on bunch of mails. apparently the only fix is if @bcherny personally DMs you as we can see in comments here. billion dollar company btw.

• 
  The Whizz AI (@TheWhizzAI) reported 14 minutes ago

  🚨BREAKING: OpenAI Assistants API costs money per token. Lang Smith is paid after free tier. Most LLM Ops platforms charge $99+/month. There is a free open-source alternative. 129,000+ stars on GitHub. It is called Dify. You build production AI apps from a visual dashboard. Chatbots. Agents. RAG pipelines. No ML degree required. What you get for $0: Visual workflow builder for AI agents Built-in RAG connect your own documents Prompt management + A/B testing Auto-generated API endpoint Deploy on your own server One engineer. One weekend. One production AI app. No vendor lock-in. Your data stays yours. Self-hosted. Free forever. 100% Open Source.

• 
  Soham Sakaria (@SakariaSoh88674) reported 15 minutes ago

  @shresthkapoor7 Are you sure it's just github not working again?

• 
  WahResume (@WahResume) reported 19 minutes ago

  @d_carter99 @girdley Request denied on source code makes sense-companies lock that down tight in layoffs to stop data leaks. Grab any public GitHub repos or clean code samples you own for your resume instead. Focus on those 4th-round IT wins to show what you bring.

• 
  Giri Kuncoro (@girikuncoro) reported 19 minutes ago

  I learned today: if we emit high cardinality metrics in @EnvoyProxy, it can cause it to deadlock Not the classic deadlock — more of a lock convoy problem, fully reproducible Will file a GitHub issue soon, has anyone else hit this? 👀

• 
  bitzuist (@shaihulud43) reported 20 minutes ago

  @jukan05 yes but googles position is terrible so msft being stronger than google is still a terrible position vis-a-vis claude code/codex/cursor. copilot absolutely sucks, but github still is the main source of truth. they need to find a way to leverage that

• 
  basedcapital (@thebasedcapital) reported 22 minutes ago

  every time i open a github issue for a rust crate the maintainer replies in german and fixes it in 20 minutes. i don't understand either part.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 29 minutes ago

  @FirstSquawk Anysphere passing on Microsoft to stay independent tracks. A Microsoft acquisition would push Cursor into GitHub/Copilot orbit and probably slow their release velocity. The valuation math only works if they keep shipping faster than Copilot, which needs autonomy.