Announced routes
Every prefix a peer of the route collectors sees with origin AS200636, 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.
| 82.24.111.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 217.217.24.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 217.217.25.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 217.217.30.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.24.85.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.24.113.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS200636: AS-PARAVIRT. 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 (AS200636 isn't in the set, or no route object for AS200636 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.
| Name | Database | ASNs | Sets | AS200636 in it | Not covered |
|---|---|---|---|---|---|
| AS-PARAVIRT | RIPE1 member set in no database: AS60223:AS-NETIFACE | 7 | 4 | Yes | 0 |
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 3 are in fix.csv.
- AS-SET: missing member1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS-PARAVIRT | AS-PARAVIRT (RIPE) lists AS60223:AS-NETIFACE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS200636 whose prefix no peer sees AS200636 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a12:bec0:1::/48 | RIPE | Valid |
| 2a13:9500:e1::/48 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.