Private Backbone Latency
Overview
Private Backbone Latency visualizes real-time average latency across Zenlayer’s premium global private backbone. With full-mesh connectivity between global PoPs, it helps users evaluate core network performance and supports planning for Private Connect (L2) and Cloud Router (L3) deployments. It usually has the following common use cases:
Common Use Cases
Backbone performance benchmarking
Measure and compare latency between any two PoPs across Zenlayer’s private network
L2/L3 solution planning
Select optimal PoP pairs for Private Connect (L2) or Cloud Router (L3) deployments
Global route optimization
Identify lower-latency paths for cross-region data transmission
SLA validation
Verify latency SLAs across private backbone paths
Procedures
Parameter Explanation
PoP Node
A Zenlayer Point of Presence. Each row/column in the matrix represents a PoP city.
Average Latency (ms)
The average round-trip latency between two PoPs over the past 24 hours. Lower values indicate better backbone performance.
Region Tag
PoPs are grouped and color-coded by region (e.g., Asia Pacific, Europe), helping users quickly identify regional patterns.
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 within the Zenlayer private backbone, measured over the past 24 hours.
Q2: Why is latency asymmetric between two PoPs? A2: Latency may differ slightly in each direction due to routing paths, local congestion, or asymmetric traffic engineering.
Q3: Can I export the latency matrix? A3: Export functionality is not currently supported. For detailed reports, please contact Zenlayer support or your account manager.
Q4: Is this based on real-time data? A4: The displayed latency reflects aggregated data over the past 24 hours and is updated regularly to reflect current network conditions.
Last updated