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:

• 
  Ronald Mannak (@ronaldmannak) reported 1 minute ago

  This is actually solving a real issue. I (a single developer) run into GitHub api limits multiple times a day and it’s super annoying. My agents literally have to wait for a GitHub rate limit reset

• 
  l-lacker (@llacker_ru) reported 6 minutes ago

  @telegram 11/12 So yes, this is what Telegram is turning into: → support black hole → rushed updates → inconsistent official clients → memory leaks → broken AI bot features → delayed GitHub source drops → Fragment money stuck with no answer

• 
  Ale 𝕏 (@SirAlexthomson) reported 6 minutes ago

  This is actually a pretty big move. Cursor has been eating GitHub Copilot’s lunch for a while now, and this feels like they’re doubling down on becoming the default AI coding environment. If they keep improving at this rate, GitHub is going to feel real pressure. Copilot was the early leader, but Cursor is moving faster on the agentic side. Interesting to watch.

• 
  Geoff Langenderfer (@geoff_l) reported 8 minutes ago

  @petergyang @GergelyOrosz it's evaluating llm performance on known github issues you have a github issue with an attached code change. The llm makes an attempt and you compare it to the known good code diff.

• 
  Will Lehnertz (@lehnertz85) reported 9 minutes ago

  @mrloldev @cursor_ai If CI is good for multiplatform, I might move my projects to it. I like the name. github has been slow lately.

• 
  ᵀᴱᵁᴿᴱˣˣ⁹⁸⁰⁰- (@TRX9800_) reported 12 minutes ago

  @itsauroraeeeee Hot take honestly Browser is extremely easy to replace, but Discord? So many project discussion happens only in discord. Some project.maintainer closes issues saying resolved in discord Like mf why are you even on Github

• 
  Kirtesh (@AKirtesh) reported 15 minutes ago

  𝗧𝗼𝗽 𝟭𝟮 𝗧𝗵𝗶𝗻𝗴𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗛𝗮𝘃𝗲 𝗶𝗻 𝟮𝟬𝟮𝟲 📌 1. Cursor (AI Code Editor) 2. Claude 4 Subscription 3. Notion (Second Brain) 4. Raycast (Mac Productivity) 5. GitHub Pro 6. Supabase / Neon Postgres 7. Vercel / Railway Account 8. Figma (Design) 9. Linear (Issue Tracking) 10. Arc Browser 11. Wise Account (Payments) 12. A strong personal domain Save this. 📌 What’s missing in this list? 👇

• 
  Retail Investors Capital Management (@isdeezthebottom) reported 18 minutes ago

  @zerohedge $ORCL refused to make the effort to comply with $MSFT’s request for a specific standard. Coming from $MSFT this is rich: from Plasma and regression bugs which where supposed to be fixed in 2024, to infecting everyone with Mini Shai Hulud and Hades trough VS Code and GitHub pipelines, to their private GitHub repositories being leaked and BitLocker being extremely easy unlock. Not to mention the need to change MFA mechanism because people would be locked out of their accounts and scammed to change Azure passwords by attackers 🤭and their security policy is: “responsible disclosure” - IE. Don’t say anything about vulnerabilities that might be exploited by attackers, even if there are ways to mitigate until they figure out how to fix them (in a few months or so, if not years). $MSFT can’t talk about “security” until they change their ways of thinking 🤤

• 
  Stefanescu Liviu (@liviusa) reported 19 minutes ago

  @swyx @TomasReimers @cursor_ai What's wrong with ***? Maybe github has some availability problems, true, but *** is fine, need to see what's different and better

• 
  Iprashant10 (@Iprashant10) reported 19 minutes ago

  Dear ministry of IT, Scammers are using Outlook, JIRA, Github, MS teams to circulate the NEET paper. Kindly issue a ban on the lines of telegram.

• 
  AcceptÐoge (@DogeAccept) reported 19 minutes ago

  @BuildrJ @DogeOS to start: 2025/09/15, you blocked me for asking you about the zk L1 proposal that Jordan submitted to the $doge project's repository on Github. Prior, Jordan also blocked me for asking about his proposal that's been there for a year. Is there an issue in talking about L1?

