All features
Website monitoring

Website monitoring that catches more than a 500

Spot Downtime loads your pages from our servers on a schedule and alerts your team the moment one fails. Add a keyword check to catch pages that return 200 but show an error.

Checks as often as every 30 seconds

Every 5 minutes on Free, every minute on Starter, down to every 30 seconds on Pro. Each monitor runs on its own schedule.

Keyword checks

Require text such as “Add to cart” on the page. If it's missing, the monitor counts as down even when the server says 200.

No false alarms from blips

A failed check is retried and confirmed from California, Amsterdam and Singapore before it counts, so a network blip near one server doesn't page anyone.

See it in Spot Downtime

The real app, with a demo team's monitors. Included on every plan, Free too.

A website monitor's page with uptime, SSL and domain expiry, and a 24-hour response time chart with p95
A website monitor: uptime, SSL and domain expiry, and response times with p50 to p99.
The Monitors page: thirteen monitors, two of them down, with a bar for each recent check
Every monitor on one page, with each recent check as a bar. It updates live.

What is website monitoring?

Website monitoring means loading your pages from outside your own network on a regular schedule and checking that they work. If a page stops loading, returns an error or takes too long, a monitor notices within one check interval and tells your team, usually long before a customer writes in.

Spot Downtime sends a GET request to each monitored page, follows up to 5 redirects, and counts any 200–399 response within 10 seconds as up. Every check is recorded with its status code and response time, so you get both an alert the moment something breaks and a history of how the site has behaved.

Why a 200 status isn't enough

Plenty of outages never produce a 500. A broken deploy can render an empty template, a CDN can serve a cached error page, and a failed database can leave a page that loads but says “Something went wrong”. The server reports success, so a basic uptime check stays green.

A keyword check closes that gap. Tell the monitor which text must appear, such as a product name, “Add to cart” or your footer, and the check fails whenever it's missing from the first 1 MB of the response. The alert says which keyword was missing, so you know where to look.

Fewer false alarms, fast real ones

An alert that turns out to be a network blip teaches people to ignore alerts. When a check fails, Spot Downtime retries it after 2 seconds and, at the same time, checks the same page from Amsterdam and Singapore as well as California. The monitor only goes down when most regions agree, and the incident says how many regions saw the failure. Each monitor's page shows these regions on a map, and you can check the site from any of them whenever you suspect a regional problem. On Starter and Pro you can also choose the region every check runs from, so a site whose visitors are in Europe or Asia is checked from there.

Real outages still come through quickly: checks run every 5 minutes on Free, every minute on Starter and as often as every 30 seconds on Pro. Every HTTPS monitor also watches its SSL certificate, and a status page lets customers see what's happening without contacting support.

How to set it up

  1. 1Click Add monitor and choose Website.
  2. 2Paste the page address, and optionally the text the page must contain.
  3. 3Pick how often to check. The first check runs within seconds.
  4. 4Connect Slack, Discord, email or a webhook under Alerts to hear about outages.

The details

Counts as up
HTTP status 200–399 within 10 seconds
Counts as down
Any other status, a timeout, a DNS or TLS error, a refused connection, or a missing keyword
Redirects
Followed, up to 5
Keyword match
Case-insensitive, first 1 MB of the response
Custom headers
Optional, e.g. a secret header your firewall lets through
Check interval
5 min to 1 hour on Free; 1 min on Starter; 30 s to 1 hour on Pro
Check regions
The US on every plan; on Starter and Pro, Amsterdam, Singapore or several at once, chosen per monitor

Questions

Where do checks come from?
From Spot Downtime's servers on the public internet, so you see what your visitors see. Checks run from the US by default; on Starter and Pro you can choose Amsterdam or Singapore for each monitor instead, to check from near your users. A failure is confirmed from the other regions before it counts. You can also pick several regions: each one then checks every interval, and the monitor is down when most of them can't reach it. Private or internal addresses can't be checked.
Does a slow page count as down?
Only if it takes longer than 10 seconds. The monitor's chart shows the average and p95 response time, with p50, p75 and p99 for the last 24 hours. On Starter and Pro, a slowness alert warns you when the p95 rises above a threshold you set, without counting it as downtime.
Our firewall blocks your checks. What can we do?
Add a secret header to the monitor and allow it in your firewall, or allow our IP addresses. The firewall allowlist guide in the docs shows how for Cloudflare, AWS, nginx and Apache.

Set up website monitoring in under a minute

Included on the Free plan. No card needed.

Create a free account