Pingdom is part of an essential toolset I use to make sure our applications are up and running
January 19, 2022

Pingdom is part of an essential toolset I use to make sure our applications are up and running

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version


Overall Satisfaction with SolarWinds Pingdom

We use Pingdom to monitor 30+ different web endpoints in terms of uptime - both internal and 3rd party applications. We have a team of admins that monitor different services and are notified within a minute via the Pingdom app, text, and email when anything goes down. Pingdom also gives us insight into what caused the error. This is an invaluable tool!
  • Timeout alerts.
  • Errors that result in non-200 HTTP responses.
  • Alerting us via different methods (SMS, notifications, email).
  • Allowing us to test uptime of internal applications.
  • Allow us to setup alerts that are more complex (not just an HTTP post/get request ... but something that is able to test an application that requires authentication).
  • Everything else is pretty straightforward and robust.
  • Helps us mitigate downtime at a moment's notice.
  • The price is reasonable.
  • The number of users we are allowed to have in our account helps us avoid the 'single point of failure' issue.
Pingdom is best at what it does: simple uptime checks.
It is the best product for the type of monitoring we want to do. The price is right. It is reliable.

Do you think SolarWinds Pingdom delivers good value for the price?


Are you happy with SolarWinds Pingdom's feature set?


Did SolarWinds Pingdom live up to sales and marketing promises?


Did implementation of SolarWinds Pingdom go as expected?


Would you buy SolarWinds Pingdom again?


The best use case for our Pingdom implementation is to monitor uptime, from multiple locations, publicly accessible web endpoints. For that use case, it is invaluable. The use cases where Pingdom lacks is being able to monitor private resources. It also lacks the ability to troubleshoot code-level errors.