Public Transit Latency
Overview
Public IP Transit - Network Latency displays real-time average latency between Zenlayer PoPs over the public internet. This module reflects latency performance across our global 150+ Tbps IP transit network, offering insights into public routing quality between various regions and ISPs. It helps users monitor public network health, compare performance with private backbone routes, and optimize global traffic delivery strategies. It usually has the following common use cases:
Common Use Cases
Public network benchmarking
Assess end-to-end latency over the public internet across global regions
Route comparison
Compare public IP transit latency against Zenlayer’s private backbone
ISP path evaluation
Identify high-latency or underperforming public paths between cities
Performance troubleshooting
Detect cross-border congestion or irregular routing behavior
Procedures
Parameter Explanation
PoP Node
A Zenlayer Point of Presence participating in public IP transit. Each row/column represents a PoP city.
Average Latency (ms)
The average round-trip latency between two PoPs over the public internet within the past 24 hours.
Region Tag
PoPs are grouped and color-coded by geographic region (e.g., Asia Pacific, Europe, North America).
Input or select cities one or more cities to include in the latency matrix. The chart displays average round-trip latency (ms) between selected PoPs over the past 24 hours.
Hover over any cell to see the city pair and latency value.
FAQ
Q1: What does the latency value represent? A1: It shows the average round-trip latency between two PoPs over the public IP transit network, measured over the past 24 hours.
Q2: Why is latency higher than on the private backbone? A2: Public internet routing is subject to congestion, ISP peering arrangements, and less predictable path selection compared to Zenlayer's controlled private backbone.
Q3: Can I export the latency data? A3: Export functionality is not currently available. Please contact Zenlayer support or your account manager for detailed reporting needs.
Q4: How often is the data updated? A4: Latency data is continuously measured and reflects the average over the most recent 24-hour period.
Last updated