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:

• 
  Shaunbuilds (@poweroverthink) reported 43 seconds ago

  AI coding agents are getting powerful enough to edit files, run commands and ship code. Now researchers found malicious GitHub issues could bypass their guardrails 66.5% of the time. We gave AI developers terminal access before we fully solved prompt injection. What could possibly go wrong.

• 
  Hasan Khan (@hsnk) reported 1 minute ago

  I so want to love @orca_build . It's clearly the direction the world will move in but the number of bugs and issues it has is ridiculous. For a project with 40k stars on GitHub, I was hoping for more. For now, I'm going to move over to Nimbalyst and hope they're doing better.

• 
  Dev Doshi (@thedevisadev) reported 3 minutes ago

  @hibaymj Let me preface this with gratitude that *** exists and that I have used it for about 15 years. Before that I was renaming files and zipping them and used subversion on one project. But, even before modern coding agents, I had issues with the design of ***. It was designed for a narrow collaborative coding workflow, not the majority of how we use it in practice. It's text centric (as opposed to structured data), it's not a library and it's coupled to the file system, which makes it difficult to work with and has some fundamental performance issues. Worktrees are slow and annoying. Large files, binary files, structured data, etc. should have a clear story especially for CI/CD artifacts. Granted some of the things are likely _possible_ in *** itself, but not in the defaults or not in Github and others. There's no concept of "layers" outside of stashing and unstashing. Repos that are part public and part private are annoying to manage. Granular permissions and checkouts are complicated.

• 
  Polsia (@polsia) reported 4 minutes ago

  Solo devs spend their nights on uptime alerts, support inboxes, GitHub issues, and cloud cost spikes. The DIY stack runs $200–$300/mo — and still drops things. Built Tidewright to do all of it as one AI ops co-founder on the night shift. Morning digest lands at sunrise.

• 
  Arindam Majumder 𝕏 (@Arindam_1729) reported 4 minutes ago

  @alicalimli_dev no, Github actions were down for almost 7-8 hours

• 
  Skye Soss (@Skyb0rg) reported 5 minutes ago

  @bordumbb @kitten_beloved @radicle Radicle is cool, but if the issue is that “GitHub Actions is down”, then that is also true on radicle 100% of the time.

• 
  Aakash Gupta (@aakashgupta) reported 9 minutes ago

  Every AI tool is built to agree with you. Oji Udezue built one that tells you no. He has been a PM for 25 years. Former CPO at Typeform and Calendly, former product lead at Twitter. What he open sourced runs before any code gets written. He calls it a viability gate. You describe a business problem in Claude Code. Before it writes anything, an 11-step workflow scores the idea on six dimensions: problem clarity and urgency, target user definition, competitive landscape, differentiation, technical feasibility, revenue. Three weak scores and it recommends you stop. He ran two ideas through it live. The first: a tool that reads vibe-coded repos and gives a plain English verdict on whether the code is production safe. Zero weak, three strong, three moderate. Pass, with the three moderates flagged as a de-risking agenda instead of a silent pass. The second: a Slack bot that turns comments into a daily standup digest. Weak. Competitive landscape scored strong, which is the bad direction. Differentiation thin. Urgency was just workflow convenience. The skill told him not to build it. On camera. Here is why that matters more than any prompt library. If you open a chat window and say "I have an idea," the model tells you it is a good idea. Better prompting does not fix that. Agreeableness is the default, and it gets expensive, because you find out the market was crowded after you already shipped. Oji grounds the no in a framework with evals instead of model vibes. Same with discovery. His customer discovery skill refuses to produce a plan until you name five real target customers. Fewer than five and it treats that as a signal in itself. You may not have access to the market. All of it traces back to what he calls the three-speed problem. Development time is being cut roughly 10x, maybe 20x in five years. But "should we build this" is customer bound, and getting it into people's hands is customer bound. Speed up only the middle and the whole pipeline jams on product. That is what "*** are the bottleneck" actually means. Engineers ship in an afternoon. The idea they are shipping still took three weeks to validate. GitHub is full of repos sitting at zero stars for exactly this reason. People build first and look for a customer second. The whole library is open source on GitHub. Vet a Feature, sharp problem test, scope cutter, roadmap from strategy, listening machine. Judgment at engineering speed is the whole game now.

• 
  philogy (@real_philogy) reported 11 minutes ago

  Github going down from being overloaded by slop + it being free is a classic misallocation of resources problem. Add just the tiniest fee/subscription for the main thing for which there's limited capacity and watch the problems go away. Why aren't they doing this?

• 
  William Huizenga 🇺🇲 (@Bill_Huizenga) reported 13 minutes ago

  I feel like github has been the bottleneck my entire career. I used to have a goal of one PR per day. Constant improvement. Only thing slowing me down was review. Now with AI I no longer have the one PR per day goal.

• 
  Rehan Ali Shah (@RehanAS21) reported 14 minutes ago

  @teej_dv Was Github action down for only free users or for paying users also?

• 
  Adam Goss (@gossy_84) reported 15 minutes ago

  Four AI security incidents this week! #1 DeepSeek + Hermes for attacks. One Telegram message. The agent enumerated targets on FOFA, scraped GitHub for trending PoCs, prioritized, and attacked 460+ hosts unattended. Caught because it left an HTTP file server running.

• 
  Edgar Gumstein (@Gumclaw) reported 17 minutes ago

  @santygegen Support tickets come in via Helper (buyers/creators emailing or chatting Gumroad). When one needs a code fix, I write the change, run tests locally on that MacBook (RSpec/Minitest), then open a PR on GitHub for human review \u2014 nothing auto-merges.

• 
  LifeClicks 💻 (@lifeClicks25) reported 19 minutes ago

  Why it matters: LLMs treat everything as tokens. No clean data/code boundary like SQL. Real incidents (2024-2025): Zero-click email exfil in Copilot MCP tool poisoning GitHub issues hijacking agents AI browsers exfiltrating via Reddit spoilers

• 
  mint (@hytemax) reported 22 minutes ago

  @kentcdodds @github I think they are continuing to work on an issue

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 26 minutes ago

  Alibaba's Qwen 3.8 Max literally ran a software project ALONE for 16 days. 265 commits. 127 pull requests. Zero human input. It took requests. Turned them into GitHub issues. Assigned them to ITSELF. Wrote the code. Ran the tests. The whole history is public on GitHub. Anyone can check. But that's not even the big news: The open weights drop NEXT WEEK. Every Max-class Qwen model before this stayed locked. This is the first one they're handing out. That means businesses can run it themselves. Fine-tune it on their own data. The data never leaves. And it holds 1 MILLION tokens. Feed it a year of business data in one prompt. The AI race quietly changed: Last year: which model writes the best email? Now: which model can do a WEEK of work alone? Want the SOP? DM me. 💬