Checkeroni logo
Why don't you offer feature X or Y?

I understand the importance of offering a cost-effective service that can be accessible to a wide range of users. As a result, I have made some intentional decisions to keep the service basic and affordable.

Advanced features often require additional resources, such as servers in multiple geographic locations for geo-location checks. As a basic service, we might have limited resources and infrastructure to support such extensive capabilities.

By offering a basic service, I aim to maintain a user-friendly experience for all customers. Complex features, while beneficial for some, can make the platform more complicated and less accessible for others.

This service might primarily target individual users, small businesses, or startups who have more straightforward monitoring needs. As such, we focus on providing essential functionalities that fulfill the requirements of this user base.

By keeping our service basic, I can focus on ensuring the utmost reliability and accuracy in the features we do provide. A simple service can often be more dependable and less prone to technical issues.

While I acknowledge that some users might have specific requirements for enterprise-grade features like multi geo-location checks, my aim is to strike a balance between affordability and functionality. I regularly assess user feedback and needs, and if there is significant demand for additional features, I might explore options to expand our offerings in the future. In the meantime, I am committed to providing a reliable, easy-to-use, and cost-effective uptime checking service that caters to a broad user base.

How often do you check my urls?

The bot will automatically monitor your URLs for their availability every 1, 2, 3, 5, 10, 15, 30, or 60 minutes. Our comprehensive monitoring system ensures that we keep a close eye on your urls.

Additionally, in the event that the bot detects your URL as being down, we take extra measures to verify the status through a Cloudflare worker. This double-checking process ensures the accuracy and reliability of our up- and downtime alerts, giving you the confidence to trust our monitoring services.

Checkeroni says my url is down, but I can still visit it. What's wrong?

If the bot reports that your URL is down, but you can still visit it without any issues, the most likely reason is that there might be a problem with the internet route or connectivity between our monitoring servers and the target URL's server. Internet routing is a complex system, and occasional hiccups or network issues can lead to false positive reports of downtime.

Here are some potential reasons why you might receive a false downtime report:

  • Temporary connectivity issues: There could have been a temporary glitch in the network path between our monitoring servers and your URL's server, causing the failure in the monitoring request.
  • Firewall or IP blocking: Some websites implement security measures that could block requests from specific IP addresses, including the ones from monitoring servers. This could lead to a false downtime report.
  • Geographic outage: The URL might be accessible from certain locations but not from others. If our monitoring servers are in a different geographic location from yours, it's possible that we are seeing a different status than what you experience.
  • Server overloaded: The URL's server might be experiencing temporary overload or high traffic, leading to delayed responses to our monitoring requests.
  • DNS issues: There might be DNS-related problems that impact the accessibility of the URL for our monitoring servers.

If the problem persists, or you have concerns, please don't hesitate to reach out to me for further assistance and investigation. I am committed to continuously improving this service and ensuring the accuracy of the uptime monitoring to better serve you.

The bot says my site returns HTTP status code 526. What does this mean?

Sometimes the bot will double-check your url through a Cloudflare worker. They implement its own HTTP status codes alongside the standardized HTTP codes. For example; if you get a 526 error status code it means that you have an invalid SSL certificate. Check out all HTTP status codes here.