The launch handed Cursor an accidental demonstration of its own pitch. The harder question for engineering leaders is what happens to repositories stored on a platform that a rocket company finished buying three days earlier.

Cursor began rolling out Origin, its own code-hosting platform, to paid users on the morning of Monday, August 17. Roughly three and a half hours later, GitHub opened an incident that would run for close to eight hours and take down pull requests, issues, Actions, and enterprise single sign-on.

Product launches are locked weeks ahead, and nothing suggests Cursor knew what was coming. The coincidence still did the company an enormous favor, because it acted out the argument Origin exists to make.

What Origin actually does

Origin lives in a new Codebase tab inside the Cursor client. Teams name a codebase, which becomes part of every repository URL, then push over a command line tool. Repositories, pull requests, code browsing, and GitHub sync shipped on day one. Cursor says agent-native features are coming, without giving specifics.

Pull requests carry the machinery you would expect: a timeline, commits, checks, and a files-changed view with inline comments and merge.

The integration story is where the launch gets more interesting than a straight GitHub clone. Developers connect a GitHub organization, choose which repositories to sync, and Cursor pulls them in. Synced repositories update in real time. Comments move in both directions, so a reply posted on GitHub surfaces inside Cursor within seconds, and a review assigned on GitHub can be merged from Cursor.

One line in Cursor's own changelog undercuts the rival framing that much of this week's coverage adopted. On synced repositories, pushes still go to GitHub, "which stays the source of truth for anything started there."

Origin is currently a layer on top of GitHub for existing work, and a full host only for repositories created inside it. That is a deliberately low-risk entry point, and it is also the reason adoption numbers will be hard to read for a while.

Three app integrations shipped at launch. Vercel handles preview deployments, so connecting it from a repository's Apps tab gives every pull request its own deploy. Depot and Buildkite cover CI, and both run existing GitHub Actions workflows, which lowers the switching cost further.

The outage, by GitHub's own numbers

Coverage this week has cited durations between six and seven hours. GitHub's status page puts the final figure higher.

The company logged the incident running from 13:28 to 21:15 UTC on August 17, a span of seven hours and 47 minutes. Peak error rates reached roughly 20% across web and API traffic. Archive and raw-content downloads failed at closer to 50%, which is the number that broke package installs and Docker builds pulling files from raw GitHub user content.

SAML and OIDC authentication went down alongside SCIM provisioning and Team Sync, locking enterprise users out entirely. Copilot degraded too.

GitHub attributes the recovery to its Central US datacenter coming back. Most services returned by 16:36 UTC. Actions stayed degraded until around 18:03, and the Copilot Token Service did not fully recover until 21:02.

Vercel CEO Guillermo Rauch noted on X that developers could now host repositories in Origin and deploy to Vercel through it, on a platform itself hosted by Vercel.

A reliability record that predates this week

The August 17 incident was not an outlier.

Between May 2025 and April 2026, incident monitoring service IncidentHub tracked 257 separate incidents on GitHub, of which 48 were classified as major outages. That works out to roughly one significant disruption per week. February 2026 was the worst month on record at 37 incidents. Actions, the CI/CD system whose failure freezes an entire engineering workflow, absorbed 57 outages in that 12-month window.

For comparison, GitHub logged 119 service incidents across all of 2024, with 26 major ones.

GitHub's official status page reports 99.79% uptime against an industry norm of 99.9%. An unofficial tracker built by researcher Marek Šuppa, which recomputes the figures from GitHub's own per-service status reports rather than accepting the headline average, put measured uptime over a recent 90-day window at 84.88%.

Writing for LeadDev in May, Charles Humble reported that the reliability problems had triggered "a visible exodus of high-profile users." The Zig programming language project moved to Codeberg in December 2025. Mitchell Hashimoto, a HashiCorp co-founder and early GitHub adopter, kept a journal marking every day an outage blocked his work, found almost every day marked, and announced that his Ghostty terminal emulator would leave the platform. GitHub's chief operating officer apologized to him publicly on X.

The loop GitHub helped build

GitHub CTO Vlad Fedorov has been direct about the cause. The platform was not built for the scale now being demanded of it. GitHub started executing a plan in October 2025 to raise capacity tenfold, and by February 2026 concluded it needed to design for 30 times current scale instead.

The driver he names is agentic development. Repository creation, pull request volume, API usage, and large-repository workloads have all climbed sharply since late 2025.

There is an irony in that which is hard to miss. Copilot arrived as a technical preview in June 2021 and became the first AI coding tool to reach mainstream professional adoption. GitHub built the market, evangelized the workflow, and trained a generation of developers to depend on it. The platform is now straining under the automated volume that followed.

Freelance developer David Bushell described the result as GitHub effectively DDoSing itself with low-quality generated code and pull requests.

Not every incident fits the scale narrative. An April 23 failure came from an incomplete feature flag that let an ungated code path reach production, silently reverting changes across 2,092 pull requests in 658 repositories. Monitoring missed it because the service stayed available and the problem was merge correctness. Customers reported it first.

Software engineering SVP Jakub Oleksy said in June that structural changes were underway to "permanently remove failure modes." GitHub is migrating infrastructure to Azure to cut shared failure points, though only a minority of traffic had moved as of earlier this year.

The question the launch coverage skipped

Three days before Origin shipped, SpaceX closed its acquisition of Anysphere, Cursor's parent company.

The deal was confirmed in an SEC Form 8-K dated August 14. SpaceX subsidiary X67 Inc. merged into Anysphere, with Anysphere surviving as a wholly owned subsidiary. Cursor stock converted into 389,289,254 SpaceX Class A shares against an implied $60 billion equity value, priced on a seven-day volume-weighted average. The merger agreement had been signed June 16. Cursor now sits inside a SpaceXAI division.

That timing matters more than the product tour.

Origin rolled out opt-out rather than opt-in. It went live automatically across every paid tier, Enterprise included, excluding only those organizations whose administrators had explicitly declined. Reporting this week found no published policy covering data retention, residency, subprocessors, or training use for code stored in Origin specifically.

VentureBeat's assessment of the gap was blunt: "a product page is not a contract."

Reporting has also described Grok 4.5 as fine-tuned on Cursor developer session data. Whether repository contents fall under any similar arrangement is exactly what the missing terms would answer. Engineering organizations under contractual confidentiality obligations to their own customers now have a procurement question that did not exist a week ago, and it lands during a beta that enrolled them by default.

The scale gap is still enormous

GitHub's Octoverse report counted roughly 180 million developers on the platform as of last October. It launched in 2008, was acquired by Microsoft in a $7.5 billion stock deal announced in June 2018 and closed that October, and remains the largest source-code host in the world by a wide margin.

Cursor is not close to that, and Origin is in early beta on paid plans only.

What Cursor has that GitHub's previous challengers lacked is a distribution channel it already owns. Roughly two-thirds of the Fortune 500 have developers using Cursor, and the company reported around $2.6 billion in annualized revenue by June 2026. Origin does not need developers to migrate. It needs them to click sync inside an editor they already have open.

Andrew Nesbitt, a former GitHub employee who has spent a decade working on open source infrastructure, argues the replacements are aiming at the wrong target. Individual developer workflow problems are already being solved by other tools. The capability nobody is rebuilding is the one only a platform at GitHub's vantage point could offer: visibility into how projects depend on each other, what happens when a maintainer goes quiet, and whether a change is about to break thousands of downstream repositories.

Origin does not address that layer either.