
Today we're announcing custom HTTP statuses for our website uptime monitoring feature. It's available for our Pro Plan users and is an extremely useful feature for setting which HTTP status codes will trigger a website down event for your monitors.
In this article I'll digest more about this feature...
When you set up a new website monitor and set it to the HTTP status type we'll send a request to your website based on your monitor checking frequency to make sure that your website is up.
If your website doesn't return a 200 response then we'll check again behind the scenes just to make sure it wasn't just a short glitch.
Beyond this, if this request fails and returns a different status code then we'll mark your monitor as down.
With this feature you'll now be able to define the status codes that you'd like to trigger a down status code.
This means, for example, you might want:
...to mark your monitor as down.
If you no longer have an active Pro subscription with us then we'll fall back to the default status code of 500.
A subdomain takeover lets an attacker claim your subdomain by exploiting dangling DNS records. Learn how it happens, real-world examples, and how DNS monitoring detects it.
Read moreMean time to detect (MTTD) measures how long it takes to discover an incident after it starts. Reducing MTTD is one of the highest-leverage improvements in reliability engineering.
Read moreBlack box monitoring tests your systems from the outside, the way users experience them — without access to internal code or infrastructure. Learn how it works and when to use it.
Read moreLooking to monitor your website and domains? Join our platform and start today.