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:

• 
  Josewins (@josewinscrypto) reported 6 minutes ago

  @tryhandlepad idea is nice, they login through X, Github o Twitch right? at some points to claim fees they need to create a wallet

• 
  Marcelo Retana (@mretsal) reported 8 minutes ago

  Every time @github goes down they should have a plan to please their users. Give me free credits for actions for example 👍🏼

• 
  Martin Tobias (Pre-Seed VC) (@MartinGTobias) reported 14 minutes ago

  if you know any founders who are winding down, I may have a buyer of their github repos. DMs open.

• 
  Eniola ' Software Engineer 💻 (@eniola_merem) reported 15 minutes ago

  @ekemini58110 Yes, you can. I try not to, but if I notice a spelling error no PC I would edit from my GitHub on my phone

• 
  Lorenzo (@lorenzolfm) reported 16 minutes ago

  GitHub search is completely broken

• 
  kryptek (@kryptek134975) reported 18 minutes ago

  @ClaudeDevs Same here.. I just saw this post and this is insane. I'm already at 35% weekly usage. I've only knocked out a couple of my Github Issues. Small scope.

• 
  Lex Duke (@HuttonBockflie) reported 22 minutes ago

  @AlexFinn @openclaw It tooks my Claude Opus 5(High) entire one hour to fix the config bugs so that OpenClaw would relaunch properly after the update. And Claude says normal users can‘t fix the bugs in one hour because the bugs have no official answers in GitHub issue, LOL.

• 
  Suryansh Tiwari (@Suryanshti777) reported 24 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  Dylan (@InsecureNature) reported 25 minutes ago

  @IceSolst Best thing to do would be to block, you can do this with pre-commit which runs locally but GitHub is anti-competitive and does not allow the best in market secret scanners to do server blocking (they force people to use theirs) 🧵👇

• 
  kkiran (@kkiran) reported 25 minutes ago

  @SparselyActive I had Claude look for a solution. I submitted an issue on GitHub for the author to take a look at this issue. I will continue monitoring this.

• 
  IMZO Dev (@imzodev) reported 25 minutes ago

  Is anyone using the Github MCP Server? Which tools does your agent use the most?

• 
  dan0mad (@dan0madpro) reported 26 minutes ago

  @witcheer Got a question for you; how do u allow them to message each other? I’ve been using a combination of Hermes kanban boards and GitHub issues as a source of truth, and it works, but curious to know if there’s more efficient ways

• 
  Zin. (@Zin_Skript) reported 31 minutes ago

  @qilua02 Github Copilot for students is really bad. A while ago, it was great, they let us use frontier models for free (with 300 requests/month) but now I'm limited to auto mode & get terrible low-end GPT Models & other low power models

• 
  pratwwk (@pratwwk) reported 34 minutes ago

  @dhh please fix github

• 
  Peter (@NoDataSold) reported 35 minutes ago

  @thsottiaux For GPT-5.6 Sol specifically, I’d push beyond “more context / more agents / think harder” and focus on making all that intelligence compound over long-running work. A few upgrades I’d love to see: • Durable cognitive state Not just memory of facts or chats. Maintain a structured evolving state of the problem: goals, decisions, hypotheses, evidence, uncertainties, dependencies, unresolved questions, rejected approaches and why. I should be able to return weeks later and have Sol understand where the thinking reached, not merely retrieve things we once said. • Epistemic retrieval Make retrieval part of reasoning. Instead of mostly finding semantically similar context, deliberately search for: – contradictory evidence – failed approaches – structurally different precedents – high-surprise observations – information likely to change the conclusion Retrieval should reduce uncertainty, not reinforce whichever explanation Sol already has. • Verifier invention Move beyond generic self-review. When correctness matters, Sol should invent an appropriate falsification mechanism: What experiment could break this? What counterexample disproves it? What independent source should disagree if I’m wrong? What test should I construct? Would an independent agent reach the same conclusion? Separate discovering an answer from certifying it. • Adaptive compute allocation Reasoning effort should become internally dynamic rather than mainly determined by one global setting. Sol should estimate where uncertainty and consequence sit, then allocate searches, reasoning, agents, tools and verification accordingly. Most of a task might need little thought while one assumption deserves 80% of the compute. Spend intelligence where another unit has the highest expected value. • Persistent world-state modelling When Sol interacts with GitHub, browsers, terminals, Drive, apps, APIs, etc., maintain an explicit model: What state existed before? What did this action change? What evidence confirms it? What could invalidate that belief? What may have changed externally? Tool use becomes reasoning over state transitions rather than disconnected calls. • Counterfactual execution planning For ambiguous problems, preserve multiple materially different strategies long enough to test them. Branch when uncertainty warrants it. Run cheap experiments. Kill losing branches when evidence arrives. Merge useful discoveries. Replan when the problem representation is wrong. Multi-agent becomes exploration and falsification, not simply parallel labour. • Native continuity across ChatGPT → Work → Codex One durable task state that moves between interaction modes without hauling an entire conversation behind it. Carry forward: – objective – current state – decisions – evidence/provenance – unresolved questions – artifacts – permissions/constraints – exact restart point The interface can change without giving the intelligence amnesia. • Context observability Without exposing private chain-of-thought, let users inspect the information shaping the task: Which memories were retrieved? Which project files are active? Which chats/sources influenced the state? What was omitted? What is stale? Where do sources conflict? What assumptions lack evidence? A million-token intelligent system is easier to trust when its epistemic inputs are observable. The common theme: I don’t particularly want Sol to just “think longer.” I want it to maintain a coherent, falsifiable, evidence-grounded understanding over time — while deciding what to remember, retrieve, test, delegate, revisit and discard. That feels like a much more interesting frontier for Sol.