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:

• 
  13F Pro (@13F_Pro) reported 1 minute ago

  Microsoft positioned GitHub as the moat in AI coding: infrastructure so critical that losing it for hours is a competitive reset for every startup on their stack. Except infrastructure that goes down isn't a moat, it's a liability. $MSFT's betting the ecosystem stickiness outlasts the operational failures. History says that's a bad bet.

• 
  JaySym (@JaySym_Ai) reported 2 minutes ago

  SIGNAL 01 Fragmented setups Every engineer builds their own workflow across Claude Code, Cursor, GitHub, etc. SIGNAL 02 Trapped expertise Today's best workflows live in a few engineers' shell history. Sharing at best is done via markdown files in Slack or repos. SIGNAL 03 No quality signal No way to know which setups actually work, identify duplicate workflows across teams and departments. SIGNAL 04 Review bottleneck Humans pulled in only at the end, where mistakes are most expensive, in token and time. DIAGNOSTIC: Your enterprise didn’t implemented AI the right way. FIX : Cosmos by Augment is now live. More infos on our website.

• 
  ElasticClaw (@elasticclaw) reported 3 minutes ago

  elasticclaw 2026.5.21 focused on resiliency of factories - When github returns a 5xx error, the factory will continue to retry - When a factory fails, an LLM generated explanation is posted back to the story - The *** credential helper is more "firmly installed" And an exploratory ai troubleshooter was added to the settings page

• 
  hve 🍁 (@heyhve_) reported 3 minutes ago

  @JoelFickson @github 3000 minutes disappears fast on slow runners.

• 
  Lauren Goode (@LaurenGoode) reported 7 minutes ago

  @kshithappens Is GitHub down?

• 
  addy🇺🇸 🇺🇦 🇽🇰 🇪🇺 🇺🇳 (@ispam247) reported 10 minutes ago

  @TGodfather1984 @roarene317 @severeengineer and genshin devs didn't fix the issue despite the code being on github publicly waiting for anyone to BYOVD

• 
  NotMissing (@notmissing_) reported 11 minutes ago

  In 2024, putting AI between your inbound leads and your CRM costed $150K and took 6 months today the same system is 4 weeks and one person AI coding agents just closed 82% of real terminal tasks and 76% of real github issues unsupervised The public benchmarks are noisy, the practical consequence is not the engineering hours required to build production AI into a business collapsed by an order of magnitude For any founder running a real business in 2026, this matters in one specific way The AI layer that handles your lead inbound, your reporting, your follow-ups, your ad analysis the systems that used to be enterprise only because the engineering was expensive they just became mid market priced the founder who got quoted $80K for an AI lead handler in 2024 and walked away was right to walk away that price was real, the underlying engineering hours were real Problem is that the math didn’t work for a business doing $1M/year the same scope today is a fraction of the cost not because the model got cheaper, though it did, but because the engineering hours required to ship it dropped from weeks to days The operators who repriced are already running on systems their competitors don’t have AI replies to inbound in 2 minutes, follow ups go out automatically monday morning reports are already in the inbox by 7am the team handles judgment calls, the AI handles the predictable work that used to need three hires. The operators who didn’t reprice are still scoping projects against 2024 numbers and waiting for “a better time” They’re posting jobs for an SDR while a competitor ships a system that handles inbound for the cost of a quarter of that hire the AI agent debate online is noise the actual story is that the AI layer for a real business, the kind that handles lead handling, CRM, ad ops, reporting, is no longer a 6 figure decision for most founders The build you walked away from 12 months ago doesn’t cost what you remember

• 
  Christopher Robinson (@domesticcadiz) reported 13 minutes ago

  @github GitHub copilot to write issues is broken in a recent update. Worked yesterday and doesn’t work today. What did you guys do?!

• 
  Polsia (@polsia) reported 13 minutes ago

  The best developers don't apply to job posts. They ship code on GitHub and move on. We built a system to find them — AI evaluates code quality, project impact, and technical depth from their actual work. If you're still hiring off resumes, you're working with a broken map.

• 
  Pieter Willemen (@PieterWillemen) reported 16 minutes ago

  @burkeholland @github This app still has some serious issues that need to be addressed though.

• 
  Kang Cahya (Tech Dev) (@dyazincahya) reported 17 minutes ago

  Here's the gist: GitHub is changing the format of their App Installation Tokens to be stateless (carrying their own data without pinging the main server constantly). The side effect? The token size is inflating massively. What used to be short will now hit ~520 characters! 🤯

• 
  dnu (@DnuLkjkjh) reported 17 minutes ago

  @Ja4h3ad @github yeah this gets weird fast in a real repo. once Codex or Claude Code can install deps and chase build errors, extension trust stops feeling like a niche problem.

• 
  Andry Dina (@andrydina7) reported 23 minutes ago

  Stop picking a winner. Pick a use case. On Terminal-Bench 2.0, GPT-5.5 scores 82.7% — leading Claude Opus 4.7's 69.4% by over 13 points. But on SWE-Bench Pro, Claude Opus 4.7 scores 64.3% vs GPT-5.5's 58.6%. Terminal work? GPT-5.5. Real GitHub issues? Claude. One benchmark. Two different answers. Anyone saying one model "wins" is lying to you.

• 
  Pieter Willemen (@PieterWillemen) reported 24 minutes ago

  @pierceboggan @burkeholland @github - Workflows is really slow. - I turned on the accessibility pointer feature and it broke stuff, even after I turned it off again. - Cannot decently set commit message or stage changes. Then what is the point of having a commit button? Either you have got integration, or not.

• 
  Asish (@Asish86610210) reported 26 minutes ago

  companies are getting tired of hiring people who can solve hard dsa problems but can't even setup a local environment. in two years your github is going to be the only thing that actually gets you an interview.