Who shipped it?
Every incident has a story: a service that broke, a release that went out, commits that rode it, and the engineers who wrote them. ShipGraph connects the dots across people, code, and deploys.
Loading recent incidents…
Four worked examples — each one follows a real trail through the graph.
1
Follow an incident to its fixers
- Open Incidents and click any one (e.g. a GitHub “Incident with Actions”).
- The detail page walks the chain: incident → affected service → deployed release → shipped PRs → commits.
- At the bottom you get the engineers who authored those commits — the people behind the fix.
2
Measure a release's blast radius
- Open Repos and pick a repo, e.g. vitejs/vite.
- The Blast radius panel lists the latest release, the services it deployed to, and incidents that overlapped it.
- Use it to answer: “if this release breaks something, what is affected?”
3
Prove two engineers are connected
- Open Pathfinder and pick two engineers, e.g.
SarahFrench (Terraform) and patak-dev (Vite). - ShipGraph returns the delivery-graph hops between them — shared repos, merged PRs, commits, incidents.
- A real answer to “do these two people work on the same software?”
4
Search anything in the graph
- Type
vite, express or terraform in the search box on this page. - Results are grouped by kind — engineers, repos, pull requests, incidents.
- Click one to jump straight to its detail page.
– nodes connected by – relationships — among them.