Frequently Asked Questions (FAQs)

How can I get notified via SMS when my servers are down?

You can add your mobile phone number to your Server Check.in account by visiting the 'Edit Account' page. Further instructions can be found here: SMS Help.

Note that some international carriers are not supported at this time. Server Check.in uses Twilio for SMS messaging, so you can check if your country and carrier is supported here.

Why don't you offer Feature X/Y/Z?

We want to keep things simple and affordable. There are many server monitoring services offering amazing and interesting features to help you keep track of many services in minute detail, but they are sometimes expensive and often complex.

This service was built for smaller developers and individuals who simply want to know when their servers and websites are down, and how they're performing over time. No excessive frills—just a really, really simple interface, and a low price.

We might offer a new feature here or there, as long as they don't detract from Server Check.in's simplicity and speed.

How can I cancel my account?

You can cancel your Server Check.in account any time. Just log in, then go to the 'Edit Account' tab under your 'My Servers' page. Scroll down and click the 'cancel account' link, then follow the directions.

Once you've canceled your account, you will no longer be charged any further yearly fees.

How often do you check my sites/servers?

We will check your sites and servers every 1, 5, or 10 minutes (you can choose the frequency per-server), every day.

Server Check.in says my site is down, but I can still access it. What's up?

Server Check.in monitors your sites and servers from different geographical locations; every now and then, one of our routes to your server may not work as well as the route you're using to get to your server. It might be us, or it might be you—but to be safe, we'll always notify you when we see a problem.

Additionally, your site may still be up, but performing very slowly (more than 25 second response times). In these cases, we'll count that as an outage, since very few people on the web are willing to wait that long to access a site, and it usually indicates either a problem with your site or server, or a huge traffic influx that you might want to know about.

What do the status codes for outages represent?

For any HTTP failure status codes (e.g. 403, 500, etc.), the code represents a standard HTTP response. For example, if you see an outage with the status code '403', that means Server Check.in was unable to access your site or a page on your site because your site returned a '403 Forbidden' response, likely meaning the page is behind an admin login or some other protection.

There are special codes used below the normal HTTP response codes (below 100), and these may be changed and/or added to over time:

Status Code Definition
0 Server unreachable (for some reason, Server Check.in could not connect to your server).
1 DNS unreachable (Server Check.in could not resolve your domain name).
2 Connection timeout (Server Check.in could see your server, but it took more than 15 seconds to form a connection).
3 HTTP content not found (only applies to HTTP content server checks).
100+ HTTP status codes (e.g. 404 = Not Found or 403 = Forbidden).

How accurate is the latency graph?

The accuracy of the latency measurements on Server Check.in can vary due to the following:

  • The geographical location of your server. Because Server Check.in is based in North-America, latency will increase as your server is geographically further away from the USA. Unfortunately, even bits on the Internet must obey the laws of physics!
  • Whether you're checking a server by ping or HTTP status. ICMP ping packets are tiny, and very fast. It's a relatively simple operation to ping a server and get back the successful result (or not). Usually, pinging a server is much faster than checking whether the server is responding via HTTP. Consider that, for an HTTP request, your server will need to accept a request into it's web server software, the server software will process the request, and build and send back a response.
  • Random things. As good as the Internet is at getting traffic from point A to point B, the actual route data takes can vary widely, and that means latency can suffer (or improve!) as a result.

It's best to use a variety of measurements to determine from where latency comes. Use Google's Page Speed and other profiling tools to get a more accurate view of your site's perceived slowness. We just measure how long it takes for our servers to connect to your servers.

What name will appear on my credit card statements when I am billed for Server Check.in?

You will see a charge from either MIDWESTERNMAC or SERVERCHECKIN on your credit card statement when you are billed for your Server Check.in account. Please contact support@servercheck.in if you have any questions related to your account or billing.

What IP addresses do you use to check my servers?

Server Check.in customers can visit the Check Servers page to view a list of current probe servers used to check your servers and websites. This listing may be useful if you'd like to restrict access to your servers, but still allow Server Check.in servers through.

Who Runs Server Check.in?

Server Check.in is a service by Midwestern Mac, LLC.