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:

• 
  Nna 🫂 | Software Engineer (@Big_Ca_li) reported 8 seconds ago

  Pre-commit hooks run before your code leaves your machine. CI/CD scanning runs after it's already on a remote server. The difference is timing. Gitleaks as a pre-commit hook means a committed secret never reaches GitHub. It gets caught in the 30 seconds before the push. The window of exposure is zero.

• 
  Arct Cloud (@arctcloud) reported 3 minutes ago

  @FurtherLucky It depends on what part of GitHub Actions you want to replace. For actual iOS builds, you would still need macOS with Xcode, so our regular VPS plans would not compile the app directly. But we can help with backend, API, database, CI helper services, or Linux based runners around the app. What is causing the most trouble right now? Build times, macOS runner costs, queues, signing, or deployment?

• 
  Jack Lippold (@CaptainAppJack) reported 3 minutes ago

  @valhalla_dev Stop trying to put humans in the loop. Oh ma gaud!!!! Is this where we are now? The h/acc vs e/acc vs Luddite’s comes down to code review? Adding this quiz as part of opening a PR on a public OS repo on GitHub might actually be a good idea, but agents would just answer it.

• 
  Gidimoney369 (@Gidimoney247) reported 4 minutes ago

  💬 PIONEERS — Node v0.6.2 just dropped. Coincidence or the final signal? ⚡ The timing is everything. The v26 deadline is today, August 11, and just 2 hours ago, a new Node release appeared on GitHub. What's in v0.6.2? · 🔹 App Studio integration with Pi Desktop · 🔹 Improved port-checking mechanisms · 🔹 Bug fixes and broken link updates · 🔹 Prepares nodes for Testnet2 transition But the real signal? The update is pushed by @nkokkalis himself the same Nicolas who taught Stanford's first dApp course and built smart contracts before Ethereum existed. The v26 Upgrade: Hard deadline. 421,000 nodes must comply or lose Mainnet access. Expected downtime? Under 5 minutes. Something is loading. The pieces are falling into place. 👇 Is your node on v0.6.2 yet?

• 
  Leander (@leanderriefel) reported 8 minutes ago

  This is what I was scared of. If this really is how Origin works it is not a GitHub alternative. It solves an entirely different problem.

• 
  Neuro (@neurometax) reported 8 minutes ago

  @BkashJosi havent had chance to finish integration, still building the PR. finally have my Hermes set up to work my github and process my PRs with merge conflicts and issues.

• 
  Yerkebulan Rakhimov (@yerkeRakhimov) reported 11 minutes ago

  Day 37 of working on the thing that hurts every SaaS founder: distribution. I'm doing it with my own product, PostMine. The numbers are the same as always, nobody's paying. 43 people signed up, and 83 tried the product if you count the anonymous ones, so without anonymous access half of those people would never have touched it and I'd have gotten about half the feedback too. But today's post isn't really about numbers. It's about one of the most common founder mistakes, one I've made and still haven't fully shaken off: building in the dark, going only by your own judgment, your own view of the product and your own picture of how everything is supposed to work. In my case it's twice as hard, because I'm my own customer and I build this thing for myself first. But what matters to me isn't always what other people need, and the stuff I throw out isn't always useless to founders just like me. Building for yourself and for people like you is a good strategy, there's just a catch. When you make something from scratch with your own hands, you really don't want to admit its flaws. It's probably how parents feel about their kids, yours is always the best one, while in reality everybody's got plenty wrong with them. Not long ago it hit me: I'm the target user of my own product and I don't use it. Weird, right? A product for people like me, and I never open it. That's a huge problem in solo SaaS. Best case it costs you time, worst case it drags you somewhere completely wrong and you lose the product. That went on for about two weeks. I was pushing as hard as I could, messaging founders from Product Hunt, finding them on X, telling them my product would help them get their first customers, which is literally what it's for, while I was out there finding my own customers by hand. Embarrassing. What actually opened my eyes was one piece of feedback that went through every little detail and named the main problem: the service does a bad job of what it promises. It stung at first, I wasn't happy about it at all. Then I sat with it and realized he was right, I just didn't want to admit it for a long time. The signs were all there. I wasn't using it myself. I was rushing to promote for the sake of promoting. I don't think it was a mistake though. Without all of that there'd be no 83 people and no feedback that pulled the mask off my project. Today is a new day and I'm getting serious about the core feature: finding customers on X and Reddit. I'm taking it to the point where I'd actually use it myself, deleting the features nobody touches, and rebuilding the MCP, because right now it's broken, it just hands you information and that's it, adapted to nothing, and I don't use it either. I want more automation in there. I may also hook up GitHub, so it can pull what I've actually shipped and write posts off that. So everything else on the promo side stops. What's left is a daily post about progress and a bit about life. If you tried PostMine and it let you down, tell me straight. That's exactly the kind of feedback that turned me around. And don't forget to give feedback to your own friends and colleagues. Sometimes it saves someone's product and turns the whole thing around 🙃 Thanks to everyone who already wrote.

