Network · data from 2026-11-12
AS269741 AS269741 - INVERSIONES RED NET 2030, C.A
Registry name: AS269741 - INVERSIONES RED NET 2030, C.A, VE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269741, 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.
| 38.150.24.0/21 | Invalid: origin | None | 26 4%low visibility |
| 38.150.26.0/24 | Invalid: origin | None | 26 4%low visibility |
| 45.181.248.0/24 | Valid | Nonecovered by 45.181.248.0/22 | 673 100% |
| 45.181.250.0/23 | Valid | Nonecovered by 45.181.248.0/22 | 673 100% |
| 38.9.184.0/24 | Valid | Nonecovered by 38.9.184.0/21 | 671 100% |
| 2803:51d0::/48 | Valid | Nonecovered by 2803:51d0::/32 | 635 100% |
| 2803:51d0::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 38.9.184.0/21 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS269741 isn't in PeeringDB, where networks name their 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 11 are in fix.csv.
- ROA: origin2
- Route object: none6
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.150.24.0/21 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS269741 should announce it, add a ROA for AS269741. |
| Route object: none | 38.150.24.0/21 | No route object for it. Add a route object with origin AS269741 in the RIR database for the space. |
| ROA: origin | 38.150.26.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS269741 should announce it, add a ROA for AS269741. |
| Route object: none | 38.150.26.0/24 | No route object for it. Add a route object with origin AS269741 in the RIR database for the space. |
| Route object: none | 45.181.248.0/24 | No route object for it. A route object for 45.181.248.0/22 with origin AS269741 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269741 in the RIR database for the space. |
| Route object: none | 45.181.250.0/23 | No route object for it. A route object for 45.181.248.0/22 with origin AS269741 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269741 in the RIR database for the space. |
| Route object: none | 38.9.184.0/24 | No route object for it. A route object for 38.9.184.0/21 with origin AS269741 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269741 in the RIR database for the space. |
| Route object: none | 2803:51d0::/48 | No route object for it. A route object for 2803:51d0::/32 with origin AS269741 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269741 in the RIR database for the space. |
| Route object: RIR | 2803:51d0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269741 whose prefix no peer sees AS269741 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.181.248.0/22 | RADB | Valid |
| 154.95.25.0/24 | RADB | 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.