Frequently asked questions (FAQ) [Servers-Monitoring.net]

News

10/12/2022
+ we have a new IP from which we carry out the secondary monitoring: 37.139.12.159. IPs of the main monitoring servers remains the same: 95.168.192.72, 95.168.192.195

09/01/2021
+ on 9.9. between 00:00 and 05:00, the measuring server will be moved within the server room. Expect a measurement failure of about 1.5 hours and the website will not work either.

11/06/2020
+ we have a new bank account: IBAN: CZ35 5500 0000 0016 8867 2001 | SWIFT: RZBCCZPP

14/09/2018
+ there will be security restart of our server on Tuesday 18th September at 08:00 am. Estimated unavailability is 60 minutes.

14/02/2018
+ there will be security restart of our server on Friday 16th February at 08:00 am. Estimated unavailability is 60 minutes.

08/07/2017
+ there will be security restart of our server on Wednesday 9th Autgust at 08:00 am. Estimated unavailability is 60 minutes.

11/25/2016
+ there will be security restart of our server on Tuesday 29th November at 23:55. Estimated unavailability is 30 minutes.

2/22/2016
+ there will be security restart of our server on Wednesday 24th February at 8:00 am. Estimated unavailability is 20 minutes.

7/30/2015
+ our ISP had a major outage connectivity. Measurement of the time from approximately 3:30 p.m. to 5:00 p.m. was broken and could lead to false reporting outages. We apologize for the inconvenience.

3/31/2015
+ we added SSL for better security for Czech version of our pages. Unfortunately it is not valuable for us to add SSL for English version too. Please use Czech version with Google Translator. We are sorry.

9/25/2012
+ we have a new IP address from which we carry out monitoring: 95.168.192.72, 95.168.192.195, 37.9.170.232

9/25/2012
+ the newly added Statistics page shows availability list of all measurements in the last year.

7/22/2011
+ we have a new IP address from which we carry out monitoring: 95.168.192.196, 95.168.192.197, 184.173.83.138 and 188.40.28.162

5/10/2011
+ possibility to pay by credit card

5/10/2011
+ you can recharge your credit without indication of billing information

5/9/2011
+ new ways of paying, faster crediting of credit, the possibility of make proforma invoice

4/23/2011
+ modified plugin for Firefox 4

3/20/2011
+ we have monitoring at about 20000 servers for today! Thank you for your confidence in our services.

12/18/2010
+ we can call defined URL if you have a fall-out

8/6/2010
+ new possibility of view page´s content in moment, when you have a fall-out, because there are not any keywords

4/3/2010
+ we established SSL in all administration for your higher safety

Do you want manage the server remotely on your own? Try dedicated servers . If you only want to provide collocation space - server hosting is available to you! Professional server management - managed server by Superhosting.cz.

Frequently asked questions (FAQ)

What does this service do?

It monitors your page's availability in the given interval and writes down the results. Those are afterwards displayed in the statistics. There is also the option to receive dropout alerts via e-mail etc.

What will happen in case of a dropout of the monitoring server or the on-the-way dropout?

In case of a dropout we try to monitor the page by two more servers across the internet (in the Czech Rep.). If all the replies are "not available" the monitoring result is claimed as a dropout. If by any case the monitoring server would disconnect the monitoring will not be made - this, of course, is looked after at all time.

What is the difference between the absolute and common availability?

Absolute availability is a mathematically exact number - there's the number of dropouts (during a time period) and the number of monitored times. If they're mutually divided we get the value of the availability during the whole time period.

Common availability comes out of the absolute availability but takes some things into consideration - gives them various importances:

When has the data changed: dropouts (and all data) are less important the older they are. Today's values are of the most importance (1), those monitored half a year ago 2 times less important (0,5), the ones monitored three quarters of a year ago are 4 times less important (0,25), finally the ones older than a year are of no importance at all. Shortly this month's data is more important than the one that is almost a year old, the course is fluent, linear.
Availability during the night hours: data monitored between the 2nd and the 6th night hour (every address can change the time) are of half importance than other data. This comes out of the fact that much less visitors use internet during this time so the eventual unavailability is not that big of a problem.

What types of monitoring do you offer?

We offer 19 different monitoring services, for more see services.

What do I get for converting to faster monitoring?

Firstly it is more often which helps to analyze the availability better and mainly it let's you know there's been a dropout much quickly.
Besides you can monitor much more than just a web server, for more see services.

Faster monitoring automatically views the responses of the page therefore you can not only see when the server was not available but also the encumbrance.

How to convert to paid monitoring?

You subscribe some credit from which we will extract the price for the services. To find out how to pay see Credit (after registration). Once there is a credit you get access to all functions.

What is the difference between HTTP (head) and HTTP (get)?

The difference is in the type of the request. The most used request for downloading the web page is HTTP command GET. It means that there is the page download request for the whole web page including the head and all data, the page. But the data itself is mostly useless for the monitoring, encumber the link and rise traffic. The condition is recognized from the returned head code, eventually if the server responds at all. That's why for 99% of the HTTP server monitoring the request HEAD is enough and this is the method we prefer.

Nevertheless it is true that some oddly set-up servers will not respond to the HEAD request at all. Therefore there is the option of monitoring using the GET request.

This is the same with HTTPS. for more information see the HTTP specification..

For how long are the results being kept?

For all services 1 year, for 10 minutes monitorings 3 months.

How can I recognize your robot in the statistics, what's his IP address?

The monitoring is primary from our server SuperHosting, that's 95.168.192.72 or 95.168.192.195. In case of unavailability of this address we have other machines which can monitor. The robot sends the User-Agent "KyblUptimeMonitor v1.1 (http://www.servers-monitoring.net, SuperNetwork, crawl)".

I have other questions, where can I ask?

You can contact us via e-mail.

Servers-Monitoring.net