CaptainDNS vs. Freshping (discontinued)

Freshing is well suited for user-facing systems, the systems they directly use. It also serves as nice eye-candy for them to look at. It does not monitor internal IT systems as well as we had hoped, so we use other tools to monitor those systems.

Incentivized

• The UI is neat. It's very easy to use, and with lots of information.
• It's very easy to set up.
• The "badge" feature is interesting for showing up on institutional website.

Incentivized

• Better integration with Freshservice to generate tickets
• Monitor internal systems
• Better ability to customize

Incentivized

It's perfectly easy and straightforward to use. There's no need to read documentation, you just register and will surely be able to configure whatever monitor you want to set up. It's also very easy to use other features like the status page, reporting, alerts, etc.

Incentivized

To date we have had no need of support from Freshping, it has just been that easy to use. It is highly intuitive and self-explanatory.

Incentivized

We use Uptime Robot, and also some internal health checks, which report directly to our emails and chat applications. They all work "pretty fine," but unfortunately all of them have had some false positives or missed some minor downtime, so as for us, it doesn't add too much overhead, and we prefer to use several. I would say all the ones mentioned are good for the job.

Incentivized

• Good visual for end users
• Adds another check to verify uptime/outages
• Cost for us was free, so we had nothing to lose by adding it

Incentivized