Catchpoint Internet Performance Monitoring Platform

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.

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.

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

I switched because Catchpoint has better capabilities.

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 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.

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.

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.