Import Uptime Monitors from .CSV

To get started, head on to your Uptime Monitors dashboard from your client area menu. Now, locate the “Import” drop-down button on the upper right corner of the dashboard. Click it and select “From CSV” from its drop-down options. Then, just follow the three easy steps on the modal window that opens up. # CSV […]

Read More

Domain Expiration Date Appears Incorrect

In some odd specific scenarios, you may get alerted by our platform that your domain is about to expire, even though your Domain Registrar shows you an expiry date long into the future (i.e., in a year from now). This happens because our system checks your domain’s actual expiration date, as it appears at Internet […]

Read More

Error 0: keyword not found

Cause This error can be found in your Location Fail LogĀ for the website uptime monitors that you have configured keyword monitoring for and the specified keyword that you configured our system to look for is not found on the monitored target page. Our system will look for the specified keyword only in the HTML source […]

Read More

HTTP Code [403] Error 0: (Xms)

Cause These errors can be encountered in your Location Fail Log for website uptime monitors when the monitored website is answering with a 403 Forbidden response towards our monitoring locations. This HTTP code basically means that the website is denying access for these web requests, so the website is not considered UP/healthy by our monitoring […]

Read More

Error 28: Connection timed out after X milliseconds (Xms)

Similar errors Cause These errors can appear in your Location Fail Log when the monitored target fails to respond within the configured timeout time frame. For example: if your website uptime monitor has a configured timeout of 10 seconds, a timeout error happens if your website fails to load within 10 seconds. These errors are […]

Read More

Error 7: Failed to connect to <target>: Connection refused

Similar errors Cause You can get this Uptime Monitoring error in your Location Fail Log if the monitored target is refusing to allow our uptime monitoring nodes to connect to it. This can be caused by any number of reasons, among which: Fix We recommend looking on your server or network to see what exactly is it […]

Read More

This is how we use our own platform when performing non-impacting planned maintenance on our infrastructure

In the following guide, we’ll demonstrate how easy it is to use our platform for your infrastructure management and the few basic steps you can take when performing planned maintenance on your servers. We use our platform ourselves to monitor our non-impacting infrastructure components. The critical infrastructure components should always be monitored from multiple different […]

Read More

How to set up Keyword Monitoring

You can use our Uptime Monitoring system to look for a specific keyword on a website and get notified when that keyword goes missing or changes. To get started, go to your Uptime Monitors dashboard from the client area menu: Click on the “Add Monitor” button to add an Uptime Monitor to your account:

Read More

Error 0: Name or service not known

Similar errors Cause You can get this Uptime Monitoring error in your Location Fail Log if the monitored hostname is not resolved properly. Our monitoring locations do not cache DNS results, so they perform fresh DNS queries on every new uptime check of your monitored target. Fix It is advised to check up on your nameservers to […]

Read More

Error 92: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR

You can get this Uptime Monitoring error in your Location Fail Log if your web server uses HTTP/2 and responds with a connection-specific header field. What is the issue? RFC 7540 indicates that the HTTP/2 response MUST NOT include connection-specific header fields, and if such headers exist, the response is considered malformed. How to find […]

Read More