Network · data from 2026-11-12
AS265654 ENX Fund
Registry name: AS265654 - ENX FUND INC, PA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265654, 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.
| 170.246.221.0/24 | Valid | Nonecovered by 170.246.220.0/22 | 671 100% |
| 170.246.222.0/24 | Valid | Nonecovered by 170.246.220.0/22 | 671 100% |
| 170.246.220.0/24 | Valid | Nonecovered by 170.246.220.0/22 | 670 100% |
| 170.246.220.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2803:96c0::/32 | Valid | RIR databaseLACNIC, RADB | 2 0%low visibility |
AS-SET
AS265654's PeeringDB record names no AS-SET.
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 3 are in fix.csv.
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.246.221.0/24 | No route object for it. A route object for 170.246.220.0/22 with origin AS265654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265654 in the RIR database for the space. |
| Route object: none | 170.246.222.0/24 | No route object for it. A route object for 170.246.220.0/22 with origin AS265654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265654 in the RIR database for the space. |
| Route object: none | 170.246.220.0/24 | No route object for it. A route object for 170.246.220.0/22 with origin AS265654 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265654 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS265654 is announced.
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.