Quality of service is the first thing that your visitors notice about your company or products when they visit your website. Network congestion, server slow-downs, high response latency, all those symptoms of degraded quality can lead your customers to leaving your web site.

Of course! All subscriptions are refundable up to 15 days after the purchase. That's because we are pretty sure you will like our service and find it valuable for your business.

We can't make any promise in this FAQ, but we are always interested in hearing from our customers. Contact us, we will be glad to provide our expertise to help you solve your issues.

Short answer: it's a time-stable, geographically-stable, relative measure of your website performance. It's relative to a reference period: the 30 first days of monitoring, by default, but you can reset this period. This metric is specially useful to watch for signs of performance degradation or improvements.
Long answer: Here.

Our mission is not just to provide real-time alerts when your sites go down, but also to give you valuable metrics and benchmarking of the Quality of Service of your web site. We believe 3 minutes is the optimal frequency to provide accurate metrics and real-time alerts. We don't provide, say, a 10 minutes or 30 minutes frequency because that would reduce significantly the accuracy of our metrics. We also believe that if you need a frequency lower than 3 minutes, then there is already something going wrong with your web site, and a technical evaluation of your software and/or hardware architecture would probably be more beneficial than any kind of monitoring.

Note however that this 3-minute constraint is a soft limit that we can easily change on a per-monitor basis, so if you think you really need a lower frequency, we'd gladly discuss the matter with you.

The answer varies depending on the web site you are monitoring. If you have a publicly accessible web site, for instance an e-shop or a corporate web site, you should monitor your main landing pages to ensure the performance is always good for first-time visitors. Additionally, most performance issues are related to the database, and it is always a good idea to monitor pages that cover some typical database-access use cases, for instance a page that displays an item with user reviews comments, or a page that provide a large listing of your data. If you are able to do so, we recommend creating a specific non-public page that makes typical database queries.

Although that would be easy to implement, it is not something that we are willing to do, and we strongly advise you not to do this. There is one simple reason to that: You should NOT give a direct access to your database to a third-party, even a read-only access, for obvious security reasons, but also for confidentiality. Instead, you should create a special page with access control, and have this special page make a series of database request. You can use our content-checking feature to spot some keywords on the page, to ensure the validity of the queries results, or simply make it respond with an HTTP error code if the test fails.

Alternatively, if you just want to monitor your database and your database only, then your best solution is a tool running inside your network, as there is no added value for you to use an external monitoring in this case.

If your web site responds with an HTTP error code, then this is automatically detected by the monitor stations, and an alert is immediately triggered. If your site sends a normal HTTP page in case of error, you can check that a specific text is sent, or that a specific text is not sent, by using our Content Checking feature, available in the Alert Conditions panel of your monitor configuration. Note that you can test as many keywords as you want with this feature.

Of course, and it's very easy. Edit your monitor configuration this way: Advanced Http Parameters > POST request, then add the form values in the HTTP Request Parameters panel. Of course, this also works for HTTP/S, so you can test a login or a purchase procedure.

If the server is accessible from the internet with a public IP address, you probably can monitor it. For instance, say you have server with IP 11.22.33.44, and http queries should be made for domain my.private.tld, you can create a monitor that targets http://11.22.33.44/SomePage and add the "Host: my.private.tld" header to your monitor configuration.

Yes. Just use their IP address directly, and add a Host header to specify the domain name, if needed.