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:

• 
  J A X 🐬TermMax (@HieuTrinhVn) reported 5 minutes ago

  @levelsio You might try the K3 GitHub issues for community fixes there.

• 
  Tanish (@Tanishrajurs) reported 6 minutes ago

  They've shipped an MCP server any AI agent (Claude Code, Cursor, VS Code) can now search their full paper database, read PDFs, explore GitHub repos. Agents standing on 3M+ papers instead of guessing

• 
  Stefan Theard (@stefantheard) reported 6 minutes ago

  damn you @github you're killing me with this api outage

• 
  ThreatWire (@ThreatWire_) reported 7 minutes ago

  @ajs6888 You’re right. The source is public, but xAI explicitly keeps GitHub Issues and external PRs closed. The goal is transparency, not community-driven development.

• 
  Harman (@itsharmanjot) reported 8 minutes ago

  Claude writes an HTML artifact. Instead of eyeballing it in a chat window, I open it in an actual local review surface, click the exact element that’s wrong, and queue that feedback for the agent to pick up. It’s called Lavish. A local CLI that turns any agent-generated HTML file into an interactive review page, so you’re not scrolling through raw markdown to catch a mistake. → Opens agent-generated HTML in your own browser, click any element or highlight any text, and it captures the precise target, not just “somewhere in this file” → Edit rendered Mermaid diagrams like a whiteboard, then queue that exact change as feedback for the agent → Runs entirely local. No cloud round-trip to view or annotate an artifact, session state stays on your machine under .lavish-axi/ → Ships built-in playbooks for diagrams, tables, comparisons, plans, code diffs, input collection, and slides, so the agent knows how to structure what it’s showing you before it writes the HTML → Session hooks plug directly into Claude Code, Codex, OpenCode, and GitHub Copilot CLI, so it triggers automatically instead of being a separate tool you have to remember to open → Runs a layout audit before it even shows you the artifact, catching overflow, clipped text, and broken elements before you waste time reviewing a broken render No install required, it runs on demand through npx -y lavish-axi. Every AI coding tool generates plans, diagrams, and comparisons buried in chat text you have to parse manually. Lavish turns that output into something you can actually click on and correct. MIT License. Built by Kun Chen.

• 
  Patrick C Toulme (@PatrickToulme) reported 10 minutes ago

  Many people are asking how did Kimi K3 catch up so fast to Western models? Simply, a frontier model really only requires compute, data and people. There is no magic secret. A few answers to this question 1. Kimi with help from the Chinese government has thousands if not tens of thousands of experts (lawyers, scientists, doctors, programmers.. etc.) making RL env data every day. A frontier model is RLed on “tasks”. Each one of these tasks needs to be created by either a human or an LLM. Claude did not wake up one day knowing how to use the Github CLI. He learned how to use the Github CLI in an RL env.  Meta is pursuing this exact same strategy with its Applied AI org and IMO it appears to be working. 2. I have said this before regarding GLM 5.2 - Kimi obviously distilled from GPT 5.5 and Claude Opus. This only eliminated their cold start problem in RL, meaning they skipped say some X number of months in cold start RL. The mass number of RL envs created by their experts is still the most crucial part here, and you cannot attribute Kimi’s success to distillation. Distillation only saved them some time. 3. Agentic coding and frontier LLMs significantly accelerated their research. My hunch is they use illegal proxies to access Claude API and GPT API for their own model development. Claude/GPT most likely wrote all their training code. This release leads to some very interesting questions. What happens now in a world in which an almost Fable class model is open sourced and free on July 27th? My view is intelligence / software will become very soon close to free. Chip makers and inference providers are big winners from Kimi’s success.

• 
  andrew (@Vavassor) reported 21 minutes ago

  @MrZing07 I agree but also I rarely see people actually submit issues to VRM on github. I see same with other software, folks complain privately for years instead of telling creators what they want. So any new effort folks need to trust them to listen, know how to contact, and help improve

• 
  The Ramen Don (@RealRiddimHours) reported 23 minutes ago

  @GregoryGregman @rocksoverrocks @actualinc I guess that's true. I didn't really know what github did 9 months ago but through trial and error with ai assistance I'm able to make stuff now. Self teaching through AI has been doing wonders for me since 2023, its nuts

• 
  mischa_u (@MischaU8) reported 24 minutes ago

  @10_X_eng will do, let me get codex to generate some useful context and I'll raise a github issue.

• 
  regent0x (@regent0x_) reported 25 minutes ago

  Anthropic CEO Dario Amodei on how they use claude internally: claude now writes 90% of their code and handles 77% of real github PRs, up from 5% a year ago a bug broke their whole training cluster, engineers chased it for days, they told claude "just poke around" and it found it in one prompt but the claude on your machine can't do this, out of the box it only reads files and runs terminal commands, no PRs, no database, no slack it's a genius locked in a room with no windows MCP servers are the windows, 4-6 of them in one afternoon turn claude from "writes code when asked" into "reads the failing PR, queries the db, posts the fix in slack" in one prompt most people bolt on 20 broken servers and wonder why claude got dumber the guide below has the exact handful that matter

• 
  Enes Y. (@senesyildizhan) reported 27 minutes ago

  It’s still an alpha release, so if you run into bugs or rough edges, feel free to open an issue on GitHub or send a PR.

• 
  David (@dayonefoundry) reported 28 minutes ago

  This got resolved. An automated system flagged and suspended my account and a human reversed it. The problem wasn't the code repo, it was the automation scripts in github functions. I was scrambling to move all the cron jobs to a VPS while sleep deprived after a 20 flight. All companies mess up so I can't stay mad at Github. But it's also my responsibility as a business owner to prepare for the worst. I setup a 2nd repo on Gitlab. It took 15 min and now all my pushes go update on both. I already setup the redundancies for the cron jobs. I setup all the appropriate CLIs so I can bypass githubs CI quickly if needed. This used to be overkill for a small project but in the age of AI, it takes less than 1 day to setup all these redundancies. It's worth doing.

• 
  Charlie Lamb (@charlietlamb) reported 29 minutes ago

  Genuinely what is the hardest infra problem out there and where does GitHub sit in this list

• 
  Michael Carpenter (@wiggycorp) reported 31 minutes ago

  For real thought I'd see a lot more people talking about GitHub being down. Basically nobody talking about it.

• 
  Rahul Goel (@rahul_nlu) reported 37 minutes ago

  Another day and another GitHub outage..