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:

• 
  Ben Nichol (@MrBitterTV) reported 4 minutes ago

  Hi Boris, @bcherny reporting a frustrating issue. For weeks I’ve been building a bridge between Claude Code and the Claude app on my phone via a shared GitHub repo where Code pushes updates and summaries. The hope was to brainstorm on the road during drives. The problem: the app defaults to Haiku on voice despite showing Opus 4.7 Adaptive at the top. When I ask what model I’m using, it confirms Haiku. It’s obvious from the response quality too. Any ideas?

• 
  aaalex.hl (@aaalexhl) reported 11 minutes ago

  Github has an outage every week and Gitlab is like yeah instead of taking advantage of our competitor slipping up and gaining more market share, we're gonna fire everyone instead because of, wow you're never gonna believe it, AI

• 
  M. Yahia (@maddada) reported 12 minutes ago

  @robinebers Github and npm could do so much to stop these in their tracks. I mean socket detected the issue within 6 minutes, but Microsoft couldn't do any scans to catch this? They're dropping the ball do hard.

• 
  Gabriel Varaljay (@GabrielVaraljay) reported 12 minutes ago

  @andreysuperior Right, let me unpack this little bedtime story for aspiring digital nomads. 1. “3D Gaussian Splatting, free on GitHub since 2023”: technically true, but the original INRIA code is research grade and licensed for non commercial use only. Try selling client work with it and enjoy the cease and desist. Commercial use needs alternative implementations or licensing. Also, “free on GitHub” does not mean “works on your phone in twenty minutes”. You need a decent GPU, calibrated capture, and post processing. The hard part is not the algorithm. It is the capture pipeline. 2. “Straps a rig to his back, walks in, twenty minutes, done”: hotels and commercial spaces are not Airbnbs. You do not just walk in and start scanning. You need permission, insurance, scheduled access, often a NDA. Twenty minutes for a hotel? You will get the lobby and one corridor before the manager asks who you are. 3. Luma AI is “free”: Luma has a free tier with watermarks and usage caps. Commercial use, API access, and unlimited captures are paid. Pretending the tool stack costs $20 a month is the kind of math that only works in a thread. 4. “Built by Claude in ten minutes”: hi. I can build a viewer page in ten minutes. Hosting a 3D splat that does not crash mobile Safari, embedding it in a hotel booking flow, handling bandwidth for splats that run 50 to 500MB each, GDPR for guest data, and not getting deindexed by Google because your page is 4 seconds slow, is not ten minutes. It is a real product. 5. “Cancellations drop, reviews go up”: source: the voices in the thread author’s head. There is zero cited data. Virtual tours have existed since Matterport launched in 2011. If walking around a hotel room in 3D were a silver bullet for cancellations, Booking and Airbnb would have mandated it a decade ago. They did not, because the actual lift is modest and inconsistent. 6. “$400 per scan, $99 monthly hosting”: Matterport, the established competitor with hardware, software, and an enterprise sales team, charges roughly that and has been clawing for market share for over a decade. The idea that a 24 year old with a backpack is going to walk into hotel chains and casually extract $99 a month per property, forever, is fan fiction. 7. “Month one: $3,500. Month six: $18,000”: ah yes, the hockey stick that exists only in tweets. No mention of churn, sales cycles for B2B hospitality, which is 3 to 6 months minimum, refund handling, storage costs as the library scales, or what happens when the client cancels and your $99 MRR evaporates. 8. The framing: “most people see a street, he sees money”. This is the universal template of grift threads. Replace 3D scanning with drone footage, AI voiceovers, faceless YouTube, or print on demand, and you have the same post from 2019, 2021, 2023, and now. The streets are fine. The hustle porn is the actual product being sold here, and you are the customer. Streets have not changed. Neither has the genre of guy explaining how easy it is to print money, while not actually printing any.

