Freshping was a website uptime monitoring tool with free and enterprise editions, from Freshworks. The product is no longer available to new customers.
$11
per month, billed annually
SolarWinds Pingdom
Score 9.5 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
$14.95
per month
Pricing
Freshping (discontinued)
SolarWinds Pingdom
Editions & Modules
Blossom - 60 checks (can add more checks)
$11.00
per month, billed annually
Garden - 80 checks (can add more checks)
$36.00
per month, billed annually
Sprout
Free
50 checks (none additional)
Synthetic Monitoring
$10
per month
Real User Monitoring
$10
per month
Enterprise
Custom Pricing
Offerings
Pricing Offerings
Freshping (discontinued)
SolarWinds Pingdom
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Every additional 10 checks - $8/month billed annually
I have used a host of other ping applications that were used to generate responses back from end hosts but that just shows the responsiveness of the host and not the applications. Seeing the response back from an application is crucial especially when a system is taken down …
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.
I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients
The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.
Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.
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.
Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.
Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.
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.
PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem
Honestly, we have 4 other products that overlap this functionality whose organizations provide far superior support. At this point it is an unnecessary expense.
In my opinion, their lack of support responsiveness and commitment has impacted our IT agility.