How often
From every 10 seconds to every 5 minutes, per check. Turn it; the next check is already on the new clock.
Uptime monitoring · for small teams
Quiet checks your sites, APIs and cron jobs every 30 seconds from six regions, and stays silent until something is actually broken. Then it sends one alert — to the person on call — not forty.
No dashboards to learn, no rules engine. Set how often, when you sleep, and who hears it. Quiet does the rest — it confirms a failure from a second region before it says a word.
From every 10 seconds to every 5 minutes, per check. Turn it; the next check is already on the new clock.
Warnings wait until morning. Outages don’t — a site that is down wakes the person on call, and only them.
One alert per incident, to the right person, by SMS, Slack or a phone call. When it recovers, one more to say so.
Anything else: [email protected]. A person answers, usually within the hour.
A failed check is repeated at once from a second region. Only if both agree does anyone hear about it. Last month that kept 0.4% of alerts false, against an industry habit of one in five.
Yes — paste a list of URLs or import from a CSV. Cron jobs report in with one curl at the end of the script.
Nothing breaks. Extra checks keep running for the month and we write to ask whether to move you up.
In Frankfurt, with a copy in Dublin. Check results are kept for 13 months, then deleted.
Ten checks free, no card. Add your first URL and the first check runs before the page reloads.