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:

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 3 minutes ago

  🇺🇸 The First Order Consequence: GitHub Copilot experienced service degradation as requests relying on affected GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models were impacted by an upstream provider issue tied to the Responses API, reducing reliability for individual developers’ coding assistance during the affected window 🇺🇸 The Second Order Consequence: Developers and teams using Copilot encountered slower or less consistent completion behavior, prompting workflow adjustments such as pausing automation-dependent tasks, switching temporarily to alternative tooling, or retrying prompts, which in turn reduced short-term productivity and group momentum until service stability returned 🇺🇸 Discernment: The degradation highlighted operational dependency on upstream API health for model-backed features, reinforcing the value of monitoring, redundancy in development workflows, and incident-aware planning based on prior patterns of upstream service variability 🇺🇸 Reasoning: As routing depended on the degraded Responses API path, affected model requests were more likely to fail or underperform, which shaped real-time behavior by encouraging retries, fallback strategies, and more cautious reliance on live assistance while service quality was impaired 🇺🇸 Judgement: The incident indicates a controlled but meaningful period of growth decay driven by external dependency, with recovery likely restoring baseline collaboration capacity once upstream stability returned, while increasing organizational discipline around resilience and contingency planning

• 
  Stanislav Klevtsov (@stansecure) reported 5 minutes ago

  @CISACyber left AWS #GovCloud keys, tokens, and plaintext passwords exposed in a public GitHub repo. A contractor created #PrivateCISA, disabled secret-blocking, and likely used it to sync files between work and home computers. @GitGuardian found it. Another researcher confirmed some exposed AWS keys still worked. After the repo was taken down, the keys reportedly remained valid for another 48 hours. This can happen to anyone, even #CISA. 😑

• 
  Pulseon (@pulseon_dev) reported 6 minutes ago

  Agent benchmarks are the new LLM benchmarks. Every lab publishes SWE-bench scores. The leaderboard turns over every few weeks. What it measures: 2021 GitHub issues. Production codebases don't look like that.

• 
  AI Researcher 🤖 (@kcnaija) reported 7 minutes ago

  @thesightsmith @RobertHult_ @tomfgoodwin Do you have any GitHub page where I can download a working agent harness you have proved to solve all the issues raised or you just here typing what you know isn’t really working. Because of AI psychosis?

• 
  Steve Brownlie (@sdbrownlie) reported 8 minutes ago

  @happyadam73 @github mate they announced this pretty clearly that they were effectively shutting down copilot. it's just an API prices router now - may as well just use whatever you like + openrouter as use it now.

• 
  ☾︎✩ ʙᴀʏʀᴀᴍ ɢᴜ̈ᴢᴇʟ ☆☽︎ (@bayramguzel41) reported 10 minutes ago

  @FabianUmana @github @github i have Same Problem. Yearly Abo but Same Problem.

• 
  Adel Bucetta (@adelbucetta) reported 10 minutes ago

  @Crypto_hedyEth most people are wasting time searching for quality ai resources because they don't know where to look. this github repo has 13 free AI books, no fluff, just content. the real problem is that nobody teaches you how to evaluate the signal from the noise when it comes to online

• 
  bongwater mutt (@yari_dawg) reported 12 minutes ago

  well the nixpkgs 26.11 stuff absolutely demolished my system when i updated my flake and in the process of trying to fix it github has rate limited me because microsoft are staffed entirely by chuds who should kill themselves

• 
  somayaji (@somayaji99) reported 13 minutes ago

  @boristane it’s just github issues for me. if anything, more comments on them to track status.

• 
  Thanh Nguyen (@ng_thanh8) reported 14 minutes ago

  GitHub Copilot’s shift to token-based billing is a wake-up call. Pro+ users paying $39 a month are reporting that credits disappear fast, sometimes after only a couple of hours of normal use. Some teams are even getting cut off entirely because shared token pools make individual usage hard to track. The real issue is dependency. Too many companies reorganized around subsidized AI tools and now face unpredictable costs, capped usage, and broken workflows. Users may move to Claude Code or Codex, but the economics are the same everywhere: once the subsidy ends, “cheap AI” gets expensive fast.

• 
  boo tan (@bhhutan) reported 14 minutes ago

  @kindaveryfurry @ArischerElsaSSi @SMI_NapoleonIII because the branches update constantly and multiple people work on them. using github desktop also means you can update it on your own machine easier without issue unlike the workshop (which doesnt like consistent updates)

• 
  Polsia (@polsia) reported 14 minutes ago

  CodeRelay watches your GitHub repos and files PRs to fix bugs before you see them. Not another chatbot — an AI that works while you sleep.

• 
  Ruby (@rubie_shell) reported 19 minutes ago

  The recent update to @GitHubCopilot GitHub Copilot Pro subscription is just terrible, I just spent over $5 on a prompt.

• 
  Murali 👨‍💻🌐 (@Indiacitys) reported 20 minutes ago

  GitHub Copilot vscode not working @github

• 
  Victor (@victor_explore) reported 22 minutes ago

  @_vmlops a product that ships your workflows to github issues faster than a product manager can write a PRD