ASPA Explorer

Right now

What today's routes, the validators and the RTR caches show at this moment.

Invalid announcements, as they happen

Loading

Share of invalid announcements, by hour

Origins with the most invalid announcements

The 20 origin ASes with the most invalid announcements in the days recorded (the last 14 at most)
OriginInvalidAnnouncementsSharePrefixes

The highest shares, and the prefixes

Origins with the highest share of invalid announcements

The 20 origin ASes with the highest share of invalid announcements, among those with at least 100 announcements
OriginShareInvalidAnnouncementsPrefixes

Prefixes with the most invalid announcements

The 20 prefixes with the most invalid announcements in the days recorded (the last 14 at most)
PrefixOriginInvalid

The report as JSON: /api/v1/invalid.json.

Valleys today

Loading

Valleys through a peer or a customer

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 betweenASes in the valleyCAIDA says of the firstRoutesFeedersOriginsExample

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 ofseems to missPlacesRoutesFeeders

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
        CacheSessionRTRVRPsASPAsLast syncSyncs, 24 hAnomalies, 7 days

        Records held and changed, hour by hour

        Anomalies in the stream of syncs

        Anomalies found by the detector: when, severity, what was off and the values
        WhenCacheSeverityWhat was offValues

        Session events of the cache of the site

        Events of the RTR session: when, the event and its detail
        WhenEventDetail

        Looking for what happened in the last days? Incidents, classified by type