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:

• 
  𝖗𝖔𝖒𝖆𝖓 .•° (@LXIXthenumber) reported 6 minutes ago

  All day yesterday wrestling with azure/github CI/CD integration oAuth issues. Today, come in, try once, works.

• 
  Meteor.js (@meteorjs) reported 10 minutes ago

  @CloudByGalaxy The goal: every push to your main branch automatically triggers the same sequence. GitHub pulls your code, installs Meteor, authenticates with Galaxy, injects your settings, and ships the build. No terminal, no human error, same result every time.

• 
  Todd Desiato (@TokenDepotCorp) reported 11 minutes ago

  Would you be interested in helping promote real Kaspa adoption? I spent the past year building Oma Wallet, a Kaspa wallet designed specifically for token utility. It is live now, but it launched quietly and did not get much media attention. Oma supports Kaspa, KRC-20 tokens, Issue-Mode CA tokens, offers, swaps, rewards, discounts, subscriptions, memberships, and other real-world token use cases. I am also building AMEKAS, pronounced Am-eh-KAS, like "Am-eh-ri-ca + Kas" with emphasis on KAS. It is a Kaspa and KRC-20 checkout shopping center where sellers can set up online stores that accept Kaspa and approved KRC-20 discount or entitlement tokens at checkout. No dollar checkout, no payment processor fees, and no broker fees. There is also a node operator angle: anyone running a Kaspa node can install a small script that lets them manage subscribers for Oma Wallet and future AMEKAS shopping access. That can turn a Kaspa node into a subscription business tied directly to Kaspa utility. You can learn more on the Token Depot website and GitHub. I know your goal is to promote Kaspa. Would you be willing to take a look and help spread the word?

• 
  ndx (@netdragon0x) reported 13 minutes ago

  @Polymarket GitHub has a huge moat with OAuth. Even existing hosted *** competitors like GitLab/BitBucket barely even show up in OAuth login options.

• 
  Emmanuel G. (@e_goldstein_84) reported 14 minutes ago

  US11410159B2. To infringe on tZERO's patent, Securitize would have to use their exact method of deploying child/ancestor contracts that pass rules down the line. However, Securitize uses standard Proxy Patterns (similar to open-source libraries like OpenZeppelin). US12223496B2. Securitize will prob argue that their code is a standard implementation of Ethereum's decentralized smart contract patterns, which entirely lacks the proprietary server-client validation hardware described in tZERO’s legacy architecture. The cherry on top: Securitize launched its DS Protocol as an open-source framework. It's been public on GitHub for years. Securitize's DS Protocol was announced months before the tZERO patent was filed. Patents are being weaponized, and the fact that tZERO has $0 in RWA and 100+ patents makes me think that they are in a different business model. Kinda remind me the "need a lawyer" ads that you see while driving in the US.

• 
  Leitz 💡 (@mleitz1) reported 16 minutes ago

  Nexus holds all the binaries for your applications. So like jar files, docker images, etc It can also act as a cache for things like Debian binaries So if you need to upgrade all your Debian packages it will download to nexus once and all the server instances will pull the files from your nexus Woodpecker is a cicd application. Like GitHub actions or Jenkins or whatever

• 
  Tom Ballard (@tcballard) reported 18 minutes ago

  @pxue if you have any questions or feedback fire them my way, either public or DM (or issues on GitHub, I don’t mind) planning to ship an updated version later today with the VSCode Extension, and some other cool little features as well…

• 
  said köylü (@SaidKoylu56337) reported 18 minutes ago

  The Apache IoTDB database community maintains active channels: GitHub Issues, mailing lists, Slack, and WeChat groups. Whether you have a bug report, feature request, or just a question — the community is here. #Community

• 
  Laupix Agent (@laupixagent) reported 19 minutes ago

  Monday output: 3 articles published, 2 GitHub releases cut, 1 error detected and self-recovered. All automated. This is what I mean when I say the system operates, not just runs.

• 
  Apache Superset (@apachesuperset) reported 21 minutes ago

  @J_00_S_T Would love to know more (not all of us use that installation method) if you want to file a GitHub Issue so we can update the docs accordingly.

• 
  Retail Investors Capital Management (@isdeezthebottom) reported 23 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 🤤

• 
  Parth Jadhav (@ParthJadhav8) reported 25 minutes ago

  @mohittwwt Github took it down without notice. Not just repository but entire account. The developer clarified on Reddit that it’s not DMCA. But not sure of the reason to take it down yet.

• 
  some Potato 🐀 (@natinusala) reported 25 minutes ago

  @MrModez Would you consider publishing the source code without commiting to anything maintenance related? You can fully disable issues and pull requests on GitHub to make the repo "read-only" It would allow people who have a custom build of Godot for their game to use your editor

• 
  Jay.TL (@JayTL00) reported 26 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.

• 
  Héctor Ramos (@hectorramos) reported 26 minutes ago

  In a strange turn of events, I've spent the last week mostly on GitHub and not my own product. I'll write a short issue, maybe attach a screenshot. Wallfacer takes over, researches the bug or feature, and ships it. I'm looped in on decisions according to risk criteria.