Issue №01 — Why your site went down

Uptime,
diagnosed.

Most monitors say “it’s down.” UptimePad tells you which deploy, which region, which DNS record, which server.

A
acme.com
https://acme.com/health
Operational
Uptime
99.98%
last 30d
Response
184ms
p95 · 3 regions
SSL
62d
until renewal
Response · 24h184 / 220 / 312 ms
iad142
sfo198
lhr168
fra156
sin234
syd286
gru220
!
CPU spike on api-prod-2 lines up with a 312ms response peak.
14:22 UTC · server↔site correlation
Open →
Trusted by teams shipping to millions
Northwind
Pinecone
Lattice
Foundry
Hearth & Co.
Cobalt
Six checks, one dashboard

Everything you’d need a runbook to remember.

One monitor watches uptime, DNS, SSL, content keywords, APIs and the server behind them at the same time, so a single check covers the whole front door.

Uptime

Up or down, down to 30s.

Checks from three regions in parallel. If two agree, we wake you. If they don’t, we don’t.

DNS

DNS, watched record-by-record.

A, AAAA, MX, TXT, CNAME (alerted the moment a value drifts away from what you expect).

SSL

Never miss a renewal again.

Certificate chain, expiry, mismatched hostnames (counted down in days, not surprises).

Content

"Was the price tag right at 2am?"

Pin a phrase in the HTTP body. We tell you the second the page lies.

API

Endpoints, with assertions.

Status codes, response shape, latency budgets. A public REST API for everything.

Correlation

Server ↔ Site, side by side.

Push your CPU, memory, and deploy events in. We line them up against the outage.

The differentiator

Connect your server. See the cause, not just the alarm.

Most monitors stop at “your site is slow.” Pipe in your CPU, memory, deploys and error logs, and UptimePad shows them on the same timeline as the outage.

  • Outage at 14:22? We point at the deploy at 14:21.
  • p95 climbing? We line it up against your CPU graph.
  • Wire up your existing metrics with a one-line webhook (no agent install).
Incident · Apr 28, 14:18 — 14:34 UTC
16 min
Site response (p95)peak: 360
Server CPU · api-prod-2peak: 92
Errors · /checkoutpeak: 22
Probable cause: CPU saturation on api-prod-2 after deploy a14d2b.
Three probes today. More coming.

If two regions agree, you’re down. Not just one flaky probe.

Every check runs from all three regions in parallel. We only page you when more than one agrees, so a flaky route doesn’t turn into a 3am wake-up call.

Probe locations3 of 3 healthy
  • iadUS East · Virginia
    142 ms
  • fraGermany · Frankfurt
    156 ms
  • sinSingapore
    234 ms
Incident timeline

A clean record of what actually happened.

Every probe, deploy, alert and recovery in one timeline. Share it with your team, paste it into the post-mortem, hand it to the customer.

  1. 14:18
    Deploy a14d2b shipped to api-prod-2.
  2. 14:22
    Three regions agree (checkout returns 502).
  3. 14:23
    Correlated: CPU 92% on api-prod-2.
  4. 14:34
    All regions recovered after rollback.
Pricing

Honest pricing. No “contact us” for the basics.

Start free. Upgrade when your business needs it. Cancel anytime in two clicks.

Free
$0forever

For side-projects and small sites.

Start free
  • 100 monitors
  • 5-minute checks
  • All 10 notification channels
  • SSL + DNS + content
  • 1 year of history
  • Public REST API
Starter
$4per month

For real businesses with real customers.

Start Starter
  • 200 monitors
  • 1-minute checks
  • Up to 5 servers correlated
  • All 10 notification channels
  • Branded reports
  • Longer retention
Most popular
Pro
$15per month

For teams who can’t afford to guess at 3am.

Start Pro
  • 1000 monitors
  • Checks down to 30s
  • Up to 25 servers correlated
  • Unlimited status pages
  • Priority probe queue
  • Email lifecycle + monthly digests

Stop guessing. Start diagnosing.

Drop in a URL, pick your regions, and you’re monitoring in 90 seconds. No card, no sales call, no “contact us” for the basics.

No card. Cancel in two clicks.