Catchpoint Reviews

My main use case for Catchpoint is that it does an excellent job in identifying the entire traffic patterns from the source to destination, and it also provides suggestions for a better path to reach the service much faster.

A specific example of how I used Catchpoint in my previous organization is that we were primarily using it for monitoring our applications and endpoints in specific regions. We were looking for a BGP workflow where the AS group for a particular provider was a lengthier path than the suggested one. Catchpoint was able to identify the particular AS BGP peers and suggest that if we go through this path, it is the fastest way to reach our packets to our destination. The path we had associated with another ISP took a longer time for a response. These features helped us plan in a way that our monitoring improved, our detection time for a particular incident for that application was significantly improved, and we were able to pinpoint exactly where the problem was and come up with a better solution. Based on the suggestion from Catchpoint, the BGP AS number which was associated with it led us to change to a particular provider, which helped us in many areas like mean time to detect and mean time to recover.

Catchpoint helped improve our numbers, and we were successfully able to integrate it with our internal tool, which gave us the right signal to initiate a war room, get the team on the call, and perform a quick troubleshoot and get those fixed as soon as possible. This helped us in many ways, especially our ability to monitor the services of our own application improved compared to waiting for a customer report. We were able to pick up issues much earlier and resolve them much faster.

Catchpoint has positively impacted my organization through detection and remediation. We were successful in getting it implemented internally, and each trigger whenever Catchpoint detected a problem showed an impact. There was no noise associated with it unless a third-party vendor had a problem and our applications were dependent on it. Overall, the improvement in detection and repair significantly improved. Detection was a major point because many applications take their own infrastructure, have their own operations, and have their own monitoring thresholds set up, but Catchpoint plays a good role in terms of detection.

I can share specific outcomes and metrics that improved after using Catchpoint, such as reduced downtime and faster detection. Previously, we were getting customer reports for about four to five incidents out of ten, where approximately 50 percent were customer reports and 50 percent were internally detected. After using Catchpoint, we were close to 90 percent, where out of ten incidents, just one incident came from a customer, and the remaining were detected by internal sources, especially with Catchpoint. This number helped us in terms of reducing downtime. On average, we would take 20 to 25 minutes to fix an issue, but with Catchpoint, we were able to do it within 10 to 12 minutes on average. That time period of downtime reduction of 18 minutes per incident on average helped us in improving our overall numbers associated with both repair time and detection time.

The best features Catchpoint offers include the entire traffic pattern from the source to destination and the hop-by-hop breakdown of all those patterns, including the BGP peers, which was very significant. Catchpoint operates at multiple known locations, and our data centers are in highly used cases. For example, a few data centers we are in are also associated with it, which gives a better and faster response that generates many use cases where we can review more about how Catchpoint can help us in detecting issues. It also performs a ping check every second or every minute based on how the particular service requires it.

Out of those features, the hop-by-hop breakdown of BGP peers is the one that made the biggest difference in my work because I have not seen this feature in others. Other products exist, but this gives very good visualization in the first place, and it also pinpoints exactly the number of milliseconds a particular path takes. By looking at it, on average, if I look at a dashboard we set up, it can give us a better understanding of where we lack and how we can improve. That decision can be much faster compared to where we would have to dig deeper and analyze with a lot of manual effort required. The dashboard visualization gives us a quicker way to justify, take action, and then we actually see the result much faster.

The visualization is also better overall. I have seen in a dashboard it gives me a quick check of where we are, what we are doing, and then how we are doing it, which helps us a lot.

I think Catchpoint can be improved because it is competitively a little costlier. I understand that Catchpoint provides the best solution, but comparatively, if I compare it with Uptrends, New Relic, DataDog, and ThousandEyes, Catchpoint does multiple things, but it comes with a cost. That is one of the areas you can leverage use cases based on customer requirements and come up with a better pricing model. The existing ones are good, but for our use case from Zoom, we were just looking for our endpoints to be monitored every minute, and that cost us a lot compared to the existing tool that we were using. That area is something to look for improvement.

I have been using Catchpoint for close to four years.

Catchpoint is stable.

