Five-minute uptime checks
Your homepage is requested every five minutes and the HTTP status and response time recorded. You get a timeline of checks rather than a single red or green light.
A check every five minutes, an independent second opinion before any alert, and a weekly full health scan that tells you when your score starts slipping.
Monitor my siteTwo jobs: tell you the moment the site stops answering, and tell you slowly when it starts rotting.
OmniCheck checks your homepage every five minutes, independently confirms suspected outages, and emails you when your site goes down and when it recovers.
Ten consecutive checks reached the site successfully.
A one-off audit is accurate for about a week. Sites decay continuously, and nobody notices the decay on their own site.
Without monitoring, the notification channel for downtime is an annoyed email from someone who tried to buy something. The cost is the sale plus the trust.
A new hero image, a marketing tag, a plugin update — each one can move speed or accessibility. A weekly scan attributes the change to the week it happened.
A page returning HTTP 200 with a broken template passes every naive uptime check. Requiring expected text is what turns "the server is up" into "the site works".
Add a site once; it watches itself after that.
Check frequency, how false alarms are avoided, and what it costs.
The homepage is checked every five minutes, so a confirmed outage reaches you within a few minutes of the first failed check — the delay is the independent second probe confirming it, which is the difference between an alert you trust and one you learn to ignore.
A single failed request never triggers an alert. The primary probe seeing a failure only raises a suspicion; a second independent probe has to reach the same conclusion before any email is sent. Transient blips from one vantage point are discarded.
Only if you tell it what "working" looks like. Add an expected text string — a product name, a phone number, anything that only renders when the page is healthy — and a response missing that string counts as a failure even though the server returned HTTP 200.
A free account monitors one site, including the weekly full-site health scan. There is nothing to enter card details for to get started.
Scheduled scans run on their own queue lanes, separate from interactive work, and are paced so they do not saturate your server. The speed check also runs alone rather than alongside the crawl, which keeps its measurements honest as well as keeping load down.
Yes. Uptime checks and scheduled scans can each be paused and resumed independently, and you can edit the URL, the expected text and the scan options at any time without losing the history already collected.
Monitoring re-runs these five checks on a schedule. Each one also runs on demand.