Deployments
The check leaves with the deploy, not on the next cycle
A probe that passes every five minutes tells you about a regression five minutes too late. PostShip fires on the event, then comes back twice.
“It had been live for forty minutes when a customer told me.”
A deploy breaks the moment it is deployed, not at a random time of day.
- passes per deploy
- 3
- as soon as the build ends
- T+0
- warm cache
- T+2
- CDN propagated
- T+8
passes per deploy
as soon as the build ends
warm cache
CDN propagated
How it works
01Your host tells us
A Vercel, Netlify or Cloudflare Pages webhook, pasted once in the project settings.
02T+0: the check goes out within the second
All your monitored URLs are replayed immediately, while you're still looking at the deploy screen.
03T+2 and T+8: the two follow-ups
Many breakages don't show right away.
04The result comes back where you work
A Check Run on the deployed commit if the GitHub app is connected, green or red, with the Ship Score as its title.
What we're often asked
What if I don't use Vercel, Netlify or Cloudflare?
PostShip keeps checking your site on its usual cycle — every 15 minutes on Free, every 5 minutes on paid plans. You lose the instant trigger, not the monitoring.
Do preview deploys count too?
Only if you ask for it, and they're handled separately: checked on their own domain, without touching your production's history or status.
Does it slow down my deploy?
No. PostShip is told when the deploy ends and works on its side; nothing waits for its answer, and your release doesn't depend on it.
Paste your site's URL. PostShip checks it in front of you, no account and no card.