We monitor your website availability from multiple locations worldwide.
Make sure you know your site is offline before your customers have to find out.
Our uptime checks run every minute from a location of your choice. Once we've confirmed your site is down, we'll notify you instantly.
There are many reasons a site can go down.
HTTP/1.1 500 Internal Server Error Server: nginx Date: Wed, 11 Dec 2019 01:30:55 GMT Content-Type: text/html; charset=iso-8859-1 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.
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 failures for 2 minutes in a row, we send out notifications so you can intervene. This prevents monitoring flaps and false positives.
You can increase our timing threshold in your settings. Prefer to get alerted after 5 minutes instead of 2? Not a problem.
In our report you'll find useful commands to replicate our monitoring, this allows to you see exactly what we see.
Is just monitoring a status code not enough? You can configure a piece of text we need to verify on the page too (a "checkstring"). If we receive an
HTTP/200, but the checkstring is missing in the source code, we'll mark the site as down.
By default we monitor using a
GET HTTP call, but you can also change this to
PATCH. Each with their own form payload. This allows you to monitor search results, contact form submissions, API endpoints, ...
You could even perform a site 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.