Storm over the checkout
shop.example.com/checkout stopped answering. It failed three checks in a row, so this is not a blip.
- First failure
- 14:20:41
- Confirmed after
- 2 retries
- Answer
- HTTP 502
- Uptime, 30 days
- 99.12%
A weather report for your websites
Example site · right now
99.98%
Hour by hour · response time in ms · example
See trouble coming
PulseGuard reads your sites' own history: a certificate nearing its date, a site that slows down at the same hour every evening, planned work. It warns you days before, and sends a short note in the morning when something is coming.
When the storm hits, you know
A failed check is retried twice, ten seconds apart. Then one email, and one more when the sky clears.
Under a minuteFrom the first failure to your inbox, with checks every 30 seconds.
No drizzle alertsA single blip that passes on retry never sends an email.
Clear againThe recovery email says how long the outage lasted.
Pick a plan
Every plan gets email alerts, the outlook and a daily uptime summary kept for 400 days.
Pro
$29 /month
- 50 sites
- Checked every 30 seconds
- 5 status pages
- 90 days of check history
- Certificate warnings
Enterprise
$99 /month
- Unlimited sites
- Checked every 10 seconds
- Unlimited status pages
- 365 days of check history
How is the outlook made?
From your own data: certificate dates, slow spells that repeat at the same hour, planned maintenance and outages this week. It never guesses about sites it hasn't watched.
What do the weathers mean?
Clear is up, cloudy is slow but answering, a storm is down, and fog means paused, waiting for its first check, or in planned work.
Can my clients see it?
Yes. Each client can get a public status page with their sites under their own names.
Will a blip wake me?
No. Three failures in a row, ten seconds apart, before an email goes out.