Cursor Launched Its GitHub Rival Mid-Outage. The Outage Broke It.

TL;DR

On August 17, Cursor shipped Origin, its "git forge for the agentic era," in early beta for paid plans: hosted repos, pull requests, reviews, and merges, with real-time bi-directional GitHub sync. The same day, GitHub logged a critical incident that ran 7 hours and 35 minutes and degraded Git operations, Actions, pull requests, and Copilot, with error rates around 20% on web and API traffic. Cursor's launch post hit Hacker News while the incident was still open. Then came the punchline: Cursor's own status page declared Origin degraded, because Origin's onboarding path starts with syncing your repos from the service it is trying to replace.

Seven hours and thirty-five minutes of critical

GitHub's incident opened at 13:40 UTC and did not resolve until 21:15 UTC. The status page lists eight affected components: API requests, Issues, Pages, Git operations, webhooks, Actions, pull requests, and Copilot, which was the first to hit "major outage." Copilot going down first, on the day an AI company launched a GitHub competitor, is the kind of detail a fiction editor would reject as too neat.

The numbers from GitHub's own updates: error rates "around 20% for web experiences and api traffic," roughly 50% on archive downloads, and knock-on failures in SAML and OIDC authentication, SCIM, and Team Sync. GitHub says a root cause analysis is coming.

Developers did not wait for it. Nineteen minutes into the incident, an Ask HN thread titled "Alternatives to GitHub" went up: "Github has been down consistently over the last few months - does it make sense to switch to alternatives?" It collected 522 points and 334 comments. About three hours later, Cursor answered the question with a product.

What Origin actually is

Origin was announced at Cursor's Compile conference on June 16 and went live on August 17 as an early beta on Pro, Teams, and Enterprise plans, per the changelog. It is a full code host: you create or mirror repos, clone and push over regular git, and get a browser view with code search under a new Codebase tab.

The docs describe pull requests with the timeline, commits, checks, and changed files you would expect, plus a detail that explains the whole product: agents are first-class actors. They can "answer, make changes, update PRs, or push a branch" directly on the forge. CI and deploys route through integrations with Vercel for preview deployments, Depot, and Buildkite.

The pitch is that a forge built when humans wrote every commit does not fit a world where most commits come from agents. Cursor's cloud agents already spin up environments and grind on tasks for hours; giving them a code host that lives next to the compute, instead of on the other side of GitHub's API rate limits, is the infrastructure version of moving in with your employer. The timing has extra weight: SpaceX closed its $60 billion acquisition of Cursor's parent Anysphere on August 14, three days before launch.

Step one: sync from GitHub

Cursor's own launch line is candid about the migration path: "It's fast, easy to use, and deeply integrated with Cursor. Get started by syncing your repos from GitHub." Origin does not ask you to leave GitHub. It mirrors your repos with real-time bi-directional sync, down to pull request comments flowing both ways.

That is the sane adoption strategy, and on launch day it was also the trap. At 14:34 UTC, Cursor opened an incident: "a service degradation affecting Automations, Cloud Agents, Review Agents and Codebase related to a GitHub degradation." The affected-components list included Origin itself. The new forge spent roughly six hours of its first day degraded because the incumbent it replaces was down. It is like opening a rival bank across the street where the only way to fund an account is a wire from the bank that is currently on fire.

The lesson generalizes past Cursor. Mirror-first migration means GitHub stays your source of truth and its availability stays your availability. Until teams flip the primary remote, every "GitHub alternative" onboarding via sync inherits GitHub's uptime, minus its own.

How bad was the day, by the numbers

GitHub's published error rates put the incident in the serious-but-not-total class: roughly one in five web and API requests failing at peak, one in two archive downloads. If your CI cloned tarballs, August 17 was a coin flip.

Before you move your remote

Straight-faced caveats. Origin is an early beta with a gradual rollout, so a paid plan does not guarantee immediate access. Free plans are excluded entirely. Teams still on Cursor's legacy privacy mode cannot enable it at all. And a code host earns trust in years, not launch weeks: GitHub's bad afternoon still ended with GitHub holding effectively all of the world's repos, including the ones Origin mirrors.

There is also an obvious custody question. Your code now sits on infrastructure owned, as of last week, by SpaceX. For some shops that is a shrug; for others, "my repos live with a defense contractor" is a compliance ticket waiting to be filed.

Key Takeaways

• Cursor launched Origin on August 17: hosted repos, PRs, reviews, and merges built for agents, in early beta on paid plans.
• GitHub had a critical incident the same day, from 13:40 to 21:15 UTC, with ~20% error rates on web and API traffic and ~50% on archive downloads.
• Cursor's own status page listed Origin as degraded for roughly six hours, because onboarding depends on syncing from GitHub.
• Origin's model is mirror-first with real-time bi-directional sync, so GitHub remains the source of truth, and its outages remain your outages.
• Agents are first-class on Origin: they can answer reviews, update PRs, and push branches, with CI via Vercel, Depot, and Buildkite.
• The launch came three days after SpaceX closed its $60 billion acquisition of Cursor's parent Anysphere, which puts code custody questions in play.

Sources: Cursor changelog, Cursor docs: Origin, cursor.com/origin, GitHub status incident, Cursor status incident, Ask HN: Alternatives to GitHub, TechStartups