Uptime checkpoint alarm
Last updated 2026-06-21
Definition
The uptime checkpoint alarm watches a website URL for you and pings your team the moment it stops responding. Quri probes each page on a schedule, and after a few failures in a row it confirms the outage and sends one alert through the channels you already use — then one more when the site recovers. No flapping, no noise.
How to do this in Quri
- Add the URLs you want watched in your uptime settings, each with a label.
- Set how often Quri probes each one and how many failures confirm an outage.
- Pick the channels the down and recovered alerts should reach.
- Optionally call the deploy-signal webhook from your CI so a fresh deploy is watched extra closely.
- Ask the assistant to list, add, or remove a watched URL any time.
Frequently asked
- How does Quri avoid alerting on a one-off blip?
- It only declares a site down after several probes fail in a row, not on a single timeout. You set the threshold, so a brief hiccup stays quiet while a real outage fires exactly one alert.
- Can it watch the site more closely right after a deploy?
- Yes. Call the deploy-signal webhook from your CI on a successful deploy and Quri tightens the probe cadence for a short window, so a bad release is caught in seconds rather than minutes.
- Where do the outage alerts go?
- Through the same alert channels you already configured — email, Slack, a webhook, or Linear. The uptime alarm reuses your existing delivery setup, so there is nothing new to wire up.