Network · data from 2026-11-12
AS54721 NGEN Networks, LLC
Registry name: AS-NGEN - NGEN Networks, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54721, 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.
| 2602:fef4:300::/48 | Valid | Nonecovered by 2602:fef4::/36 | 636 100% |
| 2602:fef4:200::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2602:fef4::/48 | Valid | Other IRR onlyRADB, RIPE-NONAUTH | 635 100% |
| 2602:fef4:400::/48 | Valid | Other IRR onlyRADB | 630 99% |
| 2602:fef4:500::/48 | Valid | Other IRR onlyRADB | 630 99% |
| 23.163.128.0/24 | Valid | RIR databaseALTDB, ARIN, RADB, RIPE-NONAUTH | 673 100% |
| 23.163.129.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS54721: AS-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 (AS54721 isn't in the set, or no route object for AS54721 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 | AS54721 in it | Not covered |
|---|---|---|---|---|---|
| AS-ALL | RADB | 5 | 1 | No | 7 |
| AFRINIC (also) | 1 | 1 | No | 7 | |
| APNIC (also) | 1 | 1 | No | 7 | |
| ARIN (also)1 member set in no database: AS30164:AS-CUSTOMERS | 3 | 1 | No | 7 | |
| RIPE (also)1 member set in no database: AS-SDN-CLINIC-LAB | 235 | 30 | No | 7 |
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 8 are in fix.csv.
- Route object: none1
- Route object: RIR4
- AS-SET: own ASN1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:fef4:300::/48 | No route object for it. A route object for 2602:fef4::/36 with origin AS54721 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54721 in the RIR database for the space. |
| Route object: RIR | 2602:fef4:200::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:fef4::/48 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 2602:fef4:400::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:fef4:500::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-ALL | AS54721 isn't in AS-ALL (RADB) once expanded. Add AS54721 to it. |
Route objects not announced
Route objects with origin AS54721 whose prefix no peer sees AS54721 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:fef4::/36 | ALTDB, ARIN, RADB, RIPE-NONAUTH | Valid |
| 2602:fef4:100::/48 | RIPE-NONAUTH | 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.