ArticlesUptime

How we confirm an outage before we alert you

Uptime Monitor checks from Paris. When a check fails, a probe in Amsterdam checks again before we alert you, and the alert says where it failed: DNS, connect, TLS or HTTP.

Your monitors are checked from Paris. When a check fails, a probe in Amsterdam checks the same thing again before we alert you. The alert then tells you which step failed, so you know where to look first.

Why a second location

One failed check from one place can be a blip in the network between that place and your server. Your site may be fine for everyone else. A second check from another city tells the two apart, so an alert from us means your site failed from two places. If the Amsterdam probe can't be reached, Paris decides on its own, so a problem with the probe never hides an outage.

What happens, step by step

  1. Paris checks on schedule. Every minute on Pro and Business, every 5 minutes on the free personal plan.
  2. A check fails. Paris checks again about 15 seconds later, and Amsterdam runs the same check at the same time.
  3. Amsterdam sees the failure too. The outage is confirmed: we alert you, an incident opens in the app, and your status page shows the service as unavailable.
  4. Your site answers again. The incident is resolved automatically, with the time it came back.

Where it failed

Loading a web page takes four steps. The alert names the first one that failed.

StepWhat failedWhere to look first
DNSYour domain name didn't resolve to an addressYour DNS host or domain registrar. Has a record changed, or has the domain expired?
ConnectThe server didn't accept a connectionYour hosting company or server. Is it running, or is a firewall in the way?
TLSThe secure connection couldn't be set up, often a certificate problemWhoever renews your certificate. SSL Monitor warns you before a certificate expires
HTTPThe server answered with an error, like 503Your website or the app behind it, and the person who runs it
Read the step before you call anyoneIf DNS, the connection and the certificate all passed and HTTP failed, the hosting company can see your server is up. Start with your web developer.

An example

A fictional webshop, checked every minute on Pro:

  1. 10:10Paris: HTTP 503
  2. 10:10Confirmed from Amsterdam: HTTP 503
  3. 10:10Alert sent by e-mail and to Slack. It says: failed at HTTP response
  4. 10:10Status page: Webshop is unavailable
  5. 10:14Webshop answers again. Resolved automatically

What Amsterdam keeps

Nothing. The Amsterdam probe runs the confirming check and passes the result back. It stores no data. Everything Uptime Monitor keeps, like check results, incidents and your status pages' history, is stored in Paris, with no US sub-processors.

Every plan gets the confirmation from Amsterdam, including the free plan for personal sites.

Related

All Uptime articles · Uptime blog

Be the first to know, and the one with the answer

Uptime Pro, €12 a month: checks every minute, 3 status pages. Monthly, cancel any time.Personal or hobby site? Monitor it free.