Product4 distinct publishers3 min readPublished Updated
Origin arrives opt-out on every paid Cursor plan with no published terms on retention, residency or training use. GitHub's reliability record is what makes the pitch land.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
Cursor began rolling out Origin, its own code hosting platform, on Monday morning, and about three and a half hours later GitHub degraded for six hours and forty-two minutes [1][2][3]. The sequence was coincidence, not choreography, but it put a code host inside the editor on the same day the incumbent stopped working [23].
GitHub first reported performance issues around 9:40 a.m. EDT and the incident resolved at 20:22 UTC [26][3]. Error rates ran about 20% on pull requests, issues and the API, and about 50% on archive and raw file downloads [4]. Enterprise single sign-on went with it, so SAML, OIDC, SCIM provisioning and Team Sync all failed [5]. Copilot and Actions degraded, and minor outages hit other Microsoft services including Teams [6]. GitHub supports roughly 180 million users [26]. It was the seventh incident on GitHub's status page in fifteen days, a rate of roughly one every two days [7][1].
The pattern is what changes procurement conversations. An analysis by LeadDev counted 257 GitHub incidents between May 2025 and April 2026, 48 of them major, with GitHub Actions alone accounting for 57 outages in twelve months [8]. GitHub chief technology officer Vlad Fedorov has said the platform never anticipated its current scale, and an April engineering post conceded the company had failed to meet its own reliability standards [9]. There has been no chief executive since Thomas Dohmke resigned a year ago; Microsoft folded the unit into its CoreAI organisation [10]. David Uzondu wrote at Neowin that GitHub has not managed a clean month all year [11]. Zig moved to Codeberg in November and Mitchell Hashimoto said in April that Ghostty would follow [12], and The Information reported that OpenAI started building its own alternative partly because outages left engineers unable to commit [13].
Origin is Cursor's first major product update since its $60 billion sale to SpaceX in June [14]. It appears as a new tab in the desktop client with a dedicated command line tool [15], and provides repositories, pull requests, code browsing and search [16]. The design decision that matters is what it does not require. You connect an organisation, pick repositories, and they sit alongside Origin-native ones, with permissions mirroring GitHub's existing read and write settings [17]. Pushes keep going to GitHub, the changelog says GitHub remains the source of truth for anything started there, and pull request comments sync both ways within seconds [18]. Depot and Buildkite run existing GitHub Actions workflows unchanged, and Vercel handles preview deployments [19]. That is a read-mostly mirror rather than a migration, which is exactly why it can be approved without a migration project.
The governance gap is the part to read twice. Origin reaches all paid plan users from Monday, except enterprise organisations whose administrators opt out [20]. Cursor has published nothing on retention, residency, training use, subprocessors or migration tooling [21]. For firms that have never ruled on whether proprietary code may sit on a new host, the default has now made the ruling.
The agentic case is not decoration. Cursor pitched Origin in June as a git forge for the agentic era, with a demo running agents at 22.6 commits per second against one repository [22]. RuntimeWire reported that autonomous cloud agents now open 35% of the pull requests merged inside Cursor [24], and Cursor's cloud agents keep working when a developer's workstation is off [25]. Google's 2025 DORA report found AI adoption tracking positively with delivery throughput and negatively with delivery stability [27], while Stack Overflow's survey of 49,009 developers found trust in AI accuracy falling to 33% from 43% [28].
Watch whether Cursor publishes data terms before enterprise security teams finish their reviews, whether GitHub's incident cadence holds through the next fifteen days, and what the unspecified "agent-native features" Cursor has promised turn out to require [29].
Ranked by verification strength, evidence, and original report placement.
Cursor started rolling out Origin, its own code hosting platform, on Monday morning.
About three and a half hours after Cursor's Origin rollout began, GitHub fell over.
GitHub's degradation ran six hours and forty-two minutes, resolving at 20:22 UTC.
At peak, GitHub error rates hit roughly 20% on pull requests, issues and the API, and about 50% on archive and raw file downloads.
No evidence suggests Cursor timed the Origin launch to the GitHub outage; Cursor employee Matt Palmer quote-tweeted the launch saying the company meant to ship earlier but GitHub was down, and companies lock launches weeks ahead.
Enterprise single sign-on failed during the outage, including SAML, OIDC, SCIM provisioning and Team Sync.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Outage and launch well corroborated; product and governance detail single-sourced
Two independent publishers document the GitHub outage with consistent error-rate and service-impact figures, and two independently document the Origin launch and its GitHub sync and partner connectors. The claims that carry the story's edge — opt-out enrolment across paid plans, absent retention/residency/training-use/subprocessor terms, the seven-incidents-in-fifteen-days count, the 35% agent-authored PR share, and the launch-before-outage sequence — rest on a single publisher relaying its own reading of Cursor's changelog and third-party reports (LeadDev, RuntimeWire, The Information). Nothing in the cluster contradicts these, but nothing independently confirms them either.
Distribution granted by default; no usage evidence yet
Origin's distribution is broad by construction — every paid Cursor plan from day one, opt-out only — and launch integrations with Vercel, Depot and Buildkite are in place. But the cluster contains zero evidence of repositories actually hosted, teams migrated, or Origin usage of any kind, and the design explicitly keeps GitHub as source of truth, so availability is not yet substitution. Real adoption signal in this cluster belongs mostly to the surrounding trend: Zig and Ghostty leaving GitHub, OpenAI reportedly building an alternative, and 35% of merged Cursor pull requests already opened by cloud agents.
Framing overstates displacement; the product is a mirror
The prevailing framing — a GitHub competitor launched into GitHub's collapse, with the outage as 'the opening' — runs ahead of the mechanics. Origin keeps pushes on GitHub, inherits GitHub permissions and treats GitHub as source of truth, and no usage figures exist for it. The Next Web itself corrects the most inflated version of the story by establishing that Origin shipped roughly three and a half hours before the outage and that no evidence suggests timing. Offsetting the overstatement: GitHub's incident record, its own admissions and the opt-out default are concrete and, if anything, under-emphasised relative to the launch narrative, which keeps the gap modest rather than large.
Vendor-favourable timing, vendor-sourced detail, new owner
Cursor benefits directly from the coincidence: a launch that a GitHub outage advertised for free, on a product enrolled by default across paid plans, published as the first major release under a $60 billion SpaceX ownership that also supplies the models its agents run on. Much of the descriptive detail traces to Cursor's own changelog and documentation, and the absence of published data terms is itself a commercially convenient silence. Publisher incentives are visible too: one publisher ran conventional launch coverage sourced largely to the vendor, another built an analytical frame around the outage-plus-launch juxtaposition that travelled widely on social media.
Facts firm, consequences unresolved
High confidence that the outage happened at the reported scale and that Origin shipped default-on with the described compatibility design — those rest on corroborated or specific, checkable statements. Lower confidence on what follows: no Origin usage data, no published data terms to evaluate, no GitHub root-cause disclosure yet, and second-hand sourcing for the incident tallies and agent-PR share. The direction of the story is credible; its magnitude is not yet measurable from this cluster.
invest
Cursor ships Origin to paying users as GitHub's outage count reaches 2571 distinct publisher
build
Cursor ships Origin default-on to every paid seat1 distinct publisher
build
Grok 4.6 lands in Copilot two days after launch, and the model picker becomes a procurement problem1 distinct publisher
build
GitHub's autoscaler watched the wrong meter, and auth, CI and Copilot fell together3 distinct publishers
Distinct publishers with included, body-backed reporting in this cluster.
devops.com
3 articles · August 19, 2026
siliconangle.com
1 article · August 17, 2026
techcrunch.com
1 article · August 18, 2026
thenextweb.com
1 article · August 17, 2026