Catchpoint does a pretty good job in scaling applications drastically. Based on our use case, the migration part, especially onboarding a new application for monitoring, is seamless and does not require a lot of our effort and analysis. It does scale well.

Support was pretty good with Catchpoint. Integration was seamless. We were onboarded to Catchpoint and started testing within a couple of hours. The visualization was good and the UI was also good. In terms of the breakdown of the BGP paths or the traffic from one location to another, the UI was good. The graphical and pictorial representations of all those traffic patterns were pretty highly useful for somebody looking at it for the first time. One of my peers who was also part of the testing got going within a couple of hours, which was much better.

Customer support was good. The initial migration and the initial days of monitoring Catchpoint involved having a dedicated TAM and a dedicated support number that could give us quick answers. All of our questions were answered much faster, and a dedicated document was prepared for reviewing content. Whenever we had a problem, we looked at that document to get those answers. Beyond that, we could call a number to have the support team available for us.

I was not part of the decision regarding why Catchpoint was brought on. I understood the reasoning, but I did not know which other tool they were using. The use case was straightforward: to detect much faster and accurately.

The initial migration and the initial days of monitoring Catchpoint involved having a dedicated TAM and a dedicated support number that could give us quick answers.

Support was pretty good with Catchpoint. Integration was seamless. We were onboarded to Catchpoint and started testing within a couple of hours.

I have seen a return on investment. We definitely saved time by an incident commander who was monitoring the applications. We used to spend at least 30 to 40 minutes on average on a call to detect what the problem was, but that reduced drastically to around 16 to 18 minutes. That time savings has significantly improved our productivity as well as our better monitoring capability. The cost part where each engineer cost comes with the amount of time spent on an incident call or on a ticket, all three factors were included when we looked into Catchpoint.

I was not part of that decision-making regarding pricing, setup cost, and licensing, but as far as I remember, it was pretty good in the early days. I think the cost increased because we were so dependent on Catchpoint for monitoring most of our applications. There was a review check, and after that, I do not remember what the decision was.

We spoke to Uptrends, DataDog, and New Relic before choosing Catchpoint.

I would advise others looking into using Catchpoint to consider that if your use case is more about detecting faster and identifying a root cause, Catchpoint stands as a top contender. It really depends on use cases, especially for someone who has a sensitive application where they want to know every minute if there are transaction failures or login failures. Catchpoint can help you in those areas. I rate Catchpoint highly for organizations with these requirements.

Hybrid Cloud

Amazon Web Services (AWS)

On the Expedia project, we have used Catchpoint for synthetic monitoring, and it is a very good tool that allows us to monitor the application synthetically and at the API level. I had a great experience with Catchpoint, and we represent all the dashboards to the leadership team as well as clients for weekly and monthly updates on any glitches or failures. Catchpoint provides excellent visibility on any failures, indicating at what time they occurred and what kind of errors were displayed, making it clear on the message.

We use Catchpoint in our daily routine tasks to monitor application levels, load, and availability of applications. At any point in the 24 hours, if an application is not available or is facing slowness making it difficult for users to access, Catchpoint captures those logs. With Catchpoint, we analyze the time duration of issues to identify why these occurrences happen, allowing us to fix them quickly and provide availability of over 99.98%. The analysis we conduct with Catchpoint proves invaluable for any upgrades, patches, or issues needing analysis.

An unexpected situation we faced with Catchpoint was when a payment gateway failed, preventing customers from onboarding or making bookings smoothly. We analyzed what was happening at that time, why the payment gateway failed, or why the application was unavailable, which allowed us to raise these issues with the leadership team before any further escalations, sorting out the cases efficiently.

Catchpoint offers several best features, including an error dashboard, successful transaction tracking, failure comparison, and the ability to set thresholds. If errors exceed the threshold, it indicates issues, and we can set alerts for any complications, allowing automatic emails or notifications to be sent to clients. We utilize both tabular and visual formats for analysis, as they provide a clear picture in the dashboard, which we can incorporate into our presentations.

Catchpoint has positively impacted our organization by saving a lot of time and preventing outages. Prior to any significant outages, we are able to identify issues needing permanent fixes and minimize reoccurrences. It enables our team to analyze data, capture detailed assessments, and streamline identification of automation and improvements, ultimately enhancing our monitoring and availability of systems.

