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:

• 
  Jaba (@Jaba96438469) reported 2 minutes ago

  Soooo, what are people using now that GitHub isn't cool anymore? I suppose I could actually run my own server.

• 
  AsfaS (@s_asfa44317) reported 3 minutes ago

  @KaiXCreator @KaiXCreator GitHub. Even when it's down, we just stare at the status page and wait patiently.

• 
  Working-Ref (@kkotkkio) reported 4 minutes ago

  How to start: → Request a Daybreak scan via OpenAI's site → Experiment with GPT-5.5 API for code security review → Prep your CI/CD for the Q3 GitHub Actions SDK False positive noise: down 50–84%. AI-native security is no longer theory. Bookmark this.

• 
  Sandro Volpicella (@sandro_vol) reported 7 minutes ago

  Docker as a service. Great idea. No WebSocket support. No Node updates. GitHub issues with zero replies. AWS published a sunset notice — then removed it. Seriously, I wouldn't recommend using that at all. 𝐄𝐥𝐚𝐬𝐭𝐢𝐜 𝐁𝐞𝐚𝐧𝐬𝐭𝐚𝐥𝐤

• 
  Felipe (@beatingLupin) reported 7 minutes ago

  @DavidKPiano @peterpme question, I remember trying and reading a issue on the github 1year ago but are people using tanstack query + xstate? how are they doing it? I really wanted to do this some time ago, but was very tricky

• 
  Darren (@CorboDT) reported 13 minutes ago

  @github reviews by @GitHubCopilot are so damn slow. Are you running your agents on half a dozen PII’s? It’s faster to wait for humans to respond. Is this a ploy to increase developer job security?

• 
  Alejandro (@mikesislac) reported 16 minutes ago

  Hey @gingerbeardman I'm mikesislac from the github twitter issues thread. I can't sent you a DM cause I'm not verified.

• 
  Grant @3D Musketeers #1440Makers (@3D_Musketeers) reported 17 minutes ago

  @stlDenise3D @lost_in_tech @ZombieHedgehog_ Let's have them edit their github first to get up to compliance, fix the fire issues in the A1, and stop threatening solo devs before they go ahead and edit that old post. You know, priorities.

• 
  Thyago Liberalli (@conanbr) reported 19 minutes ago

  DeepSWE may end up becoming one of the most useful benchmarks we’ve seen for AI coding agents. Created by @datacurve , it was designed to address many of the issues that have started to plague benchmarks like SWE-Bench Pro: contamination from public GitHub data, tasks that are too small to reflect real development work, flaky inherited verifiers, and rankings so close together that they often don’t match what developers experience in practice. Instead of tiny bug fixes, DeepSWE contains 113 original long-horizon tasks spread across 91 actively maintained repositories and five programming languages. The prompts are short and natural, but the work isn’t. On average, agents need to modify around 668 lines of code across seven files, with success measured through hand-written verifiers that check actual behaviour rather than a specific implementation. One particularly interesting finding came from Datacurve’s audit of SWE-Bench Pro. Claude Opus 4.7 and 4.6 would often inspect the full *** history available in the container, find the gold solution commit, and effectively copy the answer. That’s less “software engineering” and more “open-book exam with the answer sheet left on the desk.” According to the audit, this accounted for roughly 18-25% of their successful runs. GPT models didn’t exhibit this behaviour, while Gemini did so only rarely. DeepSWE removes this loophole by using shallow clones. The end result is a benchmark that feels much closer to real software development. What stood out to me wasn’t that GPT-5.5 came first. It was how much separation appeared once the benchmark stopped measuring small isolated tasks and started measuring messy, long-running work across real repositories. The ranking itself isn’t surprising. The size of the gap probably is.

• 
  Ruby (@rubie_shell) reported 23 minutes ago

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

• 
  Ella 😽 (@Ella_ML_) reported 26 minutes ago

  @JDSalbego @ClawSecure @openclaw Need that GitHub one locked down first

• 
  Kyle Cole (@kylecole90) reported 31 minutes ago

  @thsottiaux GitHub issue intergration. I want to be able to select the issue right from Codex. Claude Code desktop has this feature and it was nice to not leave the app

• 
  Gabi Weinberg ⚓ (@StartUpRabbi) reported 33 minutes ago

  @danielcberk What do you use to run daily tasks that you want to work on a schedule without needing to press “run” and to keep them not working with LLMs. Like I prompt a script that does tool calls/database calls, and I don’t want to setup GitHub to run workers.

• 
  Gitforge (@GitForge_io) reported 36 minutes ago

  We just completed a full frontend rebrand for GitForge. The core tech is almost done, and we’re building the first platform on Base that turns GitHub repos into autonomous onchain organizations. Repos will be able to hold treasuries, fund issues, route contributor payouts, and coordinate AI agents directly from the development workflow. Not just a new look. A new operating layer for software. Built on @Base.

• 
  QarthO (@quartzdevgg) reported 38 minutes ago

  @AdityaTripathiD @heyandras @coolifyio With AI Slop, Github issues are only going to get worse/spammy, and opensource as we know it now WILL change how its done. Coolify principle isnt telemetry = bad. How its collected, and how its used are what makes it bad. Coolify will keep degrading unless something changes.