Announced routes
Every prefix a peer of the route collectors sees with origin AS16700, 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.
| 72.162.168.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 72.162.180.0/23 | No ROA | Other IRR onlyBBOI, RADB | 671 100% |
| 204.2.0.0/20 | Valid | Other IRR onlyRADB | 671 100% |
| 64.39.128.0/19 | Valid | RIR databaseARIN, BBOI, RADB | 671 100% |
| 66.220.176.0/20 | Valid | RIR databaseARIN, BBOI, RADB | 671 100% |
| 66.252.200.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 104.244.140.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 173.214.144.0/20 | Valid | RIR databaseARIN, BBOI, RADB | 671 100% |
| 192.173.136.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.192.140.0/22 | Valid | RIR databaseARIN, BBOI, RADB | 671 100% |
| 216.157.144.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 216.212.224.0/19 | Valid | RIR databaseARIN, BBOI, RADB | 671 100% |
| 2606:ba00::/32 | Valid | RIR databaseARIN, BBOI, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS16700: AS-16700. 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 (AS16700 isn't in the set, or no route object for AS16700 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 | AS16700 in it | Not covered |
|---|---|---|---|---|---|
| AS-16700 | RADB | 5 | 1 | 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 10 are in fix.csv.
- ROA: none2
- Route object: RIR3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 72.162.168.0/22 | No ROA covers it. Add a ROA for AS16700, maxLength 22. |
| Route object: RIR | 72.162.168.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 72.162.180.0/23 | No ROA covers it. Add a ROA for AS16700, maxLength 23. |
| Route object: RIR | 72.162.180.0/23 | Route object only in BBOI, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.2.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16700 whose prefix no peer sees AS16700 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.24.156.0/24 | BBOI | Invalid: origin |
| 199.254.96.0/21 | ARIN, RADB | Valid |
| 209.37.15.0/24 | BBOI | No ROA |
| 2602:ff6a::/36 | RADB | No ROA |
| 2606:9c0::/32 | RADB | No ROA |
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.