One improvement for Catchpoint is the detail analysis logs that we struggle to find within the tool. We currently depend on other systems, like Splunk, to access those log files. If Catchpoint could incorporate these features, it would greatly enhance our end-to-end analysis capabilities in a single point of contact.

Another improvement area for Catchpoint is more precise and detailed error logs capture capability, which would enhance our monitoring and analysis process.

We believe that the dashboard could be enhanced with more tags and customization options to allow further personal tailoring of features and alerts, which are currently somewhat restricted.

I have been using Catchpoint for around four years in my project on the Expedia Global project, which is a global travel platform and hospitality company.

I have not encountered any major outages or issues with downtime regarding Catchpoint; it has proven to be a stable product.

Catchpoint's scalability effectively manages our growth without increasing demand. Based on our current organizational architecture, it efficiently handles traffic and monitoring requirements.

Customer support for Catchpoint has received positive feedback, as the visualization in tabular and bullet formats effectively represents errors and glitches. This clarity aids troubleshooting and supports engineers in meeting customer satisfaction.

We previously used other monitoring tools like Grafana, Prometheus, and NetAct. Those solutions proved more expensive in licensing and resource consumption, which led us to switch to Catchpoint for better accuracy and efficiency.

We have seen considerable returns on investment with Catchpoint, saving both money and employee time while reducing penalties from clients due to fewer outages during network deployments.

My experience with Catchpoint concerning pricing, setup costs, and licensing is straightforward. While there are occasional challenges with setup costs and financial aspects, overall, my experience remains positive without any significant challenges.

Before selecting Catchpoint, we evaluated other options. Ultimately, we found that Catchpoint was the most feasible for our project within our budget, architecture, and monitoring accuracy, making it the best choice.

I rate Catchpoint an eight out of ten because of its fast resolutions, proper integrations, and effective alerts and notifications, alongside its synthetic monitoring capabilities.

I chose eight out of ten because of some restrictions in Catchpoint, such as the unavailability of detailed logs for monitoring any glitches. Customization options are also limited, and while other tools like DataDog and Grafana offer these features, Catchpoint lacks certain functionalities.

For AI governance and security, we need to improve security measures due to multiple third-party integrations. Enhancing AI security is essential to prevent threats or vulnerabilities to applications, ensuring safe monitoring of confidential network traffic.

I find that the AI-based insights from Catchpoint are trustworthy, but we still need to focus on enhancing security. For instance, we must stop external attacks or non-secure traffic and manage any hacker-related traffic that could affect application networks. The AI security insight is reliable, but continued improvements are necessary.

My advice to other vendors or organizations is to switch to Catchpoint due to its accuracy, lightweight deployment, and budget-friendly nature. It is invaluable for synthetic monitoring and captures crucial metrics reliably. With trustworthy AI security, available integrations, and customizations, coupled with clear dashboards, Catchpoint serves as a helpful tool for enhancing project communication. Our clients, in turn, are pleased with its efficiencies, leading to significant financial and time savings for both teams and clients. I rate Catchpoint an eight out of ten overall.

Private Cloud

Amazon Web Services (AWS)

My main use case for Catchpoint is synthetic monitoring. We use synthetic monitoring with Catchpoint to monitor the customer journey of our clients on our e-commerce sites, so we can proactively detect failures or errors that could affect our customer experience.

The best features Catchpoint offers include the ability to program many steps in synthetic scripts, create performance reports about my sites, and an easy UI that I can clearly use without any troubles. The easy UI helps me in my daily tasks because it is very easy as a user to create and navigate the Catchpoint interface, and regarding the performance reports, we use them daily to analyze those reports and find out if we need to do some configurations or troubleshooting to improve our sites, ensuring our customers feel good about buying from us and that they complete their journey from the home page login loading to the cart or even the paid page of their cart or product.

I would love to have RAM monitoring available in Catchpoint, which would be a nice feature for both synthetic and real user monitoring, and it would be an amazing tool that I would love to have, complementing each other.

I would like another feature to make it easier to use the report section of Catchpoint. I would appreciate more detailed reports about my sites. Learning how to configure it and what kind of data Catchpoint can generate would help me in my daily tasks, especially with the business part of my enterprise focused on e-commerce.

