TCP Based Netpath Analysis

TCP Based Netpath Analysis

Network Path Analysis:

Ensuring uninterrupted connectivity is a paramount concern for any business. However, maintaining continuous and unbroken communication between a source and a destination in a network has historically required labor-intensive processes. It is crucial to be vigilant about potential obstacles in your network path, identify them, and promptly address them to uphold a robust and uninterrupted network.

Why monitor your Network Path?

Ensuring the health of a network stands as the utmost priority in both LAN and WAN setups. While data transmission is underway, pinpointing and troubleshooting anomalies like packet loss or transit delays occurring at different hops in the network path can be challenging. Many organizations rely on cloud services like Office 365 for their day-to-day operations, and issues with these services are easily detectable and fixable within the local area network (LAN). However, when the problem extends beyond the local network, it becomes crucial to identify the specific hop where the issue lies and notify the service provider for swift resolution.

In such scenarios, monitoring the network path proves invaluable, allowing for real-time tracking of critical parameters and prompt issue resolution. A network path analysis further provides insights into information such as latency and packet loss at any point in the network, ensuring an enhanced quality of service for end users.

Cloudmon's Network path Analysis:

In addition to its advanced capabilities in availability and performance monitoring, Cloudmon provides a comprehensive in-house network path analysis for visualizing and consistently monitoring the performance of your network path. Cloudmon allows you to monitor hop-by-hop performance across various paths connecting a source to a destination and visualize network routes from a source to its destination.

Prominent features of the Cloudmon's Network Path include: Visualizing traffic patterns and analyzing your network infrastructure and obtaining comprehensive performance insights for your network paths.

Visualizing traffic patterns and analyzing your network infrastructure:

With Cloudmon's Network Path, gain a comprehensive understanding of the paths taken by a packet from its source to its destination. Cloudmon allows you to gather essential data pertaining to the communication between a source and a destination.

Visualize a topology diagram of the path, showcasing the time taken for a data packet to traverse from source to destination and the overall duration. Hovering over the network paths provides insights into response time and latency at each hop.

Attain comprehensive performance insights for your network paths:
  1. Assess the performance of each node and link in the path using accumulated data from  Cloudmon's Network Path.
  2. Predict potential impacts on a node or link by analyzing traffic patterns through Cloudmon.
  3. Access detailed information on packet loss data and overall latency during individual hops, enabling a thorough assessment of the performance at each step of the path.
Reachable IP:



"No Reply" in a traceroute means that a particular node along
the network path did not respond to the traceroute packets.

 As there is no response from the particular node,
we are not displaying the IP address of the hop,
and we display the number of packets sent and packet loss value 

On hovering the particular hop , it will provide the following details,
The IP address of the Hop , Hop count and the latency of the packet that reached the hop. It also provides the addition stats such as
sent - The No.of packet sent
best - Minimum latency which is mentioned as "best"
worst - Maximum latency which is mentioned as "worst" and
avg - Average latency as "avg",
stDev - Standard deviation of latency measures the degree of variability in latency values.
Packet Loss - Data packets transmitted from one point to
 another do not reach their intended destination

Multipath in Networkpath:

Multipath occurs when there are alternative routes in a network. This can be intentional, designed for load balancing or redundancy, or it can be a natural consequence of the network's structure. Traceroute may reveal multipath scenarios when it discovers different routes during its probe, demonstrating the network's capability to forward packets through various paths.




On hovering the particular hop , it will provide the following details,
The IP address of the Hop, Hop count and the latency of the packet that reached the hop. It also provides the addition stats such as
sent - The No.of packet sent
best - Minimum latency which is mentioned as "best"
worst - Maximum latency which is mentioned as "worst" and
avg - Average latency as "avg",
stDev - Standard deviation of latency measures the degree of variability in latency values.
Packet Loss - Data packets transmitted from one point to another do not reach their intended destination




Unreachable IP:

Near End Issue:

Problems closer to the source can involve issues with the local network, the device initiating the traceroute, or the initial hops in the network. It may include firewall rules, routing misconfigurations, or connectivity problems near the source.



Far End Issue:

This could arise due to problems with the destination network or the devices near the destination. Issues might include misconfigured routers, network congestion, or hardware problems at the far end.







The broken red line indicates that the Destination IP is unreachable.