When your competitor's infrastructure fails the exact day you launch, you don't need a marketing budget.
The Summary
- Cursor launched Origin, its code hosting platform, on Monday morning; three and a half hours later, GitHub suffered a 6-hour-42-minute global outage with 20% error rates on core features and 50% on downloads
- GitHub's enterprise SSO, SAML, OIDC, and Copilot all failed simultaneously, leaving thousands of dev teams locked out while Cursor's new platform ran smoothly
- Cursor is challenging GitHub's 18-year monopoly on source code hosting with native AI integration, betting developers are ready to rethink infrastructure choices they've treated as boring defaults
- Vercel CEO publicly dunked on GitHub by noting Origin "unlike GitHub, it's online," then admitted his own company was stuck because of the GitHub outage
The Signal
The timing looks suspicious but Cursor didn't orchestrate it. Product launches lock weeks ahead. What matters is that the coincidence crystallized something real: the gap between how critical GitHub is and how fragile it's become. When your entire CI/CD pipeline, authentication layer, and AI coding assistant all fail at once, "industry standard" stops feeling like security.
Origin's rollout to paid Cursor users started Monday morning. By early afternoon, GitHub's status page showed systematic failure across the stack. Pull requests, issues, APIs, enterprise sign-on, and Copilot went dark. The error rates tell the story: 20% on core developer workflows, 50% on file operations. Not a blip. A meltdown.
"A GitHub outage delayed the launch of a GitHub competitor."
The real signal isn't the outage. Stuff breaks. The signal is that Cursor already had native deployment integration with Vercel built into Origin at launch. That's not a hosting platform. That's an end-to-end AI development stack that happens to store code. GitHub invented the social layer around version control. Cursor is betting the next layer is agentic: your editor writes code, your hosting platform understands it, your deployment pipeline acts on it, all without context switching.
For 18 years, source code hosting has been the least interesting infrastructure decision an engineering team makes. You pick GitHub because everyone picks GitHub. Network effects plus Microsoft's bankroll made it unassailable. But AI coding tools create a wedge. If your editor already understands your entire codebase and writes half your functions, why shouldn't it also handle versioning, review, and deployment?
Key advantages Cursor is playing:
- Native AI integration across the full development lifecycle, not bolted on
- No legacy enterprise architecture to support (GitHub's SAML/OIDC failures hurt big orgs most)
- Tight coupling between editor, hosting, and deployment removes handoff friction
Microsoft owns both GitHub and the model infrastructure under Copilot. That should be an advantage. Instead it's created a bloated surface area where six-hour outages take down authentication, storage, and AI at once. Cursor's stack is younger, lighter, and built assuming AI agents are writing the code.
The Implication
Watch what infrastructure developers switch to when the old choice becomes friction. GitHub's network effects are still massive, but AI-native tools create new lock-in points. If Origin can tie your editor, hosting, and deployment together tightly enough, the switching cost reverses. The question stops being "why would I leave GitHub?" and starts being "why am I using three tools when one handles all of it?"
For teams already using Cursor's editor, Origin is a natural evolution. For everyone else, it's a reminder that the tools we assumed were permanent are up for grabs again. The agent economy doesn't just change what gets built. It changes who builds the infrastructure the agents run on.