I like that it's easy to set up, can be easily monitored from anywhere using our mobile apps. It has great support team and friendly community. We use it as part of our CI/CD pipeline in order to check if code changes have broken any scripts or services. Sometimes we get stuck with certain issues and do not know how to fix them even after contacting their support - sometimes they don't respond at all. The biggest problem here is lack of documentation so you need to figure out what does each function mean by reading source codes (which are quite difficult). They also charge extra fees when you exceed your allocated usage. For this reason we decided to roll our own solution using Jenkins instead. However, Healthchecks was still very useful since it helped us monitor other systems such as Redis queues.