Availability monitoring

You hear about an outage before your customer calls.

We check your website from our own infrastructure, at a pace set by your plan. We confirm a failure with a further check, so a single network glitch wakes nobody up.

Free plan at no cost, no payment card.

yourcompany.comchecked every 30 sThe website is back
check passedno response
Time to detection
1 minute
Time to notification
3 minutes
Resolved. The outage lasted 7 minutes.
A simulated run on the Business plan. Time is compressed.
Content phrase

The response code is not enough.

A website failing on the server side can return empty content with code 200, which reads as “everything is fine”. Monitoring that only looks at the code will call it healthy. We also watch a fragment of content that has to be in the response: the company name from the footer or another fixed element. When it disappears, we open an event.

The home page content check is included in every plan, the free one as well.

What the server returns
HTTP 200 OKthe same code in both situations
<html>
  <body>
    <h1>Your Company</h1>
    <footer>Your Company Ltd.</footer>
  </body>
</html>
Verdict of the check
Monitoring that only reads the response code
Code 200. The website is considered healthy.
Calmfox Watch
The phrase “Your Company” is in the response. The website works.
Switch the situation to see the difference. Simulated.

Two dates a year that can take down the website and the email with it.

Certificates and domains expire quietly, and the effect shows only when the browser warns your visitors or the email stops arriving.

SSL certificate

We warn you well before expiry. Tools that renew certificates automatically usually do it a month ahead, so an earlier notification would be a false alarm.

14731days before expiry

Domain expiry

We read the dates straight from the domain registry. An expired domain takes the email with it, and getting it back is expensive and slow.

3014731days before expiry

Domain and DNS changes

We compare the domain configuration against the previous reading: server addresses, mail records, name servers and DNSSEC signatures. We report a change only once a second reading confirms it, because a single discrepancy is usually not a change but a missing answer.

The first reading becomes the reference point and wakes nobody up.

We also check the addresses you choose.

From the Start plan you decide which pages are checked separately. For each one you can give a phrase that has to appear in the content.

Three addresses on Start, twelve on Business, on Enterprise as agreed.

  • cart and order summary
  • customer account sign-in
  • pricing and services
  • contact form
  • booking page

How long it takes.

We sell two numbers, not the gap between checks. Time to detection is the gap multiplied by the number of confirmations. Time to notification adds the threshold that keeps a short outage from waking anyone.

PlanFailure detected withinNotification arrives within
Free10 min15 min
Start2 min4 min
Business1 min3 min
Enterprise1 min2 min

Who responds to a failure.

Detection and notification are on us in every plan. The response belongs to your team, and our on-call duty is a separate service. On the Enterprise plan response times and on-call duty go into the contract and we agree them individually.

We say this plainly, because the difference between “we will tell you” and “we will fix it” is the difference people pay the most for.

Check your website.
Free, in two minutes.

The free technical review covers availability, the certificate, the domain, email, content and forms. It ends with a score and a list of tasks you can hand to your developer. No payment card and no commitment.