Cursor Origin, the new code-hosting platform from the AI coding startup, launched this week into a market suddenly looking less settled than it has in years. GitHub, which counts some 180 million developers on its platform as of last October, is struggling with a reliability record that is growing harder to defend, and Cursor is making its move.
What Cursor Origin Code Hosting Actually Offers
Origin covers the basics developers expect: repositories, pull requests, and code browsing. According to the Cursor Origin changelog, the platform is rolling out in early beta to all paid plan users, excluding enterprise organisations whose admins opt out.
Crucially, Cursor is not asking developers to burn their GitHub accounts on the way in. Origin is designed to run alongside GitHub: connect your GitHub account, pick an organisation, and your existing repos sync across. ‘Your GitHub repos can sit alongside the ones Cursor hosts,’ the company says in its Origin launch blog post. That interoperability lowers the switching cost to nearly zero, which is a sensible way to get developers through the door without forcing a commitment.
Cursor describes Origin as ‘designed for agent scale’, with agent-native features listed as coming soon. An ‘app ecosystem’ is also in the works, though details remain sparse. The company’s pitch to enterprise buyers already carries some weight: the Cursor homepage states the product is trusted by over half of the Fortune 500 to accelerate development securely and at scale.
The ambition is framed in fairly unambiguous terms. ‘Origin is not an experiment,’ the company writes in its launch post; ‘it is the result of many decades of experience building these same systems, from people who deeply understand the magnitude of the challenges involved.’ Whether that confidence is earned is a separate question, but Cursor is at least not hedging its language.
GitHub’s Outage Problem, by the Numbers
The timing of the launch was, charitably, fortunate. On the same day Origin went live, GitHub suffered a worldwide outage lasting over six hours, with a nearly 20% error rate reported globally. It was not a one-off.
Between May 2025 and April 2026, LeadDev, citing IncidentHub data, tracked 257 GitHub incidents, of which 48 were classified as major outages: roughly one significant disruption per week. February was the worst single month on record, logging 37 incidents. GitHub Actions, the CI/CD service baked into countless engineering workflows, was the hardest-hit component, suffering 57 outages in the same 12-month window. An Actions failure does not just inconvenience developers; it can freeze an entire deployment pipeline.
The root cause of the most recent major failure, per the GitHub status page, was network saturation on load balancers in its Central US region. A new traffic peak caused an Istio sidecar pod to hit its concurrency limits; a misconfigured auto-scaling policy meant it could not recover. Four HAProxy nodes then exhausted their flow limits, degrading the gateway authentication path and causing widespread authentication latency across the platform.
Recovery was complicated further by a pair of collateral problems. A wave of scraping attacks hit codeload endpoints during the incident, and a latent retry bug in VS Code amplified traffic by approximately 10x, delaying restoration of the Copilot Token Service. These are the kinds of compounding failures that erode trust faster than any individual outage does on its own.
LeadDev’s Charles Humble described the pattern as producing ‘a visible exodus of high-profile users.’ That may be overstated, given GitHub’s sheer scale, but the direction of sentiment is not hard to read.
The Scale Problem Cursor Still Has to Solve
GitHub was founded in 2007 and acquired by Microsoft in 2012. It remains the largest source-code host in the world by a wide margin, and 180 million users do not migrate on the strength of a beta launch, however polished.
Cursor’s business momentum is real. The Cursor blog cites Bloomberg reporting that the company’s recurring revenue doubled in three months to $2 billion, a figure that reflects how quickly its AI Code Editor has taken hold in professional development teams. Origin is a natural extension of that footprint: if developers are already writing code inside Cursor, hosting it there too is a short step.
Still, Cursor Origin code hosting faces a gravitational pull that is hard to overstate. GitHub’s integrations, its Actions marketplace, its social layer, and its institutional familiarity are not dismantled by a competitor offering sync-and-interop. Cursor’s smartest move may be to stay in co-existence mode long enough for GitHub’s reliability record to do the persuading for it.
The next stress test for that thesis is February. If GitHub’s worst month on record repeats itself, Origin’s early beta waitlist may start looking rather less exclusive.
