Network Path Testing¶

Network Path Testing is used to actively probe the network path of a target address from public or self-built testing nodes, continuously observing end-to-end connectivity, network quality, and hop-by-hop path changes to help locate the locations where latency, packet loss, and routing anomalies occur.

Network Path Testing is an independent testing type and does not modify or migrate existing TCP, ICMP, or API Testing tasks.

Supported Scope¶

Creating a Network Path Testing Task¶

Go to Synthetic Tests > Testing Tasks, click Create > Network Path Testing.

Step 1: Configure Detection Target¶

Configure the following information:

Step 2: Configure Availability Judgment¶

Set the conditions for task success or failure. The system calculates task availability based on probe results and displays the judgment result in the run records.

Step 3: Select Testing Nodes¶

Select the public testing nodes or self-built testing nodes from which to initiate the probe. Different nodes generate separate run records and path results.

Step 4: Set Execution Frequency¶

Set the scheduled execution frequency of the task. After saving and enabling the task, the system will continuously execute network path probing according to the configured frequency.

Pre-Save Test¶

After configuring the target and protocol, you can perform a test before saving the task.

The test results include:

• Whether the target is reachable;
• End-to-end latency;
• Packet loss situation;
• The current detected hop-by-hop network path;
• Standard error messages in case of failure.

The pre-save test is only used to verify the current configuration and does not generate formal scheduled run records.

Managing Tasks¶

In the Network Path Testing task list, you can:

• Search and filter tasks;
• Enable or disable tasks;
• Edit, clone, or delete tasks;
• View operation audits;
• Initiate instant testing;
• View run records.

Instant Testing¶

Instant Testing immediately executes one network path probe from the selected nodes without waiting for the next scheduled task. The results of instant testing are included in the task run records.

Run Records¶

Run records display the execution time, testing node, execution status, availability judgment result, end-to-end metrics, and path summary for each execution.

Click a run record to enter the network path details page.

End-to-End Metrics¶

The details page displays the overall network metrics between the probing node and the target address, including reachability, end-to-end latency, packet loss rate, etc.

Specific metrics differ based on the TCP, UDP, and ICMP protocols.

Hop-by-Hop Path¶

The hop-by-hop path displays network nodes in the order that data packets traverse. Each hop can show the hop number, IP address, location, network affiliation, response latency, and packet loss situation.

Special Path Statuses¶

Partial Path¶

When the probe has obtained part of the network path but has not fully reached the target address, the page will display the obtained hops and mark the path as a partial path.

Anonymous Nodes¶

Some network devices do not return probe responses. Such nodes are displayed as anonymous nodes but do not affect the display of subsequent detected hops.

Path Changes¶

When the current probe path differs from historical paths, the page marks the changed hops to help determine route switching and its impact on latency or packet loss.

Error Messages¶

When a probe fails, the page displays standard error messages. The error message should include the error type, the stage at which it occurred, and suggested handling methods.

Common causes include unresolvable target address, network unreachable, connection timeout, port unreachable, abnormal testing node, etc.