Cursor becomes a code host by default, and GitHub's seven outages in 15 days is the opening
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
What happened
- 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.
- Enterprise single sign-on failed during the outage, including SAML, OIDC, SCIM provisioning and Team Sync.
Why it matters
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 [5][6][1]. The sequence was coincidence, not choreography, but it put a code host inside the editor on the same day the incumbent stopped working [24].
GitHub first reported performance issues around 9:40 a.m. EDT and the incident resolved at 20:22 UTC [14][1]. Error rates ran about 20% on pull requests, issues and the API, and about 50% on archive and raw file downloads [2]. Enterprise single sign-on went with it, so SAML, OIDC, SCIM provisioning and Team Sync all failed [3]. Copilot and Actions degraded, and minor outages hit other Microsoft services including Teams [4]. GitHub supports roughly 180 million users [14]. It was the seventh incident on GitHub's status page in fifteen days, a rate of roughly one every two days [18][30].
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 [9]. 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 [10]. There has been no chief executive since Thomas Dohmke resigned a year ago; Microsoft folded the unit into its CoreAI organisation [11]. David Uzondu wrote at Neowin that GitHub has not managed a clean month all year [12]. Zig moved to Codeberg in November and Mitchell Hashimoto said in April that Ghostty would follow [20], and The Information reported that OpenAI started building its own alternative partly because outages left engineers unable to commit [21].
Origin is Cursor's first major product update since its $60 billion sale to SpaceX in June [13]. 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 [7]. 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 [8]. Depot and Buildkite run existing GitHub Actions workflows unchanged, and Vercel handles preview deployments [17]. 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 [22]. Cursor has published nothing on retention, residency, training use, subprocessors or migration tooling [23]. 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 [29]. RuntimeWire reported that autonomous cloud agents now open 35% of the pull requests merged inside Cursor [25], and Cursor's cloud agents keep working when a developer's workstation is off [26]. 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 [19].
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence72
- Adoption
- Not scored
- Hype gap+30
- Incentives60
- Confidence65
Perspective Coverage
4 publishers- Builder
- Builder 39%
- Operator
- Operator 34%
- Investor
- Investor 27%
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
GitHub's degradation ran six hours and forty-two minutes, resolving at 20:22 UTC.
- [2]
At peak, GitHub error rates hit roughly 20% on pull requests, issues and the API, and about 50% on archive and raw file downloads.
- [3]
Enterprise single sign-on failed during the outage, including SAML, OIDC, SCIM provisioning and Team Sync.
- [4]
GitHub confirmed degraded availability for Copilot and GitHub Actions, and minor outages were reported across related Microsoft services including Microsoft Teams.
- [5]
Cursor started rolling out Origin, its own code hosting platform, on Monday morning.
- [6]
About three and a half hours after Cursor's Origin rollout began, GitHub fell over.
- [7]
With Origin, a user connects an organisation and picks repositories, which appear alongside Origin-native ones; permissions mirror GitHub's existing read and write settings rather than creating a parallel system.
- [8]
Pushes keep going to GitHub, Cursor's changelog says GitHub stays the source of truth for anything started there, and pull request comments sync both ways within seconds.
- [9]
An analysis by LeadDev counted 257 GitHub incidents between May 2025 and April 2026, 48 of them major, roughly one significant disruption a week, with GitHub Actions alone accounting for 57 outages in twelve months.
- [10]
GitHub chief technology officer Vlad Fedorov says the platform never anticipated its current scale, and an April engineering post conceded GitHub had failed to meet its own reliability standards.
- [11]
GitHub has had no chief executive since Thomas Dohmke resigned a year ago; Microsoft folded the unit into its CoreAI organisation instead.
- [12]
David Uzondu wrote at Neowin that GitHub has not managed a clean month all year.
- [13]
Origin is Cursor's first major product update since its $60 billion sale to SpaceX Corp. in June.
- [14]
GitHub, a Microsoft subsidiary supporting roughly 180 million users, first reported performance issues around 9:40 a.m. EDT on Monday.
- [15]
Origin is accessible via a new tab in the Cursor desktop client's interface and via a dedicated command line interface tool.
- [16]
Cursor Origin provides repositories, pull requests, code browsing and search.
- [17]
Depot and Buildkite run existing GitHub Actions workflows unchanged, and Vercel handles preview deployments for Origin.
- [18]
It was the seventh incident on GitHub's status page in fifteen days.
- [19]
Cursor will add more integrations in the near future and plans to release unspecified "agent-native features".
- [20]
Zig moved to Codeberg in November, and Mitchell Hashimoto announced in April that Ghostty would follow.
- [21]
The Information reported that OpenAI began building its own alternative to GitHub partly because outages left engineers unable to commit.
- [22]
Cursor Origin reaches all paid plan users from Monday, except enterprise organisations whose administrators opt out; it is opt-out, not opt-in.
- [23]
Cursor has published nothing on retention, residency, training use, subprocessors or migration tooling for Origin.
- [24]
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.
- [25]
RuntimeWire reported that agents running autonomously in cloud machines now open 35% of the pull requests merged inside Cursor.
- [26]
Cursor supports desktop-hosted agents and agents running in a cloud sandbox; cloud agents can work on long-horizon coding tasks even when a developer's workstation is turned off.
- [27]
Google's 2025 DORA report found AI adoption tracking positively with delivery throughput and negatively with delivery stability.
- [28]
Stack Overflow's survey of 49,009 developers found trust in AI accuracy falling to 33% from 43%.
- [29]
Cursor announced Origin in June at its first developer conference, pitching it as a git forge for the agentic era; the demo ran agents at 22.6 commits per second against one repository.
- [30]
Seven GitHub status page incidents across fifteen days is a rate of roughly one every two days.
Sources
4 independent publishers whose own reporting we read for this story.
- devops.comGitHub Hit by Widespread Outage, Halting Work for Global Developers
3 articles · August 19, 2026
- siliconangle.comCursor launches Origin code hosting service to compete with GitHub
1 article · August 17, 2026
- techcrunch.comCursor capitalizes on Github frustration, launches rival hosting platform
1 article · August 18, 2026
- thenextweb.comCursor Origin is on by default for paid users, and its data terms are unpublished
1 article · August 17, 2026
Topics and entities
Topics
- Source code data governance
- AI Coding Agents
- Platform Reliability and Incident Response