Catchpoint offers over 800 public nodes including Backbone, Cloud, Last Mile, and Wireless node types, as well as the option to install your own on-premises Enterprise nodes. These points of presence can help you build a holistic monitoring strategy that will quickly detect suboptimal experiences from anywhere in real-time to ensure the speed, reachability, reliability, and availability of all your digital services.
How do Catchpoint nodes work?
Catchpoint nodes are configured in specific physical locations and connect to a single ISP (with a few exceptions where single-homed connections are not an option). These nodes are directly linked to the ISP in that geographic region. For example:
• Node A is located in LA and connected to Verizon.
• Node B is located in LA and connected to Comcast.
Node A and node B have multiple servers to help scale capacity based on test volume. Our Backbone nodes reside in top-tier data centers with dedicated ISP links, thereby providing you with the best visibility into your services, network routing, and providers. We have designed our nodes to minimize noise by having a stateless architecture and not storing test configurations, but instead, fetching them in real-time from our Command and Control (C&C) infrastructure.
With so many node types and locations to choose from, it’s crucial to know which ones are appropriate for your unique requirements. Each variant is slightly different in terms of its configuration, offering different perspectives and data points to help you figure out what went wrong, where it went wrong, and why the problem occurred.
How does Catchpoint monitor node health?
All nodes are monitored for the ratio of Successful Tests vs Total Tests, or what we call the Run Rate. When a node has Run Rate issues (<=95%) during a 15-minute period, we determine whether the issue is due to misconfigured tests or if it is a Catchpoint Systems issue. If the issue is Catchpoint related, the node will be paused, and the Node Status page will be updated accordingly.
Please note that not every issue is Catchpoint-related. If we are still in the process of determining the source of the issue, we will not pause the node. In this way, we will not miss important upstream ISP or internet issues. In this context, we define upstream as any component that is not the node itself, the local network, or the software. Examples include routing paths outside of the primary ISP, 3rd party ISP connection, and TLD issues.
What are the criteria for pausing a node?
A node is paused only if the issue is caused by the node configuration or if it is hardware-related. Upstream ISP/internet issues and misconfigured tests are considered valid non-Catchpoint issues and do not result in us pausing nodes. For example, if a specific ISP is facing problems, we will NOT pause the node. In a case such as this, the failure in the application delivery chain is something that you may want the node to track as part of your monitoring strategy.
On the other hand, if a test fails consistently and the cause is due to an issue with the node hardware, routing, or configuration, the node will be temporarily paused. If individual customer test(s) are impacting node performance (and other customers), we will suspend that customer’s tests till the issue is resolved. This may happen if, for example, a customer decides to load-test a specific node without first notifying Catchpoint, and we need to ensure other customers are not impacted.
Please go through the best practices listed here to configure tests correctly or contact us for assistance.
How long does a node typically stay paused?
Whenever a node is paused, Catchpoint's support team works quickly to troubleshoot and determine the cause of the problem. The amount of time it takes to restore the node depends on the type and severity of the issue. If the node hardware needs to be replaced or upgraded, then the node may need to remain paused for a week or more.
If a node is paused, the Node Status page is updated with detailed information regarding the issue and why it was paused. The status page is updated regularly to provide customers with the latest information on the node and steps that the customer can take while it is being resolved.
You can contact our support team (support@catchpoint.com) for regular updates on a specific node or check the Node Status page for more details on the issue.
How can I confirm this is not a Catchpoint issue?
The first step would be to reach out to our support team. The team will run tests and validate if the issue is Catchpoint-specific. If the issue is determined to be node-related (configuration or hardware) then it is paused, and the support team will immediately start working on a resolution.
When a support ticket is related to a node issue, the standard escalation process will be followed. The customer can change the ticket priority to HIGH if needed or reach out to our support team to do so.
You can contact our support team for regular updates on a specific node or check the Node Status page for more details on the issue.
We are exploring ways to improve our escalation process to address node queries/issues faster. We will be updating this FAQ with more details when the new process is implemented.
How do determine which nodes to use?
Catchpoint provides a variety of node types. Different node types provide different perspectives on your system's performance, and each has strengths that are applicable to specific situations. To better understand which node types are right for your testing needs, please refer to the chart below or reach out to your Catchpoint representative for more information.
| Node Type | Properties |
|---|---|
| Backbone Nodes | Use backbone nodes to monitor your digital service from outside the infrastructure it resides in. Backbone nodes are deployed on high-speed lines inside Tier-1 and Tier-2 ISPs (and in some instances Tier-3). Backbone nodes provide you with data that accurately represents the end-user experience, excluding the variations brought in by the end user’s network. |
| Last Mile Nodes | Use last mile nodes to monitor performance from a local ISP or mobile provider. If you’re running a test with a last mile node, you’re likely trying to troubleshoot issues on a more local scale. |
| Enterprise Nodes | Use enterprise nodes to determine both internal and external issues. Enterprise nodes are installed inside a client’s network. They can be deployed physically and virtually, on Linux (RedHat or CentOS). |
| Wireless Nodes | Use wireless nodes to see how performance varies across different mobile networks in different locations. Wireless nodes utilize 3G/4G networks and cell towers to tell you how your mobile users are experiencing your application and services on a variety of wireless providers. |
| Cloud Nodes | Use cloud nodes to measure the speed and availability of your digital services and applications from the vantage point of the cloud itself. Cloud nodes allow you to preempt performance challenges from global cloud providers. Often, Catchpoint cloud agents will be on the same cloud network they are testing. |
An important distinction is that cloud nodes are not in the direct line of service delivery to end users. For example, consider a web service hosted by a cloud provider. End users will access the service through an ISP and depend on DNS, CDNs, and a variety of other supporting Internet services and capabilities.
Node Related Resources
Looking for more information about node usage? Search no further! Check out these great resources:
Catchpoint Global Node Network Access the world's largest, most reliable monitoring network. Learn about the different node types we offer.
Catchpoint Backbone and Broadband Nodes Learn more about collecting data from backbone and broadband locations.
Catchpoint Cloud Nodes Learn about monitoring from cloud nodes.
Catchpoint Enterprise Nodes Learn about monitoring from enterprise nodes.
Catchpoint Last Mile Nodes Learn about monitoring from last mile nodes.
Catchpoint Wireless Nodes Learn about monitoring from wireless nodes.
Digital Experience Monitoring 101 – Know Your Node Learn about the different node types are within the context of the different types of data they provide.
Monitoring from Backbone Nodes vs. Cloud Nodes A quick reference guide to help you use backbone nodes and cloud nodes (two of the most commonly used node types) more effectively.
Catchpoint Tip of the Day - Know Your Node Discover the exceptionally wide selection of telemetry points (nodes) that Catchpoint provides to ensure complete visibility for your monitoring needs.
Catchpoint Tip of the Day - Backbone vs. Cloud Understand when and why to use two of Catchpoint's powerful telemetry points, Backbone Nodes and Cloud Nodes.