AS151633 Archon Data Solutions

Announced routes

Every prefix a peer of the route collectors sees with origin AS151633, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

AS-SET

PeeringDB's irr_as_set for AS151633: AS151633:AS-DOWNSTREAM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS151633 isn't in the set, or no route object for AS151633 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 126 are in fix.csv.

• Route object: none2
• AS-SET: not found1
• Route object: not announced123

Route objects not announced

Route objects with origin AS151633 whose prefix no peer sees AS151633 announce. Many are kept on purpose (backup routes, space announced only in some places).