I have been using Catchpoint for about two years.

Catchpoint is really stable.

We previously tried using Dynatrace, but it was really expensive for us, and when we discovered Catchpoint, we fell in love with it. We evaluated Dynatrace before choosing Catchpoint, but it was too expensive for us, leading to its discharge.

I do not have information right now regarding how much downtime we have prevented, but I believe we have an 85% success rate in detecting website issues before they impact the client, which I think is a good metric.

My team is responsible for monitoring and using Catchpoint to collaborate with the e-commerce support team, so when an alert is triggered on Catchpoint, we use it to report that issue to support, enabling them to troubleshoot before it impacts the client. We efficiently use the historic information in Catchpoint with our architecture team to identify necessary improvements from our provider's infrastructure side, demonstrating how helpful Catchpoint is for us.

My team works closely with incident management, allowing us to detect when an alarm triggers in Catchpoint, so I immediately open an incident with the support team for them to troubleshoot. Catchpoint has helped us improve our response times significantly; previously, we would wait until the customer reported an issue, but now we proactively address performance issues on our sites as soon as they arise.

We evaluated Dynatrace before choosing Catchpoint, but it was too expensive for us, leading to its discharge.

With compliance, we need a monitoring platform for our e-commerce sites, and after some research, we found that our home office in Bentonville uses Catchpoint to monitor a part of their e-commerce sites, so we added it for our market use.

Regarding resource optimization, we are currently reviewing all the performance reports generated by Catchpoint to gather ideas on how to optimize our e-commerce sites and manage costs while maintaining nice site performance.

We are currently using Catchpoint's reports for capacity planning on our e-commerce sites, setting up information to send to our provider to help make decisions about improving infrastructure or identifying issues they might have.

Currently, we do not use Catchpoint for business continuity or disaster recovery plans; we only use it for monitoring.

I do not manage Catchpoint at work, but I have seen that it has passed all our security tests, so I think it has nice governance and security configuration.

I recommend having some training before using Catchpoint, as it has many features that can help users with monitoring, reports, and other activities. If you are looking for a platform or tool that excels in monitoring or synthetic monitoring, I would definitely recommend Catchpoint.

Public Cloud

Other

For Catchpoint, it has been a year since I have been using Catchpoint primarily for monitoring our Atlassian SaaS applications, specifically Jira and Confluence.

Our monitoring focused on several key areas with Catchpoint. First was authentication, where we monitored login flows to ensure users could successfully authenticate. Second was page load performance, where we tracked how long important Jira and Confluence pages took to load. We also monitored functional workflows such as opening projects, navigating spaces, and accessing commonly used pages. Finally, we covered API monitoring to validate that important backend endpoints were available and responding within acceptable thresholds.

We stimulated real user experience by using a service account that would log in to Jira or imitate the login workflow to check if the authentication login workflow is working fine with Catchpoint, and we used a browser-based authentication process.

We primarily use it to monitor Jira and Confluence, including authenticated user journeys, page load performance, functionality, and API endpoints.

We did not have to update Catchpoint monitors very frequently once they were stable. Most changes happened when the applications themselves changed. For example, when Atlassian updated the UI or changed page elements in Jira or Confluence, some of our synthetic monitors had to be adjusted because they relied on specific element locators. We would update the scripts or selectors, test them, and redeploy the monitor. Overall, it was a smooth process, although it did require some maintenance whenever the application changed significantly. Once the updates were made, the monitors continued to work reliably.

When Catchpoint detects an issue, an email triggers to our team distribution list. The first step is for the alert to notify the operations team. We review the alert details and associated metrics to understand whether it is an availability issue, a slowdown in page load, a failed authenticated transaction, or an API performance problem. If the issue is confirmed, we investigate further by checking the affected Jira or Confluence service, correlated with application and infrastructure logs, and determine whether it is a temporary issue or something requiring immediate action. If needed, we escalate it to the appropriate application or infrastructure team. Once the issue is resolved, we verify through Catchpoint that the monitors are healthy again and close the incident.