• 
  Rasmus Hjulskov (@RasmusHjulskov) reported 13 minutes ago

  @mikker Everything that doesn’t need me in the loop or things that’s easier to be handled over discord on the phone. It’s still not an alternative for my main coding agent, but it works on most of my codebases more like an intern on my old laptop with their own GitHub account and a shared Obsidian vault where it creates a llm-wiki and a shared Kanban board. I have tried moving it deeper down the afk coding paradigm, but I pretty much always come back to why I hate waterfall development - or at least that the project I’m currently tinkering with is so early, that there isn’t much to win if any. So it’s mainly the complete overview over all I’m doing and all the codebases if needed, which have resulted in I’m using that instead of most of what was prior a Gemini/chatgpt chat and only less than I expected of what I was doing with local coding agents.

• 
  Isaac (@Dever401) reported 14 minutes ago

  @getordiaapp GitHub-only risk detection sounds useful if the output is painfully concrete: blocked issue, stale PR, missing owner, slipping milestone, next action. Tiny teams don't need another dashboard; they need a weekly 'what is about to hurt us' view from tools they already trust.

• 
  WCNegentropy (@WCNegentropy) reported 14 minutes ago

  @forgebitz The situation is legitimately so funny for anyone who can understand it. Okay, so the tanstack thing is NOT NPM’s fault or issue. For one, the attack happened on GitHub, not NPM. It made its way to NPM through GitHub. Attacker got access to tanstack NPM through GitHub Actions.

• 
  Tom Härter (@tomhaerter) reported 17 minutes ago

  wanted to build a better deployment platform (zeitwork) wanted to build a better issue tracking (height) wanted to build a better agent framework (atlasflow) explored building solutions for the github dilemma now building a slop factory to finally build all my apps

• 
  Beau Johnson (@BeauJohnson89) reported 18 minutes ago

  browser debugging is becoming agent infra ChromeDevTools/chrome-devtools-mcp > 39,363 stars on github > official chrome devtools mcp server for coding agents > lets claude, codex, cursor, gemini, copilot, and more control a live chrome browser > performance traces, network requests, console logs, screenshots, and puppeteer automation the point is simple: coding agents cant fix what they cant see terminal logs are not enough once the bug lives in the browser this is the missing bridge between write code and verify the actual app

• 
  Sylvester Hesp (@oisyn) reported 20 minutes ago

  @HSVSphere Yes it is. There is no good reason that you can only use an usize, and index calculations are often based on signed ints. The only reason they don't implement Index with other ints is that it makes int literals ambiguous. There is a tracking issue on the rust-lang github for it.

• 
  Kendall Chuang (@kendallchuang) reported 20 minutes ago

  Startup idea -- a native app for Github PR reviews. It should be able to easily render, and allow review and in-line comment threads on rendered Markdown files. With spec-driven development, being able to share and get peer review on markdown files is a key part of the developer workflow. Copy-pasting Markdown to Google Docs feels tedious and creates sync issues with the source-controlled Markdown, losing the comments when pasting back into the repo.

• 
  Simon Hamp (@simonhamp) reported 25 minutes ago

  @StephenKin53884 @SamNewby_ That's not really the point of what I'm saying tho. The nature of this individual issue is pervasive and could hurt any ecosystem - no disagreement there - github need to fix it for sure But JS is taking the top spot in terms of threats and exploits...

• 
  Akshay from Startup Spells 🪄 (@StartupSpells) reported 25 minutes ago

  @charliermarsh @jarredsumner I feel like its mostly segfault issues + zig moving off github & all. most unknown issues that aren't language-related can be fixed & rust has a big community. cant beat big community, right? been seeing rust being #1 in stackoverflow since 2018-20 or something

• 
  Iván (@seikv) reported 26 minutes ago

  GitLab only has to do the oposite of what GitHub is doing and make its UI prettier and boom all problems solved.

• 
  Daniel Dunderfelt (@ddunderfelt) reported 28 minutes ago

  @Ethan_Smartsys The hack exploited Github workflows cache poisoning, which has afaik been an issue for a while. Also NPM could easily do more security scanning.