verified before it pages you
Quorum re-checks every failure before it wakes you — a one-off blip never pages you. When your phone buzzes, it's real — with the evidence attached.
~2 min setup · no credit card · commercial use welcome
verification — checkout-api
suppressed
a single timeout on cdn-edge, healthy on the next re-check 14s later. Recovered inside the window — no alert sent.
alerts arrive where you already are
the problem
A single-vantage monitor watches your site from one network. When that network blips — a bad route, a DNS hiccup, a congested peer — it declares DOWN. Two minutes later, UP. Your site was fine the whole time.
A few nights of that and every buzz might be nothing. You mute the channel. You swipe without reading.
That's the real outage risk — not downtime. The night you stop believing your monitor.
140
false alarms in one day
0
real outages
reported by a real UptimeRobot user
one vantage point, one bad night
the same night, with a quorum
Up all night. Six single-region blips were re-checked from us-east over the ~40s window — none confirmed, none forwarded.
how verification works
US East is the one live region today. It reports a 503 on your endpoint — to Quorum that's a claim, not an incident yet.
The same region probes the endpoint again, and again. A one-off blip that clears on the very next check never leaves this stage.
The window closes. Still down and you get one alert with evidence. Recovered inside the window and nothing pages.
confirmed
One alert, evidence attached.
recovered
Suppressed, logged, silent.
Today, from one region — US East — by re-checking. As eu-west and ap-south roll out, the quorum becomes geographic.
A single check can't tell your outage from a network blip. A quorum can.
coverage
HTTP(S) checks with status codes, response keywords, and latency — re-checked before anything pages you, from US East today with more regions rolling out.
200 OK · "healthy" · 124 ms
Your job pings a unique URL when it runs. Miss the period plus grace, and you know.
$ curl https://q.rm/p/a1b2c3
Certificates and domains age in silence. Quorum counts down and warns at 30, 14, 7, and 1 days out.
T-30 · T-14 · T-7 · T-1
A public status page on your domain, in your brand. Live in minutes, not a weekend.
status.yourapp.com
Telegram, Slack, Discord, webhooks, email. Every channel included — no SMS upsell games.
Flap detection groups a bouncing service into one incident with one timeline. When it recovers, the notice includes how long it was down — not 140 emails.
incident #4128 · checkout-api
recovered
1 incident · 14 state changes · 7m 36s
get started
Add a URL, or paste an UptimeRobot API key / Uptime Kuma backup and every monitor moves over in one click.
Telegram, Slack, Discord, webhook or email. Set who, not just what.
Checks run from us-east; nothing pages you until a re-check quorum confirms it. eu-west and ap-south are rolling out next.
heartbeat ping
# ping this when your cron job finishes$ curl -fsS https://quorum.sh/p/a1b2c3 > /dev/nullAbout two minutes. No credit card. Commercial use welcome.
evidence attached
response body · application/json
{"error":"upstream timeout","upstream":"payments-v2"}You start fixing from the notification — not logging in to check whether it's even real.
compare
| Quorum | UptimeRobot | Uptime Kumaself-hosted | Enterprise suites | |
|---|---|---|---|---|
| Verification before alerting | re-checks before alerting (multi-region rolling out) | single check fires the alert | one vantage point — yours | yes, tuned by an ops team |
| Evidence in the alert | status code, body, re-checks, timeline | a link to log in | what your one server saw | deep, if you built the dashboards |
| A flapping service means | one grouped incident | an inbox full of up/down | an inbox full of up/down | an escalation policy |
| Survives your infra dying | external by design | external | it died with your server | external |
| Built for | solo devs & small teams | everyone, loosely | people who enjoy patching | SRE teams |
If you have an SRE team and Terraform, use Better Stack or Checkly — genuinely. Quorum is for the rest of us.
questions
No credit card
Start free, upgrade when it earns it.
Commercial use welcome
Run it for real work.
One-click import
Bring your UptimeRobot or Uptime Kuma monitors over.
Early access opens soon. Early users get the migration importer first — paste an UptimeRobot API key or Uptime Kuma backup, and every monitor moves over in one click.
No spam. No credit card. One launch email.