| Time range | 2013-04-29 16:17 to 2013-05-01 11:48 UTC (1 day 20 hours) (5 days ago) |
| Total traces | 542349 |
| Traces with responding destinations | 65817 (12.136%) |
| ASes with responding destinations | 4472 (25.382% out of 17619) |
| Prefixes with responding destinations | 21967 (22.496% out of 97648) |
| Protocol version | v4 (switch to v6) |
Generated for cycle 2498 on 2013-05-04 20:07 UTC
All images can be clicked on for more detailed information.
Median RTT per country and US state
Mapping RTT by political boundaries can reveal where high latency issues are located.
-
Median RTT per country and US state
Path Dispersion
The paths taken by different traces show where the majority of a monitor's traffic travels.
-
AS Path Dispersion (by AS Hop)
AS connectivity near monitor
-
AS Path Dispersion (by IP Hop)
AS connectivity near monitor (with IP hop distances preserved)
-
IP Path Dispersion (by IP Hop)
IP connectivity near monitor
Path Length Distributions
Path length distributions show, on aggregate, how well-connected a monitor is to the rest of the Internet.
-
CCDF of IP path lengths for responding destinations
percentile 10th 25th 50th 75th 90th Max IP path length 8 10 12 15 17 35 
-
CCDF of AS path lengths for responding destinations
percentile 10th 25th 50th 75th 90th Max AS path length 2 3 3 4 5 10 
-
CCDF of IP path lengths for non-responding destinations
percentile 10th 25th 50th 75th 90th Max IP path length 5 7 10 12 15 38 
-
CCDF of AS path lengths for non-responding destinations
percentile 10th 25th 50th 75th 90th Max AS path length 2 2 3 4 4 12 
-
CCDF of destination RTTs
percentile 10th 25th 50th 75th 90th RTT (ms) 72.368 117.889 184.862 229.596 390.478 
-
RTT quartiles vs hop distance
-
RTT density versus geographical distance
-
RTT quartiles versus geographical distance
