01 Site-to-site performance views
Compare branch, data-center and cloud paths by availability, round-trip latency, loss and jitter. Filter the view by site, region, provider or business service to locate common patterns and the specific connections that deserve investigation.
02 Protocol and service checks
Use bounded ICMP, TCP, DNS, TLS, HTTP and API tests for the relevant dependency. Compare network reachability with the expected service result so operators can identify the layer at which usable connectivity changes.
03 Current and historical paths
Review traceroute or active-path observations, fingerprints and changes over time. Place path divergence beside the selected performance interval to understand whether a route change preceded the service symptom.
04 Independent source vantages
Compare eligible Sensor or Agent observations with their own source, direction and timing. A successful alternate vantage can help distinguish destination failure from a local path problem, while contradictory results remain available for review.
05 Hop and destination evidence
Inspect available hop and destination latency, loss and jitter, with quality and unobserved-hop status. Hidden or rate-limited intermediate devices remain visible as incomplete evidence rather than automatically becoming failed network links.
06 Circuit, routing and overlay context
Connect path changes to interfaces, BGP/OSPF/BFD evidence, VRFs, MPLS or SD-WAN paths and provider circuit records. This lets the team identify the operating domain responsible for the affected connection.
07 Traffic and congestion correlation
Place Flow, utilization, errors, discards and QoS pressure beside the latency or jitter change. Distinguish a path-quality incident from traffic growth, a class-specific congestion problem or an unrelated application symptom.
08 Service targets and historical comparison
Compare paths with configured objectives, relevant baselines, prior intervals or similar sites. Keep service hours and measurement rules attached when using path results in a provider or branch SLA review.
09 Focused verification and recovery
Launch the permitted path or service test from the current investigation and retain its bounds, results and provenance. Repeat the relevant check after the approved action so the team can show the connection meets its service objective again.