Announced routes
Every prefix a peer of the route collectors sees with origin AS54054, 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.
| 198.133.158.0/23 | Invalid: origin | None | 0 0%low visibility |
| 44.30.122.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.219.56.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 192.110.255.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 199.168.88.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 2606:700::/32 | Valid | Other IRR onlyNTTCOM, RADB | 636 100% |
| 2620:8c:4000::/48 | Valid | Other IRR onlyALTDB, RADB | 636 100% |
| 192.48.223.0/24 | Valid | RIR databaseARIN, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS54054: AS54054:AS-DETEQUE-CUSTOMERS. 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 (AS54054 isn't in the set, or no route object for AS54054 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 | AS54054 in it | Not covered |
|---|---|---|---|---|---|
| AS54054:AS-DETEQUE-CUSTOMERS | NTTCOM | 6 | 1 | Yes | 1 |
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: origin1
- ROA: none1
- Route object: none1
- Route object: RIR6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 198.133.158.0/23 | ROAs covering it name AS2914, not AS54054. If AS54054 should announce it, add a ROA for AS54054. |
| Route object: none | 198.133.158.0/23 | No route object for it. Add a route object with origin AS54054 in the RIR database for the space. |
| ROA: none | 44.30.122.0/24 | No ROA covers it. Add a ROA for AS54054, maxLength 24. |
| Route object: RIR | 44.30.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.219.56.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.110.255.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.168.88.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:700::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2620:8c:4000::/48 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54054 whose prefix no peer sees AS54054 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.6.192.0/18 | 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.