Places of valley where the first AS after the climb is, for CAIDA, a peer or a customer of the AS before it. A route may have been passed on up when it should not have been, or an ASPA or a relationship may be missing: the operators are the ones who know.
Valleys through a peer or a customer: the place of the valley, the ASes inside it, and the feeders and origins that see it
Valley between
ASes in the valley
CAIDA says of the first
Routes
Feeders
Origins
Example
ASPAs that seem to miss a provider
Places of valley where the first AS after the climb is, for CAIDA, a provider of the AS before it: the ASPA of that AS does not list it, so valid routes through it look like valleys. The owners are the ones to tell.
ASPAs that do not list an AS that CAIDA gives as a provider of the customer, with the feeders that see routes through it
ASPA of
seems to miss
Places
Routes
Feeders
Over time, and collector by collector
Places of valley over time
Collectors compared
RIS and RouteViews on the same places
Validators compared
Loading
ASPAs on which the validators differ: the providers that each of them has, and a possible reason
The validator as a router sees it
Loading
The caches side by side
The caches followed: session, RTR version, VRPs, ASPAs, last sync, syncs in 24 hours and anomalies in 7 days
Cache
Session
RTR
VRPs
ASPAs
Last sync
Syncs, 24 h
Anomalies, 7 days
Records held and changed, hour by hour
What each cache did in the period
Each cache in the period: the VRPs and the ASPAs it held, and what it did
Cache
VRPs held
ASPAs held
What it did
Anomalies in the stream of syncs
Anomalies found by the detector: when, severity, what was off and the values
When
Cache
Severity
What was off
Values
Session events of the cache of the site
Events of the RTR session: when, the event and its detail