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:

• 
  jdx (@jdxcode) reported 1 minute ago

  @nateberkopec @jnunemaker I feel like if GitHub had an option to require trusted publishing approvals through the mobile app that would really solve a lot of our problems. Deployment protection rules are _almost_ there, they just need to be improved a scosche more. I'm definitely long OIDC.

• 
  Josh Cirre (@joshcirre) reported 2 minutes ago

  @marcelpociot It's crazy how fast it is to get social login setup with auth I "own" for something like GitHub / Discord.

• 
  𝑫𝒂𝒏𝒊𝒆𝒍 𝑺𝒄𝒐𝒕𝒕 𝑴𝒂𝒕𝒕𝒉𝒆𝒘𝒔 🇦🇺 (@DanielSMatthews) reported 4 minutes ago

  @hakluke That data has been sitting on github for years, all it takes is a an import into QGIS then you can save it to the viewer for mobile and it sits on your phone, no server connection required. This is desirable as it lets you still find the nearest phone when the mobile network goes down.

• 
  Timur Yessenov (@Timur_Yessenov) reported 7 minutes ago

  @siloagents @trq212 I’d separate two layers: remote control from Telegram is easy; reliable Claude Code channels are really about auth, session resume, and permission prompts not getting lost. if GitHub issues are piling up, the UX problem is probably state, not chat.

• 
  Gaurav (@Leapofcode) reported 8 minutes ago

  @droidbuilds Claude can have its own version control tool like Github too, but if they force it use that only then it will be a problem for sure.

• 
  Kush (@kushbhuwalka) reported 12 minutes ago

  I find that an underrated way to get a lot of startup ideas is to just do a startup. here’s my list of spaces that i find interesting / have had problems with. - ci/cd - github actions alts - agent o11y - slackbot / iMessage / WhatsApp dx - coding agent optimization - dynamic UIs - agent harness testing on docs - software digital twins for testing - ui/ux bots - clicky but for your product - permissioning for agents - agent onboarding & auth - billing and cost tracking

• 
  MarMar Labs (@MarMarLabs) reported 13 minutes ago

  Most people use Codex to write code. The bigger unlock: use it to review code. Drop "@codex review" on any GitHub PR and it posts a real review focused only on P0/P1 issues. Reply "@codex fix the P1 issue" and it pushes the fix to the branch. Set AGENTS.md rules ("don't log PII") and it follows them. Auto-review on every PR = a second pair of eyes that never gets tired. #Codex #AIEngineering

• 
  Gabriel Varaljay (@GabrielVaraljay) reported 14 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.

• 
  Sylvester Hesp (@oisyn) reported 16 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.

• 
  Priyanshu (@imdevPU23) reported 18 minutes ago

  - Claude for coding. - Supabase for backend. - Lovable for frontend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - Resend for emails. - GitHub for version control. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally ship a startup from your bedroom now. It’s not even cost much many of them give free initial credits

• 
  Ruben Distinct (@RDistinct) reported 19 minutes ago

  @eleliayub you missed the point. The recent tanstack supply chain attacks were due to github actions cache being poisoned through a pull request which in turn allowed malicious npm packages to be published as if legit. JS has its own quirks but the recent attack was a ci/cd issue not js.

• 
  Jekson (@Jekson1pp) reported 20 minutes ago

  Nobody noticed this repo until Big Tech started paying lawyers to make it disappear. Invidious. An open-source, privacy-first frontend for YouTube. No ads. No tracking. No algorithm feeding you outrage. Just the video you came to watch. On the surface: a clean GitHub README. AGPL-3.0 license. A bird from Big Buck Bunny playing in the preview. Community chat on Matrix, IRC, Fediverse. Looks like a quiet indie project maintained by a few idealists. Pause here. Look past the screenshots. 275 commits per year. 403 open issues. 77 pull requests. A distributed instances list — meaning no single server to shut down. 78% translated into other languages. 477 users actively coordinating on Matrix right now. This isn't a side project. This is infrastructure. The real signal is the architecture. Invidious doesn't ask YouTube's permission to exist. It reverse-engineers the public interface, strips the surveillance layer, and serves you the content through self-hosted nodes. When Google blocks one instance, another spins up. The network is the product. The "humane tech" badge isn't branding — it's a declaration of intent. Here's why this is the 2026 meta that most people are missing. The creator economy just hit a wall. Monetization is being strangled by opaque algorithm changes, ad revenue collapse, and platform lock-in. Simultaneously, the open-source infrastructure to route around these platforms has quietly matured. Invidious exists. PeerTube exists. Nostr exists. The pipes are ready. While everyone else is debating whether to post Shorts or long-form, a parallel internet is being assembled piece by piece, repo by repo. The catch — and this is what the mainstream tech conversation never addresses — is distribution. Open infrastructure without distribution is a library in the woods. Beautiful. Empty. Invidious solves the consumption layer. It doesn't solve discovery. That's the next frontier, and whoever builds a decentralized recommendation layer on top of this stack owns the next decade of attention. Most people will scroll past this repo and see a niche tool for privacy nerds. What they're missing: every major platform shift in the last 20 years started as a "niche tool for nerds." RSS. Bittorrent. Email encryption. The pattern is always the same — the infrastructure arrives years before the mainstream moment. The people who understood the infrastructure early built the products that captured the wave. The open-source YouTube alternative wasn't the story. The story is that the replacement stack for the attention economy is already built, already running, already global — and almost nobody building consumer products is paying attention to it. Everything else is cope.

• 
  uncomfy (@uncomfy____) reported 21 minutes ago

  @schmayterling @github github so slow today. i cant load ****

• 
  JoshXT (@JoshXT) reported 22 minutes ago

  @FrancescoCiull4 Opus 4.6 was the true king before they removed it from GitHub Copilot and Claude Code. Using 5.5 for long running back end tasks and Opus 4.7 for UI work. Opus 4.7 constantly drops the ball and is not thorough at all, terrible experience vs 4.6 and GPT-5.5 is worse at UI than me

• 
  Oluwamayowa (@oluwamayowa) reported 24 minutes ago

  Most product teams do not have a roadmap problem. They have an evidence problem. Support tickets, call notes, reviews, analytics, Slack threads, GitHub issues, surveys... The signal exists, but it is scattered. That is what Vyrric is built to fix.