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:

• 
  Glenn 'devalias' Grant (@_devalias) reported 4 minutes ago

  @thsottiaux Now how about some focussed humming through that Codex GitHub issue backlog instead of ignoring everyone bothering to report things…

• 
  3D Print Hashira. ☸️ (@the_Spartan_Dev) reported 8 minutes ago

  Am I the only one who can’t push to GitHub? Is GitHub down?

• 
  Alex Zerntev (@alexzerntev) reported 8 minutes ago

  These are my literal prompt before creating a PR: Codex: /goal Do local PR reviews. fix any findings from those local PR reviews. keep looping on this until there are no local PR review findings. afterwards, push the changes to github and ask for a codex review. Monitor the PR, and fix any codex review comments, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. Otherwise, keep looping until the PR is ready to be merged and fully reviewed. Claude: /loop Do local PR /review and codex cli review ,fix any findings from those local PR reviews keep looping on this until there are no local PR review findings. afterwards, create a PR on github and ask for a codex review. monitor the PR, and fix any codex review comments or CI failures, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. otherwise, keep looping until the PR is ready to be merged and fully reviewed.

• 
  Kumar (@kumardeepam) reported 9 minutes ago

  @adisingh @agentmail github issues

• 
  Ramanjit Singh (@ItzRamanCoder) reported 11 minutes ago

  rebuilt the core of what i'm building after reading someone else's code on github. nous research open sourced their agent loop. i opened it planning to skim for ideas, and about an hour in realised my whole design was solving a problem they'd already solved better, with the model doing work the system should have been doing. deleted a lot that week. reading other people's code properly is the highest leverage thing i do, and i still catch myself treating it like procrastination.

• 
  Личная Борда (@myprivateboard) reported 12 minutes ago

  @RobertStefanic @valigo Well, I personally think the recent major outages affecting the largest services (e.g. github as the brighest one) are a sign the decline acceleration. As for the small features, e.g. google services have so many ******* annoying little issues that it's insane.

• 
  Nandlal Ushir (@nandlal_ushir) reported 13 minutes ago

  Instead of writing full prompts for minor use cases in GitHub Copilot use: /fix: Fix a function. /test: Fix or generate test cases /explain: Explain a method. #CopilotTips #CodeSmarter #DeveloperHacks

• 
  Ihor_Sk (@IhorSkiba) reported 15 minutes ago

  ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. ONE SLASH COMMAND REPRODUCES THE BUG, FIXES IT, WRITES THE REGRESSION TEST. It's called /debug-fix. Open source. Four beats, one command: → reproduces the bug from the logs → finds the root cause → ships the fix → writes the regression test so it never comes back That's the manual afternoon you used to bill for. Gone. It lives in Poshan's .claude folder on GitHub. One `*** clone`, one `/setupdotclaude`, done. Same repo ships hooks that block force-push to main and DROP DATABASE, plus /ship (staged code to merged PR) and /tdd (red-green-refactor). VILA-Lab took Claude Code apart and found it's overwhelmingly infrastructure, not model. /debug-fix is the proof. The $200-$500/seat IDE + copilot + SaaS debugger stack is doing less than a markdown file in a public repo. 👇

• 
  Damian Kleiman (@damiankleiman) reported 15 minutes ago

  @piyushkumarr_ Because GitHub is down 99% of the time

• 
  Tyler F. Cloutier (@TylerFCloutier) reported 20 minutes ago

  @ngriffin_uk @github My point is that I can appreciate the complexity and also feel this is unacceptably slow.

• 
  Local Man 🎯 (@KiddBubu) reported 22 minutes ago

  @penzington @linear A **** to disable review requests through specifically the github team. Githubs codeownership is broken already and we shouldn’t have to suffer on too linear for that.

• 
  Upwind Security MDR (@UpwindMDR) reported 25 minutes ago

  🚨High - Reported SQLite JSON Parser Use-After-Free (CVE-2026-51297) A use-after-free is reported in SQLite 3.41's JSON parsing logic: a crafted JSON payload can free memory and then trigger an illegal access, potentially leading to code execution, information disclosure, or denial of service. CISA-ADP scored it 8.8 (network, no privileges, user interaction required) and notes a public PoC. Caveat: this is not vendor-confirmed. The only technical reference is an anonymous researcher's GitHub repo - there's no official SQLite advisory, no fix commit, and no patched version, and it fits the pattern of low-quality SQLite CVEs the project often disputes. Verify against the SQLite project before acting. 👉If you parse untrusted JSON via SQLite's JSON functions on an old 3.41-era build, monitor for an official SQLite fix and update to a current release; otherwise treat as unverified pending confirmation.

• 
  WorktreeWise (@worktreewise) reported 25 minutes ago

  Your *** workflow is probably slowing you down. The cost of context switching isn't just mental—it is technical. Rebuilding dependencies, re-running servers, and stash conflicts add up to hours lost every week. Worktrees fix this. #*** #GitHub #DevTools

• 
  Nekt0 (@Nekt_0) reported 26 minutes ago

  Jarred Sumner tried to build a browser game. The JavaScript tooling was so slow that he abandoned the game and rebuilt the tooling instead. Three weeks later, his Zig transpiler was 3x faster than ESBuild. He spent the next year working alone in his room. When Bun launched, it pulled 10,000-20,000 GitHub stars almost immediately. The hype came from speed. The difficult part came after launch: supporting 10 years of Node.js edge cases without breaking production apps. Today Bun runs more than 2,000 Node tests on every commit. A 14-person team watches that number on office TVs. Jarred is also preparing Bun for developers who will not read the docs themselves. Every page ships in clean Markdown so AI agents can consume it directly. The game disappeared. The frustration became infrastructure. That is usually where the better company was hiding.

• 
  Nafiz M. (@nafiz_mahmud_99) reported 27 minutes ago

  The dev cycle: Write code. It works locally. Push to GitHub. CI/CD fails because of a missing semicolon in a file you didn't edit. Spend 20 minutes reading logs. Fix it. Repeat. #DevOps #CI/CD #SoftwareEngineering