• 
  Charlotte Schmitt (@LottiSchmitt) reported 19 minutes ago

  We spent two years building an app, then noticed our best customers barely open it. They read mentions in Slack, pull them through the API, or ask their agents. So the newest thing we built is for the terminal - the @Octolens CLI: npm i -g octolens - your agent reads overnight mentions and sends you the ones worth replying to - bug reports on Reddit or GitHub become Linear issues - the weekly report lands in Slack Every command has a --json mode, and the package ships with an AGENTS.md so Claude Code can figure out how to use it on its own. Many of our customers will never open a terminal, and nothing changes for them. This is for the growing group of teams automating this work.

• 
  JackLame (@Jack_Lame12) reported 19 minutes ago

  @ardent__dev .env.dist with instructions on how to use it But then I dont use github. *** feels a lot safer if I just use another partition or a drive on my home server to house the ***

• 
  RaoulDuke (@RaoulDukeDegen) reported 22 minutes ago

  @mertdumenci yeah theres a bunch of open github issues about desktop lagging on long threads

• 
  Pitchfork & Torch ♞ (@SuddenlyJon) reported 23 minutes ago

  Grok Bot’s Electron desktop app launched dead because a botched app.asar rewrite left empty dist/deps stubs (so Node couldn’t find the real tree-sitter package still sitting in app.asar.unpacked), Grok Build CLI immediately diagnosed it, wrote a one-command restore script + full runbook, and published the MIT fix on GitHub LOL @bot @SpaceXAI

• 
  Berend de Boer (@berenddeboer) reported 23 minutes ago

  I really liked this article from @victorsavkin . I agree on workflow, but I don't think that's incompatible with a product. So my ready-for-agent tool implements a workflow by taking in GitHub issues as work, but from there it's automated, all the way to create PRs and merge.

• 
  noah lewis (@novalevys) reported 27 minutes ago

  @effectfully can new Claude solve your Haskell 8 problem GitHub event?

• 
  Branko (@brankopetric00) reported 30 minutes ago

  You push a quick fix. Five minutes later the commit has a live AWS key, sitting in a public repo with three forks already. A teammate says delete the file, force-push, move on. That key is already out. Scrapers harvest secrets off public GitHub in seconds. Rewriting history cleans the repo. It does nothing about the credential itself. What you're actually staring at: - A key with S3 and compute permissions on a real account - Forks that already have the bad commit, force-push or not - No secret scanning or pre-commit hook that would have caught this earlier - A clock that started at push, not at the moment you noticed Revoke first, rotate first, audit for use first, or clean the *** history first? Pick the wrong order and the "fixed" repo still has an active key loose in the wild.

• 
  Nitesh (@NiteshTechAI) reported 30 minutes ago

  Every agent tool wants your keys on their server. This one never leaves your machine. It's called ZeroClaw, from @zeroclawlabs. • One Rust binary, no runtime to install. • Around 20 LLM providers including Ollama. • 30+ channels: Discord, Telegram, Matrix, email, voice. • Tools reach shell, browser, HTTP, hardware and MCP servers. • Your keys, your workspace, your machine. The reason to reach for this is never speed. It is that the data cannot leave. Client work, anything under NDA, or a home server you want reachable from Telegram without handing a vendor your shell. Point it at Ollama and ask it to read one file on your own disk. No account, no key, nothing leaving the machine. ⭐ 32,000+ stars on GitHub. Apache-2.0 licensed. 🔗 GitHub link in the comments 👇