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:

• 
  ɹǝqɯǝɯ OƎƆԀ∀W∀ (@AMAPCEO_member) reported 23 seconds ago

  @HansGermishMagi @HealthRanger Hugging Face and GitHub have these models, including quantized versions with reduced hardware requirements for running locally. Make sure to use recognized sources as there are numerous forked implementations which could have security issues.

• 
  Axel Bitblaze 🪓 (@Axel_bitblaze69) reported 4 minutes ago

  if you see posts like this, top 10 repos that "print money while you sleep" and install all of them then you’re wasting your tokens, a quick reality check: these github repos don't print money. workflows do. these repos are just the tools. you still have to wire them into something that solves a real problem you have. like the ones from the list i actually run since past few weeks are > hyperframes - generate reels from prompts. saves me 2 hours per video > fincept terminal - open source bloomberg, running locally > agentic inbox - email automation that doesn't suck (cloudflare built this) > camofox browser - the stealth browser for serious scraping and what i'd add to the list > claude-mem for persistent memory across claude code sessions (46k stars in 48h) > last30days-skill to scrape reddit/x/youtube for any topic in one prompt > anthropic skills repo for production-grade skill templates good post below but install based on actual workflows you want to automate, not the promise of passive income.

• 
  Matt Helm (@matthelm) reported 5 minutes ago

  @noahzweben Fantastic! I tried it out with Issue opened, creating a new GitHub Issue on the repo, but it didn't trigger the routine. trig_01MNuMWeDvQLTw3arNHoSysT

• 
  Ronan Berder (@hunvreus) reported 10 minutes ago

  @badlogicgames What about greenfield work, or new features. I'm assuming you don't do that off of GitHub issues. Just talk back and forth with the AI to build a plan in a markdown file and then pull the trigger once aligned?

• 
  artee (@artee_49) reported 14 minutes ago

  Github has handled this quite poorly. We have not been given a list of affected commits so we can go and track them down and ensure all our automated flows are working as usual and that engineers are aware their changes got reverted. It's chaos.

• 
  Ryan Oksenhorn (@ryanzip) reported 15 minutes ago

  .@GitHub is screwing up so hard here. Terrible terrible bug, and worse: they’ve provided Zipline zero support for identifying afflicted repos and PRs. We’re still cleaning up their mess.

• 
  Vulnerable U (@vuln_u) reported 16 minutes ago

  Unlike basic data theft, it encrypts and sends data to an external server, and if that fails, it pivots to GitHub creating repos, abusing tokens, and even pulling secrets from CI environments. If version 2026.4.0 is installed, assume everything on that machine is compromised.

• 
  Shane Andersen (@Shane380) reported 17 minutes ago

  @Telzezl @DefenderOfBasic It's not exactly "written" down. The internet is a decaying medium where only some things last forever but everything is real the moment it is said for that is how reality be. My .net went down due to debunking. my GitHub will have some relevance soon But I'm busy with babies

• 
  dexploarer (@dEXploarer) reported 19 minutes ago

  ngl, the amount of projects that die, all because its holders dont have, or understand github sucks. solo founders/devs/small teams, they are building, not socializing....and if they are socializing they should prolly be building. im try and fix that soon fyi

• 
  Hazeezet (@hazeezet) reported 20 minutes ago

  AI developer tools tier list: S Tier: Claude, Cursor A Tier: GitHub Copilot, ChatGPT B Tier: Gemini, Codeium C Tier: Amazon CodeWhisperer Fight in the replies. I have strong opinions and I'm not backing down. 🏆🤖

• 
  bored michael (@mvarinus) reported 21 minutes ago

  @GergelyOrosz Pretty sure the core problem is github actions. Each commit cascades to multiple compute-heavy test/build/etc steps, and if commits 10x, that is a huge call on your infra. They recently started gating action runs more from non-verified contributors it seems, confirming it.

• 
  Tech Ironic (@techironic11) reported 25 minutes ago

  @howfxr I didn't research in detail of exact issue here. But github actions allows you to automate certain workflows such as after every comit pushed, build an apk and release it. So attackers manipulated it to make it mailicious

• 
  Josh Long (@starbuxman) reported 29 minutes ago

  ouch 🤕 big L for @github I know good people there and they’ve been I think unfairly lampooned this year for outage after outage which I think would be better laid at the feet of AI agents deluging the platform so this sort of actual problem comes at a really bad time

• 
  Chief | Senior Vibecoder🛶 (@sniperchief_001) reported 32 minutes ago

  type “*** add src/about.jsx and hit enter. 📍Step 3. type “*** commit -m “fill up short description of your changes” and hit enter button. 📍Step 4 - Push to github: type “ *** push” - viola your files should now be updated on github - to see changes, redeploy server.

• 
  Matt Pocock (@mattpocockuk) reported 33 minutes ago

  Tons of folks are piling in here saying that AFK agents are a myth. I have been using them to ship these GitHub repos: mattpocock/evalite mattpocock/sandcastle mattpocock/software-factory (might be public by the time you see this) Here are a few steps to making this work, and some reality checks. Definitions Let's split this into the day shift and the night shift. Day shift is planning/review/QA, night shift is AFK implementation. Day Shift (part 1) 1. Use /grill-me to align with the AI 2. Use /to-prd and /to-issues to create a PRD (the destination) and implementation steps as separate tickets, which can be grabbed in parallel (the journey) 3. The PRD is a ticket, but it's not an actionable step. You just put the user stories there This is pure requirements gathering ****, same as it ever was. Night Shift 1. I run a planner agent which looks at all the tickets and sees what can be worked on now, and what's blocked 2. The planner agent then kicks off multiple agents (sandboxed using Sandcastle, my OSS tool) to implement the code 3. I then have an automated reviewer agent look at the commits produced - one agent per implementation. This checks alignment to the original PRD, as well as code quality 4. These commits end up on branches that get PR'd to main 5. The planner agent runs again until all work has been completed The review is a crucial step - it's saved me MANY times. I am planning to massively increase the amount of review I do, hopefully with multiple agents. But guess what - AFK agents sometimes produce bad code. This can happen because of: a. The original plan was bad because the best solution was something different b. The original plan was bad because it didn't take into account all the unknown unknowns, and the AI had to make some decisions during the coding session which were bad c. The plan was good, but the AI just shat the bed (twice, once in the review stage, once during implementation) d. Your codebase is bad and the feedback loops don't tell the agent if it did a good job or not So... QA: Day Shift (part 2) 1. QA all of the branches created 2. Create follow-up issues, potentially editing the original PRD to adjust the destination This will usually take a long time, often as long as planning. But then you kick off the night shift again. Once QA is all done, you review the important bits of code manually, usually in PR's. There isn't anything better than the PR UI right now, so that's what we're stuck with. Wake-up Calls 1. If you let the AI run all night unbounded by planning, it's going to produce **** code 2. Mostly, my loops finish before I go to bed, it's just the night shift catching up to the day shift 3. The only reason I do AFK at all is because it allows me to automate review and totally not give a **** about latency 4. I always run night and day shift in parallel. I can't plan that far ahead (skill issue, probably). I need working code to base my plans from, so I'm aggressively QA-ing stuff that lands