Overall, Catchpoint met our expectations. We used it to monitor Jira and Confluence, including authenticated user journeys, page load performance, and functionality checks. The monitors are reliable, and the alerts give us early visibility into performance issues before users report them. It also provides enough diagnostic information to help us identify where the shutdown or failure is occurring. For our monitoring requirements, it performs well and meets our needs.

One thing I really appreciate about Catchpoint is its synthetic monitoring capabilities. Instead of waiting for users to report issues, we could stimulate user journeys at regular intervals. That helped us identify slowdowns or failures proactively, especially for business-critical workflows. This aligns well with Catchpoint's focus on synthetic transaction monitoring and proactive digital experience monitoring.

The alerting functionality in Catchpoint provides value. We configure thresholds for response times and failures so that our operations team could be notified whenever authentication failed, APIs became unavailable, or page performance degraded beyond acceptable limits. This reduces the time needed to identify issues and begin troubleshooting. From a usability perspective, I found the dashboards useful for getting a quick overview of application health, making it easy to see trends in availability and response times over time. When an issue occurred, having historical performance data helped determine whether it was a temporary spike or part of a larger pattern.

For example, we have applied alerting on create pages on Confluence. The slowness, even if we have added a response time on our monitors, and if the page does not load in between that time or takes more than the defined time, we would be alerted. That way, we were notified about the issue before even a user responds about the slowness. We have defined thresholds for every page load or workflow in our application.

Catchpoint has positively impacted our organization by providing reliable visibility into performance and availability of our Jira and Confluence environments, giving us confidence that critical user journeys are being continuously monitored. For an organization that relies heavily on SaaS applications and wants proactive monitoring instead of waiting for end-users' complaints, I think it is a solid solution.

The improved response time is noticeable since using Catchpoint.

For some larger workflows, I think the product could improve in a few areas. As the number of synthetic tests grows, managing them can become more complex, so that is the area I believe Catchpoint can really focus on to improve how we can have better visibility even with multiple synthetic tests.

I also think simplifying the investigation workflow when drilling down into failures could make troubleshooting faster.

The reason it is not a full ten, or why I rated it eight, are mainly around ease of managing larger monitoring environments and making troubleshooting workflows a little more streamlined.

To be transparent, I did not directly use Catchpoint's AI capabilities, so I cannot comment from hands-on experience about its governance or security. My work focuses on synthetic monitoring, but I was not involved in evaluating or confirming any specific governance features, so I prefer not to speculate beyond my actual experience.

I have been working as a Cloud DevOps engineer for five years and managing the Atlassian platform.

I have not seen significant downtime or reliability issues with Catchpoint.

I would rate Catchpoint's scalability around eight out of ten. It comfortably supports our growing monitoring requirements, although I do not have first-hand experience with very large-scale global deployments.

Catchpoint's customer support is really helpful. I have talked to them and logged support tickets, and they would invest in it and escalate your issues. The experience was really great with them.

I would rate the customer support nine out of ten, as if they did not have the solution because of Catchpoint's limitation, they would fairly give alternatives or make the monitor work. They would literally write Playwright for you if you cannot get the element right.

We were previously using DataDog, but since we moved to the SaaS solution and needed browser-based monitoring because we do not have any instances or resources on-premise, we switched to Catchpoint as a solution.

I would say the initial implementation of Catchpoint is moderately straightforward. The basic setup is fairly easy, but configuring meaningful synthetic monitors, especially for authenticated user journeys in Jira and Confluence, requires some planning and testing. We have to make sure the authentication page flows, page validates, and API checks accurately reflect real user behavior. Once those monitors are in place, ongoing maintenance is minimal, and the platform is reliable. Overall, I would not call it difficult, but there is a learning curve to getting the most value from its features.

I was not the primary administrator for Catchpoint, so I was not heavily involved in managing user access or permissions. From my perspective as a user, I had the access needed to create and manage monitors, review dashboards, and investigate alerts. We did not run into any issues with permissions during my day-to-day work, so it seemed flexible enough for our team's needs.

We did not track formal ROI metrics, but Catchpoint helped us save time by identifying performance issues early and reducing troubleshooting effort. I cannot provide specific numbers, but it improved our operational efficiency.

