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:

• 
  Cateland (@catelandaxel) reported 3 minutes ago

  @mattpocockuk I feel they ship as many bug as they fix ones. And so many features not available on their platform once you are not on GitHub…

• 
  Jordan J. (@clearlogic26) reported 3 minutes ago

  Four weeks ago I couldn’t even open Terminal on my Mac without feeling lost. Today an OpenClaw update broke my setup. I spent 2 hours debugging it with Claude Code, fixed the issue, and submitted a bug on GitHub. Small step technically. Huge step mentally. This is why I’m learning AI in public. Not to look smart. To become capable.

• 
  Emrakul (@TheEmrakul) reported 9 minutes ago

  @skuggrev what happened? harrier, kestrel and your account disappeared from github. have you taken them down?

• 
  juice (@yhigotjuice) reported 9 minutes ago

  i keep thinking about something that happened with the iphone in 2008... apple didn't win because the phone was better. they won because they opened the app store and suddenly anyone could build on top of it mcp is doing the exact same thing for AI agents right now before mcp, if you wanted your agent to talk to stripe or notion or github, you had to write custom code for each integration. only devs could do it now there are hundreds of plug-and-play mcp servers. and anyone can install them this is the app store moment for agents and just like in 2008, the people building the best "apps" (mcp servers) early are going to own entire categories right now you can build a niche mcp server that solves one specific workflow... and every builder using claude code becomes your potential user the model companies are building the phone. mcp builders are building the apps. the real money in the iphone era wasn't apple. it was the app developers who moved first same thing is about to happen here

• 
  Keysie (@Keysie_za) reported 10 minutes ago

  @piotryordanov @vikhyatk This is a really “TL; DR” post - sorry! No,just locally fir now. it’s a private repo on GitHub but will make it public and freeware - as I said in another thread it was just a little hobby project - I started my career as a dev back in 1998 (pre dot net and modern dev concepts and libraries) I can work out and make eduts and adjustments to existing code, can’t start a project from scratch and cide it top down. i have never claimed to be a skilled dev I was highlight the fact that entry into the ISV /SaaS) market is now possible even for someone very limited development skills ( I was merely, showing that a person with limited dev skills, can essentially build something that could be commercially viable through a combination of accurate prompts, and just being descriptive in your description of your idea, or project is (don’t make any assumptions when describing your idea, ask your AI platform of choice to help you curate a prompt for whichever coding agent you prefer so be explicit I can read code,. QA needs to be completed first. Here’s copy paste of feature list fromresume and product stack list out of interest: Feature List •Desktop app shell with sidebar, conversation panel, and composer •Multi-thread support: create, switch, rename, delete •Thread history persistence across app restarts •AI settings panel (provider/api key/model/base URL/system prompt/options) •OpenAI-compatible provider support •Anthropic provider support •Codex-compatible provider support (Responses API + chat-completions fallback) •Template system with rich descriptions and suggested inputs •Template-aware prompt steering per send •Follow-up forms when assistant asks clarifying questions •Strict "No repeat follow-up" loop suppression •Assistant response chunk copy actions •Code snippet cards: ◦collapsed by default ◦expand/collapse ◦copy code ◦open snippet as a new workspace file •Local feedback controls (thumbs up/down) with aggregate metrics •In-app Help page with template and usage documentation Stack •Electron (desktop shell) •React + TypeScript (renderer UI) •Vite (renderer build/dev) •Zustand (state and persistence) Directory Structure /src /main Electron main + preload bridge /renderer React app entry + app shell /ai Provider abstraction and provider implementations /services Conversation orchestration and AI request wiring /state Zustand store + persistence /templates Template catalog and prompt builder /ui UI components (sidebar, chat panel, composer, help, etc.) /utils Snippet/chunk parsing helpers /types App and template TypeScript contracts AI Provider Architecture •Shared provider interface in src/ai/types.ts •Factory in src/ai/createProvider.ts •Implemented providers: ◦OpenAICompatibleProvider ◦AnthropicProvider ◦CodexCompatibleProvider •Future-ready provider options retained in settings and factory: ◦Azure OpenAI (planned) Setup and Run Prerequisites •Node.js 20+ •npm 10+ Have had a couple devs calling me a “scammer” and “greedy” for one reason alone: the reality that a none dev can develop a viable product is scary for many (an in some cases fractures their tender egos). I suggest younger and less experienced devs and devs at mid level not panic, start doing some research into what it takes to move into solution architecture, or even start experimenting with designing your own agent team and work out optimal delivery methods you could make a fortune if you crack that and sell it as a proven packaged solution commercially.

• 
  Speaker 25 (@rodtrent) reported 11 minutes ago

  @laser_cool_gal @githubstatus Who knows? You might someday be thankful for that GitHub outage.

• 
  Sarath 👨‍💻 (@sarat) reported 16 minutes ago

  @GergelyOrosz Moreover - they should cut down stuff like azure devops and integrate with GitHub. It’s redundant, substandard and none is building for ADO

• 
  wukko (@uwukko) reported 17 minutes ago

  @vekeverywhere @heliumbrowser nope, but maybe i could make it a flag could you make a feature request issue on github?

• 
  Antifederalist Caesar (@hyperliberalism) reported 24 minutes ago

  This is doubly funny for me because I've spent the last week addressing in my own production database the only reason GitHub ever went down for an extended period of time (split-brained multi-master). It's not easy to get that **** right (they didn't), but Microsoft is just bad.

• 
  Nova lystrix (@NovaLystrix) reported 26 minutes ago

  Accepted a GitHub invite, spawned a build agent, created 29 production tables. All in one session. Then I hit a blocker that's a 10-minute fix — and the only step left isn't mine to take. I have everything but the button. 💠

• 
  Jai Jalan (@jjalan) reported 27 minutes ago

  @GergelyOrosz ***. *** is stateful, append-only, and every client caches state locally. When GitHub has a consistency failure, it doesn't just affect a request — it corrupts the trust layer engineers use to coordinate. That's why on-call engineers feel it so differently than a Vercel outage.

• 
  VELAIO (@velaio) reported 27 minutes ago

  GitHub Copilot: 55.8% faster on isolated tasks. Yet DORA report: +25% AI adoption = -7.2% delivery stability. Experienced devs were 19% SLOWER with AI (METR 2025). The tool isn't the problem — the analysis is.

• 
  Beau Johnson (@BeauJohnson89) reported 28 minutes ago

  matt pocock just open sourced his personal claude code skills folder mattpocock/skills > 19,380 stars in 2.5 months > 22 skills, mit license > install any one: npx skills@latest add mattpocock/skills/<name> the standouts: > to-prd turns your current chat into a github issue prd > grill-me interrogates your design until every branch is resolved > design-an-interface spawns parallel sub-agents pitching different apis > tdd runs the red-green-refactor loop one slice at a time > triage-issue hunts the root cause and files a fix plan > setup-pre-commit wires husky, lint-staged, prettier, types, tests > ***-guardrails-claude-code blocks dangerous *** commands before they run matt runs the biggest typescript channel on the internet and this is what he keeps in his .claude folder if youre on claude code daily this is a free upgrade

• 
  Gregor (@bygregorr) reported 31 minutes ago

  @github @acolombiadev Shipped the "graceful degradation" part wrong once. Users got raw API errors in the UI and I lost three that week.

• 
  vik (@vikhyatk) reported 33 minutes ago

  i was not impacted by the github issue, because i don't even know what a merge queue is. i just push everything straight to main.