We monitor your website availability from multiple locations worldwide

As soon as your site goes offline, we notify you via e-mail, Slack, SMS, Discord, Pushover, ... Your choice.

Get started »

10 day free trial
No credit card required

Our uptime checks run every minute from a location of your choice. Once we have confirmation that your site is down, we'll notify you instantly.

We'll alert you if your site goes down

There are many reasons a site can go down.

  • Human error
  • A faulty deploy
  • Lack of network connectivity
  • High load on the server
  • Domain name offline
  • DNS resolving issue
  • ...
HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Sat, 4 Apr 2020 05:20:55 GMT
Content-Type: text/html
Content-Length: 531
Connection: keep-alive

Whatever the cause may be, we alert you instantly. With all the details to help you troubleshoot the problem & fix it.

Via email, SMS, Slack, Discord, ... you name it. We've got plenty of notification options.

Here's how that might look.

An example of a Slack alert when a website goes down and when it recovers.
Screenshot of a Slack notification

The technical explanation of what we monitor

We monitor what truly matters: your application or website.

If we fail to receive an HTTP/200 response within a reasonable timeframe, we mark your site as down. When we see website failures for 2 minutes in a row, we send out notifications so you can intervene. This prevents monitoring flaps and false positives.

You can change the timing threshold in your settings. Prefer to get alerted after 5 minutes instead of 2? Not a problem.

Our downtime reports give you all the details to quickly verify and troubleshoot any alert.

Here's an example when we detect a site is down.
Screenshot of a uptime monitoring details

In our report you'll find useful commands to replicate our monitoring, this allows to you see exactly what we see.

Content verification & checkstring monitoring

Is just monitoring a status code not enough? We can verify the existence of a piece of text on the page too (a so called "checkstring"). If we receive an HTTP/200, but the checkstring is missing in the source code, we'll mark the site as down.

Monitoring beyond a GET request

By default we monitor using a GET HTTP call, but you can also change this to POST, PUT or PATCH.

Each method can have its own form payload. This allows you to simulate a form submission and monitor search results, contact forms, API endpoints, ...

You could even perform a website login through a POST call and verify the account page loads properly.

Want to get into the nitty gritty details of our uptime monitoring? Have a look at our documentation.

Want to get started? We offer a no-strings-attached 10 day trial. No credit card required.

Get started »

You're all set in
less than a minute!