Catchpoint is used for Synthetic monitoring of internal IT resources from various internal office locations and also for Product observability initiative from various last mile connectivity networks and cloud locations in accessing and using the cloud software products to measure the customer impact, connectivity challenges and product usage challenges. Real User monitoring is out of scope currently and IPM is under deep dive evaluation.
Pros
Our standard operating material documents Catchpoint’s breadth on HTTP/Browser, API, Streaming, DNS, FTP, TCP, SMTP, Ping, Traceroute, SSH with content validation and custom widgets/dashboards. This gives SREs and L0/L1 a single place to validate both page flows and the underlying network/application protocols.
Product runbooks use Catchpoint to validate critical steps (for ex, login, overview dashboard, unit dashboards) and to detect DNS issues that break those journeys. so we catch experience regressions even when the backend looks healthy.
We’ve standardized Catchpoint alert categories/templates with ITSM so L0 includes the right analysis in handoffs. This tightened “first message, best message” during incidents.
Our operating procedures use Catchpoint for alwayson availability checks with email notifications and multi‑location verification when a site is down. This is useful for unambiguous “is it up/where is it failing” signals.
Cons
Catchpoint excels at realtime monitoring but offers only basic trend analysis. We noted that historical insights and advanced anomaly detection are weak compared to other observability platforms which provide richer forecasting and correlation features. This limits proactive problem prevention and long horizon of capacity planning.
Catchpoint does not provide deep application level visibility like code level tracing, log ingestion, or distributed tracing. It is inability to correlate API and frontend failures with backend logs or infrastructure metrics is a challenge. This forces teams to rely on other tools for full stack troubleshooting.
Catchpoint lacks AI powered anomaly detection and automated remediation. This gap means more manual triage and slower MTTR during incidents. Internal roadmap discussions flagged this as a strategic limitation for predictive observability.
Likelihood to Recommend
For black box monitoring of applications and end points connecting to external systems, third party systems and also other internal applications. Deep dive public performance of Internet facing applications across the globe.
VU
Verified User
Director in Information Technology (Industrial Automation company, 10,001+ employees)
We use Catchpoint to inform us about the breaking change to the production for L'oreal's brand's sites. Any breaking changes trigger the email for which we need to resolve the issue asap to minimize the loss of revenue. Also, it "starts" the mail if any 3rd party implementation is failed or is down for some reason.
Pros
Code is not available
3rd Party Application is down
In Salesforce cloud commerce, any important piece of XML in Business Manager is not available (like System attributes, shipping methods, services)
During the release of the new website
Cons
Making Catchpoint highly reliable
Should be available in other countries.
Reliability should be measured on users metrics
Likelihood to Recommend
Working as a support developer for loreal, alerting was the main feature that helped us in improving efficiency. Whenever some breaking changes occur to the site, it immediately triggers the email which helps in minimizing the loss of revenue to the client as we as a developer would the issue immediately to resolve it or raise an alarm to the 3rd party if they are the reason.
We use this tool to continuously monitor our sites and their performance, like PDP performance and site load issues. After every build, we run a Catchpoint system on it to monitor if something is broken on our sites. This tool has been really helpful in mitigating a lot of mishappening due to site performance and quickly making a decision regarding what went wrong. Overall this product has been a real time-saver in such unpredicting times and really a great tool to work with
Pros
This tool gives us the notification regarding the down time of certain pages
It helps in collecting the mobile device performance of the site as we are using a mobile-first approach. The performance of our mobile sites helps in deciding the new approach of designing the future designs as the mobile traffic is performance-sensitive
Whenever we integrate other systems it helps us in giving a clear picture of how much site performance has been impacted by enabling certain features hence they allow us to make decisions to optimize the code for that integration
Cons
The Catchpoint tool sometimes gives immediate notification alerts when certain pages are down. This becomes sometimes false alert for us, for example, if the system is on maintenance then it gives notification regarding them at all times
Catchpoint should use some machine learning techniques regarding the traffic on site and based on those should send out or process the decision to throw a notification.
There should be a provision in Catchpoint to add certain non-availability times of our server so that we can relax the notification for some time so that we are not notified of false flag alerts if the system is on maintenance then we should configure the times in catch point so that notification can be relaxed
Likelihood to Recommend
When we do a build on our system, it helps in immediately point out the areas affected by recent builds and helps us make a decision in future planning of our scope of code change, and improve the code quality of our deliverable by helping us always to be mindful of what you send in the build and it's particular impact hence narrowing down our scope of changes and help us make a better decision regarding the coding process and build process as well.
VU
Verified User
Consultant in Information Technology (Cosmetics company, 10,001+ employees)
We currently use Catchpoint to monitor externally-facing endpoints, checking for health, latency, and errors. This provides us a level of monitoring and observability over these endpoints, and alerts us when a service is down or degraded.
Pros
Geographically-based latency monitoring
Endpoint health monitoring
REST response testing
Cons
Adding an endpoint to be monitored requires a lot of steps (since there are a lot of functions and features). A quick-add feature would be nice. If the settings are similar, the interface allows you to duplicate an existing setup and tweak the settings.
Likelihood to Recommend
Catchpoint has a vast and robust interface for all kinds of endpoint monitoring and testing. It is reliable, somewhat easy to configure, and can integrate into many third-party alerting tools. Setting up many endpoints can take a while, so a "quick add" or "bulk add" feature would be helpful. The interface is constantly being updated and improved based on user feedback, so if those features don't exist, they'll probably exist soon.
VU
Verified User
Manager in Information Technology (Computer Hardware company, 501-1000 employees)
We utilize Catchpoint to identify site issues that may be the result of programming, hosting, DNS, or other service providers. Part of this is done through a dashboard and also through email alerts when response times cross a specified threshold.
Pros
Track trends through a smart board
Customizable alerts
Provide breakdown of site load
Cons
Improve alert management to minimize false positives
[Create a] more user-friendly UI
[Improve] long term Smart Board refresh capabilities for use on remote viewing (i.e. wall-mounted screen)
Likelihood to Recommend
Catchpoint is an excellent service when tracking down issues. It also has an alert system to proactively detect problems. It is difficult to massage the alerts to prevent false positives, but it does find issues if they arise. They could improve by providing better dashboards that could be displayed on a monitor and [that don't] require intervention to refresh or login regularly.
VU
Verified User
Manager in Information Technology (Consumer Goods company, 11-50 employees)
The primary use of Catchpoint at our company is to ensure our websites are available and reachable to our end users. One of our main reasons for selecting Catchpoint was because they had testing locations near the backbone providers instead of just cloud locations as with our other testing tools. Additionally having the traceroute data has been very valuable in troubleshooting networking issues.
Pros
Large Selection of locations to use for testing.
Excellent reporting and data metrics collected.
Lot of flexibility in creating Alerts to reduce noise.
Traceroute data collection.
Filmstrip functionality to see how the page is loading over time.
Cons
Have not really noticed any areas that needed any major improvements.
Likelihood to Recommend
If you are looking for a tool to measure actual end-user accessibility to your sites then this has to be one of your synthetic monitoring solutions. All the other vendors only provide cloud-based testing locations.
Catchpoint is used across multiple departments to analyze overall site performance.
Pros
Catchpoint's analytics capabilities are great, intuitive to use, great slicing and dicing of data.
Catchpoint's customer success efforts improve the overall value we get out of the platform.
Cons
Would like Catchpoint to replace awful canned scheduled reports with customized ad-hoc reports built from the Performance tab.
Pricing for Catchpoint Points is too high. Limits the number of tests we use.
Likelihood to Recommend
Excellent performance monitoring platform. As an ex-Keynote customer and an ex-Gomez customer, we are uniquely positioned to compare the available platforms.
VU
Verified User
Manager in Information Technology (Computer Hardware company, 5001-10,000 employees)