Catchpoint was already being used by our organization, so we did not evaluate other options. We compared it with DataDog and found Catchpoint better.

The reporting and analytics in Catchpoint are useful for our monitoring needs. We primarily use the dashboards and performance reports to track page load times, authenticated transactions, and API response times for Jira and Confluence. When an alert is triggered, the metrics help us understand whether the issue is related to authentication, page performance, or an API endpoint, which makes troubleshooting more efficient. The dashboard provides enough visibility for our operations team to identify trends and investigate performance issues over time. While we did not use Catchpoint as a business analytics tool, its reporting was valuable from an operational and performance monitoring perspective.

Catchpoint's AI capabilities are great, and while I have not explored that feature as of yet, the visibility I have around it is good. The governance is intact, and it does give you the required information and helps you set up monitors more easily.

My advice to others looking into using Catchpoint would be to start by identifying your most critical user journeys and business transactions before implementing it. Focus on monitoring the workflows that have the biggest impact on your users. Spend some time designing those synthetic monitors properly, because that is where you will get the most value. Also, be prepared to update monitors occasionally when the application UI changes. For example, we have to make adjustments when Atlassian changed elements in Jira and Confluence. Once everything is configured, Catchpoint provides reliable monitoring and proactive alerts that help identify performance issues before users are affected. I have rated this review eight out of ten.

Private Cloud

Other

My main use case for Catchpoint is to check website availability in different regions so that we can be aware of any downtimes.

A specific example of how I have used Catchpoint to check website availability is when we check DNS propagation. We analyze how it is working and which locations it has propagated because sometimes clients reach out to us that a website is not available in a certain location, which could be due to DNS propagation. Catchpoint helps with those pain points, and we also use it to monitor when a website struggles on the CDN.

In my opinion, one of the best features Catchpoint offers is the detailed alerting, which not only points out outages but also provides a lot of information in the alerts.

I find the alerting details helpful because, working for hosting organizations, it is tough to identify issues due to third-party providers, such as a CDN. The alerts contain all the details, such as when a website is failing to load due to a CDN issue, such as a 503 error at the CDN.

I think Catchpoint helps us detect issues before anybody could report them, which can impact clients because it provides prior monitoring that also sees outside the infrastructure, meaning outside the backend.

Catchpoint positively impacts our organization by helping us build customer trust, as customers do not care if the issue comes from the backend or our infrastructure. It allows us to determine issues that are not related to our services, which builds good trust with customers, and they know we are working on downtimes.

I believe Catchpoint's accuracy and reliability of output is impressive because it finds issues before anyone else does. Even if a website viewer identifies a problem, Catchpoint has good global coverage on outages and checks application statuses continuously, reporting them immediately.

Catchpoint has good scalability and is stable.

Catchpoint is very great software for troubleshooting APIs, websites, availability, and other third-party services such as CDNs, which makes it stand out.

I think Catchpoint should have licensing models for individuals or very small organizations, and there is no auto-tuning for alerts, so auto-tuning features for alerts would be beneficial.

I have been using Catchpoint for around two years.

Catchpoint is stable.

Catchpoint has good scalability and is stable.

I have not interacted with customer support. I read the documentation for monitoring details instead.

I did not previously use a different solution.

My experience with pricing, setup costs, and licensing is that you just need to buy the licenses, and the team sends you the license keys, which is pretty easy. I am not sure about cost-effectiveness because that was decided by the organization, as I was the monitoring person.

I believe we see a good return on investment with Catchpoint because you only need one or two people to monitor, so you do not need a larger team. This way, the license count is also reduced, and you build customer trust, which we market as a feature; that is what our organization did, indicating a positive ROI.

My experience with pricing, setup costs, and licensing is that you just need to buy the licenses, and the team sends you the license keys, which is pretty easy. I am not sure about cost-effectiveness because that was decided by the organization, as I was the monitoring person.

I did not evaluate other options before choosing Catchpoint.

My advice to others looking into using Catchpoint is that if they need to check third-party services, they should consider buying it. Otherwise, if it is related to the infrastructure, they may not need to consider it, but it is pretty reliable for other services. I would rate this review a 9.

Public Cloud

Amazon Web Services (AWS)

