Announced routes
Every prefix a peer of the route collectors sees with origin AS23286, 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.
| 8.28.124.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 8.28.125.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.60.116.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 199.200.50.0/23 | No ROA | RIR databaseARIN, RADB | 672 100% |
| 208.91.158.0/23 | No ROA | RIR databaseARIN, RADB | 672 100% |
| 208.91.156.0/23 | No ROA | RIR databaseARIN, RADB | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS23286: AS-DSS-ALL. 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 (AS23286 isn't in the set, or no route object for AS23286 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 | AS23286 in it | Not covered |
|---|---|---|---|---|---|
| AS-DSS-ALL | RADB | 6 | 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 17 are in fix.csv.
- ROA: none6
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.28.124.0/24 | No ROA covers it. Add a ROA for AS23286, maxLength 24. |
| Route object: RIR | 8.28.124.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 8.28.125.0/24 | No ROA covers it. Add a ROA for AS23286, maxLength 24. |
| Route object: RIR | 8.28.125.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.60.116.0/24 | No ROA covers it. Add a ROA for AS23286, maxLength 24. |
| Route object: RIR | 199.60.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.200.50.0/23 | No ROA covers it. Add a ROA for AS23286, maxLength 23. |
| ROA: none | 208.91.158.0/23 | No ROA covers it. Add a ROA for AS23286, maxLength 23. |
| ROA: none | 208.91.156.0/23 | No ROA covers it. Add a ROA for AS23286, maxLength 23. |
Route objects not announced
Route objects with origin AS23286 whose prefix no peer sees AS23286 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.3.214.0/23 | ALTDB | No ROA |
| 199.200.48.0/22 | ALTDB | No ROA |
| 199.200.48.0/23 | ARIN, RADB | No ROA |
| 199.200.49.0/24 | RADB | No ROA |
| 208.91.156.0/22 | ALTDB | No ROA |
| 209.130.204.0/23 | ALTDB | No ROA |
| 209.249.186.0/24 | ARIN | Invalid: origin |
| 2620:100:3000::/40 | ARIN | 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.