| Time range | 2013-05-03 12:52 to 2013-05-05 11:27 UTC (1 day 23 hours) (1 day ago) |
| Total traces | 515214 |
| Traces with responding destinations | 61795 (11.994%) |
| ASes with responding destinations | 4296 (24.764% out of 17348) |
| Prefixes with responding destinations | 20860 (22.093% out of 94419) |
| Protocol version | v4 (switch to v6) |
Generated for cycle 2504 on 2013-05-06 13:18 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 13 16 17 19 21 37 
-
CCDF of AS path lengths for responding destinations
percentile 10th 25th 50th 75th 90th Max AS path length 3 4 4 5 6 14 
-
CCDF of IP path lengths for non-responding destinations
percentile 10th 25th 50th 75th 90th Max IP path length 8 10 13 16 19 36 
-
CCDF of AS path lengths for non-responding destinations
percentile 10th 25th 50th 75th 90th Max AS path length 2 3 4 4 5 14 
-
CCDF of destination RTTs
percentile 10th 25th 50th 75th 90th RTT (ms) 46.365 102.665 166.454 293.883 592.855 
-
RTT quartiles vs hop distance
-
RTT density versus geographical distance
-
RTT quartiles versus geographical distance
