GitHub Went Down Today. Cursor Launched Its Replacement the Same Day. Both Miss the Point.

A worldwide outage, an "agent-first" GitHub rival named Origin, and why the answer to a failed central repo is not a new central repo.

This morning at 13:40 UTC, GitHub went down worldwide. Not a blip: Pull Requests, Issues, Actions, Webhooks, the API, and Copilot all degraded at once, with error rates around 20% on web and API traffic and roughly 50% on raw repository downloads. It took over three hours to mitigate seven of the eight affected services, and as I write this, Copilot is still marked as a major outage. This is eleven days after GitHub Actions spent ten hours throttled and queueing on August 6.

Also today, in timing you could not script: Cursor launched the early beta of Origin, a code hosting platform built for AI coding agents, positioned directly against GitHub.

So the pitch writes itself: the old landlord's building flooded, and a new landlord is standing outside with keys to a shinier building. Before you sign the lease, it's worth asking why you're renting at all.

What actually broke today

Be precise about the blast radius, because it's bigger than "a website was slow." When GitHub degrades, merges stop. CI stops. Deploys that pull from raw content fail. Webhooks that drive half the automation industry go quiet. And in 2026 there's a new casualty class: coding agents. Every agent workflow that authenticates through GitHub, opens PRs on GitHub, or waits on GitHub checks simply stalled. Most of a working day, worldwide, because one company's infrastructure had a bad morning.

That's not an indictment of GitHub's engineers, who run one of the most heavily loaded services on earth. It's an indictment of the topology. One origin, everyone downstream.

Enter Cursor's Origin

Credit where due: Origin is a serious product with a real insight behind it. Repositories, pull requests, reviews, merges, CI connections, and a public REST API, built around the assumption that agents are first-class users: cloud agents work in sandboxes on long-horizon tasks while your laptop sleeps, and your repos sync from GitHub so switching feels safe. The insight is correct. GitHub was designed for humans with browsers, and the industry is now full of non-human contributors that need something better.

But look at the structure you'd be moving into:

1. It's a paid gate on day one. Origin ships on Pro, Teams, and Enterprise plans, not Free. The baseline social contract of open source hosting, that anyone can host and anyone can fork, is not the starting point here.

2. The vertical stack should look familiar. Cursor is now a SpaceX company, acquired for $60 billion, shipping Grok models with bundled usage and a Router that decides which model handles your request. Editor, models, router, cloud agents, and now the code itself, all in one P&L. I wrote last week about what happens when routing and billing share an owner after Stripe bought OpenRouter. This is the same consolidation pattern, one layer deeper: the company that runs your agents now also holds your repos, and its incentives point at its own model stack.

3. Your agents live in their sandboxes. Agent-first hosting where the agents run in the landlord's cloud is not agent autonomy. It's workflow captivity with better ergonomics. The agent's identity, its permissions, its compute, and its output all exist at one company's pleasure.

4. It's still one origin. This is the unfixable one. Origin is a centralized service. It can go down this morning the exact same way GitHub went down this morning. Nothing about the topology changed; only the logo on the building did.

The answer is not a better landlord

The failure mode today was not "GitHub is badly run." It was "there is a single place where everyone's code, checks, and automation converge, and that place had a bad day." A replacement with the same shape inherits the same failure, plus a fresh set of lock-ins.

The actual fix has existed in principle since git was invented: git is a distributed system that we collectively re-centralized for convenience. What was missing was infrastructure that keeps the convenience without the chokepoint. That's the thing gitlawb has been building: a peer-to-peer git network where the hosting layer itself is distributed.

The architecture reads like a checklist written against this morning's incident report:

• No single origin. Repos live as content-addressed objects on IPFS; push to one node and the mesh mirrors it within about 30 seconds over libp2p. There is no central service whose bad morning becomes your bad morning. "Origin" isn't a place that can go down; it's everywhere the network is.
• Agent-first without captivity. Identity is an Ed25519 keypair with a DID, not an account on someone's server. Permissions are UCAN capability tokens an agent can delegate and revoke without a central authority. Every node exposes an MCP server, so any agent, running on your infrastructure, can push code, open PRs, and run reviews natively.
• Open and free at the base layer. The OpenClaude CLI (~30K GitHub stars) and the network tooling are open source. git push works through a standard transport helper. Nobody's pricing tier sits between you and hosting a repo.
• No model agenda. gitlawb's OpenGateway routes to whatever model you choose through one OpenAI-compatible endpoint. The infrastructure has no house model to sell you.

The honest caveats

Symmetry demands the same scrutiny I gave Origin. gitlawb is younger and smaller than either incumbent; a p2p network's UX has real friction that a polished centralized product doesn't; and decentralized systems earn trust in years, not press cycles. Origin will onboard more developers this quarter than gitlawb has, because defaults and polish win quarters. Topology wins decades.

And one more fairness note: GitHub will fix this outage, publish a thoughtful postmortem, and be fine. The point is not that GitHub is doomed. The point is that today every developer got a three-hour demonstration of what "one origin" costs, and the loudest alternative on offer is one origin with a different owner.

What to do with your three hours of downtime

1. Mirror your critical repos somewhere that isn't the same company as your CI. Today, that alone would have kept you shipping.
2. Audit your agent workflows for GitHub-shaped single points of failure. If your agents authenticate, commit, and verify through one provider, they share one off switch.
3. Try the decentralized path with one repo. gitlawb's install is a one-liner, and pushing a mirror to a p2p network is a fifteen-minute experiment that makes the topology argument concrete.

Cursor named its platform Origin, and honestly, the name gives the game away: it's a bid to be the new single remote everyone points at. The whole lesson of this morning is that the origin shouldn't be a company at all.

---

Sources: Bleeping Computer · GeekWire · Engadget · IncidentHub · TechStartups · SiliconANGLE · explainx · gitlawb architecture