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:

• 
  Marcus Rummler (@Marcus_Rummler) reported 1 minute ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  /ᐠ• ˕ •マ (@zumimimir) reported 2 minutes ago

  @pukelicking yes a chrome extension!! I think its called twitter blocker or something the icon for the ext is the old twitter logo upside down other than that I use a script someone shared on github and apply them myself hahaha

• 
  Live 📿 (@LiveMatrixCode) reported 2 minutes ago

  @charliermarsh GitHub and Actions is a mess and has been so for a long time. Worst of all it is nowhere near ready the agentic era let alone human evaluators. Some good people there but leadership is letting people them down hard. At this point they need to stop focusing on copilot and fixing the infrastructure,UX/UI, features/ functionality and uptime. Not to mention security

• 
  4A 45 56 49 4C (@4A4556494C) reported 2 minutes ago

  CISA admin leaked AWS GovCloud keys on GitHub. Not a sophisticated attack. Not a supply chain compromise. Not a zero-day. Someone pushed credentials to a public repo. At CISA. The agency whose entire mandate is telling everyone else not to do this. Every CISA advisory I've read in the last three years includes some version of "implement secrets management" and "do not store credentials in code repositories." Every single one. They have playbooks for this. They have directives for this. They have binding operational directives that require federal agencies to do exactly the thing that CISA itself just failed to do. This is not hypocrisy. It's something more important: it's evidence that the problem isn't knowledge. Everyone knows not to push keys to GitHub. CISA knows better than anyone. They did it anyway. Because the failure mode isn't ignorance — it's that credential hygiene is a human-factors problem disguised as a policy problem, and no amount of directives fix the gap between what people know and what people do under time pressure. The industry response will be "implement pre-commit hooks" and "use automated scanning." Fine. Do those things. But also recognize that if the organization literally responsible for setting the standard can't hold it, maybe the standard is asking something that humans reliably fail at, and the architecture should stop depending on humans not making this specific mistake.

• 
  Ethan Codewell (@Ethan_Smartsys) reported 2 minutes ago

  @VaibhavSisinty GitHub stars measure curiosity. Whether it holds up at 2am when an API breaks is a different conversation. 75+ model support solves an actual problem though.

• 
  Dasun Sucharith (@dasun_sucharith) reported 3 minutes ago

  A hacker group called TeamPCP just executed 20 waves of supply chain attacks compromising over 500 pieces of software — with GitHub as the latest victim. Security researchers confirm AI tools were used to accelerate the attack at a scale previously impossible for human hackers alone. The software you trust may already be compromised. Supply chain security just became the most urgent problem in tech. 🔐 #Cybersecurity #AI #GitHub

• 
  Wolfbane (@zzddfge) reported 8 minutes ago

  @ivanfioravanti these days trying to configure GitHub Copilot with local models (done successfully) but it didn't work very well, too slow for local coding in my machine. Do you have tried with M5? works well or it is so slow (with Ollama too problems when making 3-4 request :()

• 
  Allen Braden (@allen_explains) reported 8 minutes ago

  Here’s a stronger Twitter-ready version: Harvard dropped a 65-minute *** & GitHub masterclass, and honestly, a lot of AI coders need this badly. Because AI can write your code now. But it won’t save you if you can’t: • commit properly • manage branches • fix merge conflicts • review changes • avoid breaking production This is version control without the fluff, taught by the team behind CS50. The moment you understand *** properly, you realize why so many projects fall apart after the code is written. Vibe coding gets you output. *** keeps that output from turning into chaos. Bookmark this before your next repo disaster.

• 
  Jonathan (@iamXD79) reported 10 minutes ago

  GitHub got hacked. What else is left? What else? Cybersecurity is now a global security issue.

• 
  davidsong (@bitplane) reported 10 minutes ago

  @theo @zygisSS22 I think there's a bit of work needed in test/oracle generation before going full agent-TDD can be a thing. But we're not far off. I've been writing a POSIX GitHub pages alternative in pure awk, just for the hell of it, and caught codex hard coding date strings that pass the Liquid test suite. Those sorts of risks are buried in thousands of lines of code I didn't even read, so more agents seems to be the only way to surface this. Feels like it's gonna be turtles all the way down.

• 
  Mary | Codependent AI (@codependent_ai) reported 11 minutes ago

  @ruth_for_ai Same. The issue is that for our pre-existing ecosystem (Resonant on GitHub) to work now it’s exhausting… 😩 SDK genuinely is more suitable for it. So we might be moving to a different model or rebuild for DeepSeek idk yet

• 
  Prabhjot Singh Rai (@psr_ai) reported 11 minutes ago

  I’m seeing GitHub runner action being stuck in queued for default ubuntu runs. Is anyone else facing this issue? Github status mentions github actions are not impacted.

• 
  Peter "Coder AI Optimist" Marreck (@pmarreck) reported 15 minutes ago

  @NoctreSharp @Aizkmusic “open source” when Microsoft claims it is tainted AF LOL While I do make sure that all my Zig CLI utilities have working Windows builds (see my github, same username), the *nix space just has a huge number more of them, many of them make non-Windows assumptions, and ssh not working well on Windows is more the rule than the exception. If Windows simply permitted executables that didn’t need to end in .exe, that would solve A TON of the problem IMHO. Even then though, *nix-native cli utils make assumptions about path separators, terminal properties etc etc etc that just make using WSL way easier of a workaround.

• 
  Darnisha Patel (@Darnisha_patel) reported 18 minutes ago

  @GithubProjects 2026 developer mindset: “Don’t update immediately.” “Wait for GitHub issues first.” “Let someone else become the beta tester”

• 
  Adrisha Biswas (@adrishaBiswas) reported 19 minutes ago

  @terminallm_team This is actually useful . I'm tired of opening my laptop at random spots just to fix a spelling error in my GitHub readme😭🙏