My main use case for Catchpoint is mostly automating. I use Catchpoint automatically for automated monitoring of our various UIs and also the backend APIs. We rely on Chrome and Selenium and JavaScript automation type.

Catchpoint offers great features, including web browser testing, UI testing, API testing, and many other good features.

We find ourselves mostly using Playwright JavaScript and Chrome-based UI testing, which stands out the most for us.

Catchpoint has impacted my organization positively by speeding up the process in detecting issues much earlier, even before the business reaches out. I can now detect issues almost two hours earlier than what it used to take from the field.

Catchpoint can be improved by supporting some of the APIs and other technical testing with some kind of metric validations as well. I do not have anything more to add about the needed improvements, particularly related to UI or reporting.

I have been working in my current field for almost eight years now.

Catchpoint is stable.

Catchpoint's scalability is good; it can clearly detect any kind of performance issues, and you can spin up new VMs or instances if required.

The customer support for Catchpoint is really good; they get you on the call and will assist you if you are mixed up or blocked with some kind of coding. I would rate the customer support a 10 on a scale of 1 to 10.

We used Blue Prism previously, and Blue Prism was more time-consuming in terms of developing; that is why we leveraged Catchpoint.

I have seen a return on investment, and I think it saves everything in terms of money and time, as we are using it on a day-to-day basis.

My experience with pricing, setup cost, and licensing is that I am not directly involved in pricing, but the pricing is very decent.

Before choosing Catchpoint, we have not leveraged other options; we just use Catchpoint.

I would advise others looking into using Catchpoint to start leveraging it if they have not started already. I would rate this review a 9 out of 10.

Hybrid Cloud

Other

My main use case for Catchpoint is external website monitoring.

I use external website monitoring with Catchpoint in my company by checking whether websites are reachable from certain countries and what the performance of the websites is from those countries.

In my opinion, the best features that Catchpoint offers are the regions from which monitoring is done and the graphical overview of the data.

The specific advantages I see in the fact that Catchpoint enables monitoring from different regions are that you can make country-specific queries and know in which country a site might be blocked or is slower, which is very important if the website needs to be available worldwide.

I also appreciate that reporting is a very important and good feature, along with the dashboards.

Catchpoint has had a positive impact on my company because we have a good overview of the worldwide availability of our sites, at least in the countries where we need to make them available.

I can specifically tell you that we were able to meet the internal KPIs we set, since with Catchpoint we were able to confirm that the KPIs had been met.

I don't think of anything that could improve Catchpoint at the moment.

Perhaps I would like to see better integration with other tools.

I have been using Catchpoint for eight years.

In my experience, Catchpoint is stable.

I rate the scalability of Catchpoint as good.

How I find the customer support of Catchpoint depends on who I have as an account manager at the time, but overall it is quite good.

I did use another solution before Catchpoint, which was Neustar.

I switched because Catchpoint has better capabilities.

My experience with pricing, setup effort, and licensing with Catchpoint is that it is not the cheapest product.

I consider the investment to be justified for large companies; definitely so for large companies. For small and medium-sized businesses I see a big problem, as large companies can handle it while small and medium ones, I do not think so.

Before deciding on Catchpoint, I evaluated a few other solutions, though I do not remember exactly which.

My advice for others considering using Catchpoint is to evaluate the costs carefully and evaluate the integration capabilities carefully. I would rate this review an 8.

Public Cloud

Other

My primary use case was monitoring the availability and performance of applications and services to help identify potential issues and ensure a reliable user experience. Although my experience with the platform was relatively brief, I found it useful for proactively monitoring system performance and supporting troubleshooting efforts.

t provided visibility into potential issues before they affected end users, which supported faster troubleshooting and issue resolution.

The dashboards and Real User Monitoring (RUM) features were the most valuable to me. They provided visibility into the performance experienced by actual users, which helped the team better understand real-world application behavior and identify potential performance issues.

Overall, Catchpoint had a positive impact by helping reduce downtime through proactive monitoring, improving visibility into application performance, and supporting a better end-user experience.

There is room for improvement in terms of the overall user experience. I think the interface could be made more intuitive, especially for new users, and some areas of the platform could benefit from better guidance and documentation. Those are the main reasons I rated it 8 out of 10.