• 
  Jay.TL (@JayTL00) reported 21 minutes ago

  Cursor just announced Origin — a *** forge "built for the agentic era." 11.5K likes on the announcement. Nobody is asking the obvious question: is this a GitHub competitor, or the most aggressive vendor lock-in play since Microsoft bundled IE into Windows? The framing is "code storage and *** hosting." That's deliberately boring. Here's what's actually happening. 1. The review bottleneck, not storage, is the real target GitHub hit 275M commits per week by mid-2026. Claude Code alone generated 5.2M commits in February. Storage isn't the problem — scale is. Cursor's bet is that the bottleneck has moved. Junior hiring at big tech is down 22% this year; senior hiring is up 26%. The constraint is no longer generating code. It's reviewing it. Origin isn't competing on hosting features. It's competing on whether the review layer itself should be agent-native — where agents review agents, not humans reviewing agents. 2. The vertical stack is the actual product Think about what Cursor now controls after the SpaceX acquisition: - The editor (Cursor IDE) - The agent models (Composer, Fable integration) - The code storage (Origin) - The review pipeline (auto-review, already default for new users) That's not a tool. That's a platform. The last company to own the editor, the runtime, the storage, and the review surface was Microsoft in the Visual Studio era — and they used that stack to lock in an entire generation of enterprise developers. Origin's landing page says nothing about *** compatibility or migration. It says "join the waitlist." That silence is the strategy. 3. "Agent-native" is doing heavy lifting The phrase "a *** forge for the agentic era" sounds like marketing. It's the entire thesis. Traditional *** forges assume a human writes, a human pushes, a human reviews, a human merges. Origin assumes the opposite: an agent writes, an agent pushes, an agent reviews, an agent merges. The human shows up for the 5% of decisions that need judgment. This is why Origin handles 22+ commits per second and 290K+ clones per hour. Those numbers sound like infrastructure specs. They're actually throughput assumptions — Cursor is designing for a world where commit velocity is 100x human speed and the forge has to absorb it without breaking the review queue. But here's what most people missed: The lock-in isn't technical. It's economic. Once your agents are trained on Cursor's review patterns, your code review history lives in Origin's format, and your team's workflow is tuned to Cursor's auto-review classifier (97% accurate, already default), migrating away means retraining your entire agent fleet on a different review surface. You won't switch because you can't. Not because of lock-in. Because the switching cost is measured in agent retraining cycles, not in developer hours. GitHub's moat was 100M developers who learned its UI. Cursor's moat will be agents that learned its review grammar. The real question isn't whether Origin is better than GitHub. It's whether we're about to let one company own the entire code lifecycle — from generation to storage to review — at the exact moment code is becoming the most valuable asset class in the economy. We've seen this movie before. It didn't end well for developers last time.

• 
  Eneko (@iameneko) reported 22 minutes ago

  Two things on this: 1 . I hope this becomes a real competitor to Github. At minimum, real competition is needed here. They way they are managing github is terrible 2. So now xAI and cursor will have github equivalent code data? Maybe composer will need more attention than ever.

• 
  JT Koffenberger (@DMVG_JTK) reported 23 minutes ago

  Microsoft spent years promising AI coding agents would change everything. They were right — the agents got so good at hammering GitHub that they basically DDoS'd the mothership. 275 million commits a week. Nine service-degrading incidents in May. Availability slipping under 99%, which in SLA terms is the polite corporate way of saying "we'll get to it." So Microsoft did the only thing a trillion-dollar company can do when its own platform is on fire: it called Amazon. Yes — the company that owns GitHub, owns Azure, and built Copilot is now routing traffic to AWS, its biggest cloud rival, because the robots it shipped ate the house it built them in. Somewhere a Microsoft VP is explaining to the board why the cloud invoice now has a competitor's logo on it. The machines didn't take our jobs. They took down the repo. #DevOps #AI

• 
  troy (@RobloxVoiceChat) reported 24 minutes ago

  @w1nthinker @Aspernator I had originally planned on publishing it to GitHub, but since this is decompiled code, I don't own it and I don't want to get in trouble with Roblox. Then again, other people have gotten away with publishing unlicensed code (see: Satchel, which copies Roblox's backpack code)