Announced routes
Every prefix a peer of the route collectors sees with origin AS36951, 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.
| 2c0f:fe28:e::/48 | No ROA | Nonecovered by 2c0f:fe28::/32 | 635 100% |
| 41.223.120.0/22 | No ROA | Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH | 672 100% |
| 41.223.122.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 2c0f:fe28:1::/48 | No ROA | RIR databaseAFRINIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS36951: AFRINIC::AS-Derivco. 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 (AS36951 isn't in the set, or no route object for AS36951 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 | AS36951 in it | Not covered |
|---|---|---|---|---|---|
| AFRINIC::AS-Derivco | AFRINIC | 0 | 1 | No | 4 |
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 11 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: RIR2
- AS-SET: own ASN1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2c0f:fe28:e::/48 | No ROA covers it. Add a ROA for AS36951, maxLength 48. |
| Route object: none | 2c0f:fe28:e::/48 | No route object for it. A route object for 2c0f:fe28::/32 with origin AS36951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36951 in the RIR database for the space. |
| ROA: none | 41.223.120.0/22 | No ROA covers it. Add a ROA for AS36951, maxLength 22. |
| Route object: RIR | 41.223.120.0/22 | Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.223.122.0/24 | No ROA covers it. Add a ROA for AS36951, maxLength 24. |
| Route object: RIR | 41.223.122.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2c0f:fe28:1::/48 | No ROA covers it. Add a ROA for AS36951, maxLength 48. |
| AS-SET: own ASN | AFRINIC::AS-Derivco | AS36951 isn't in AS-DERIVCO (AFRINIC) once expanded. Add AS36951 to it. |
Route objects not announced
Route objects with origin AS36951 whose prefix no peer sees AS36951 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.223.123.0/24 | NTTCOM, RADB | No ROA |
| 2c0f:fe28::/32 | NTTCOM, RADB | No ROA |
| 2c0f:fe28:1:1::/64 | AFRINIC | 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.