I've used Catchpoint for around 2 months

No, I did not use a different digital experience monitoring solution before Catchpoint. Catchpoint was the first platform I worked with for monitoring the performance, availability, and reliability of websites, applications, and APIs. During my time using it, I found it to be a reliable platform that provided good visibility into application performance and helped support proactive monitoring.

No Experience

I wasn't involved in the evaluation or selection process, so I can't comment on which other solutions, if any, were considered before Catchpoint was chosen.

I would rate Catchpoint 8 out of 10 overall.

My advice to organizations considering Catchpoint is to clearly identify their monitoring requirements and make use of the platform's dashboards and Real User Monitoring capabilities, as they provide valuable insights into application performance and the end-user experience. Catchpoint is a powerful platform that offers excellent visibility into the performance and availability of websites, applications, APIs, and network services.

While my experience with the platform was relatively brief, I found it to be reliable and effective. I believe there is room for improvement in terms of user experience and making some advanced features easier to configure, but overall, it is a strong solution for organizations looking to proactively monitor their digital services.

My main use case for Catchpoint is to observe anomalies in the infrastructure. For example, when server memory gets exhausted, Catchpoint sends us a notification, and then we react to it and solve the issue. I use Catchpoint for multiple infrastructure alerts such as CPU, RAM, IOPS, and any application down, so I rely on it for multiple purposes.

Catchpoint has positively impacted my organization because we have supported multiple customers and handled many escalations before they became critical issues. Catchpoint alerted us with the defined threshold, and we solved the problems before they escalated. We have seen a reduction in escalations, and apart from that, we have saved our SLAs.

The best feature that Catchpoint offers me is a dashboard to monitor all anomalies on one page. What I appreciate most about the dashboard is that the color coding itself highlights the failures and running services, which is great. The customization is easy, and the connection between it and outside tools is seamless, so those are the good things about Catchpoint.

Catchpoint is working fine. I believe the connection with Snowflake, AWS, and other new upcoming AI tools should be easier, especially the configuration with AI tools and LLMs.

I have been using Catchpoint specifically for four years.

Catchpoint is stable.

Catchpoint's scalability is good; it can be increased as per the requirement, and updating the license for the number of users is easy to do in Catchpoint.

Catchpoint's customer support is good, and they are very responsive.

Previously, we used Zabbix, and we found that Zabbix had some limitations; that's why I moved on to Catchpoint.

I have seen a return on investment; it is time saved and money saved.

My experience with pricing, setup cost, and licensing is that the pricing is good, and the licensing is also good; that's why we opted for Catchpoint.

Before choosing Catchpoint, I evaluated other options such as OP5.

Regarding Catchpoint's AI capabilities, the governance and security are really high and can be defined as per the different policies and processes of the company. I have not worked on the AI solution of Catchpoint. I would definitely recommend Catchpoint to others. I gave this review a rating of 9.

On-premises

We are using this for an eCommerce product for live customers. This is used to monitor business performance, checking if customers are able to make payments on time or if they encounter issues during online shopping. If there are issues in a specific market, we can monitor the entire country and identify the frequency of issues. We wait for 15 minutes and, if the frequency increases, we take quick action.

One of the features, the scatter plot, is very useful. It shows red dots wherever there are issues. Another feature is regional filtering, which allows us to filter the market based on risk. For instance, suppose we want to identify issues in all markets over the last twenty-four hours. These are the two features we use most frequently.

As part of the improvement, there are certain categories, like for the China market, where we face issues. We are currently using an external tool, Splunk, for reporting. If we could receive similar data for the China market as we do for North America and Asia Pacific, this would be helpful.

I have used the solution for around four years.

So far, we have not found any issues. During business hours, it has worked absolutely fine without any issues.

I haven't reached out to technical support so far, so I'm not sure about it. I did not contact anyone in Catchpoint technical team.

The initial setup is very simple. There is no complexity in that.

We have Grafana, which is a tool for monitoring at the functional level. However, this functional level is not available in Catchpoint.

Overall, for Catchpoint, my advice is if there is any plan for improvement, it would be helpful, and maybe the number of users will increase. I would give a rating of seven out of ten.

Public Cloud