Network · data from 2026-11-12
AS267818 OPTVE
Registry name: AS267818 - OPTVE TELECOMUNICACIONES SpA, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267818, 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.
| 190.97.172.0/24 | Valid | Nonecovered by 190.97.172.0/22 | 12 2%low visibility |
| 190.97.173.0/24 | Valid | Nonecovered by 190.97.172.0/22 | 12 2%low visibility |
| 190.97.174.0/24 | Valid | Nonecovered by 190.97.172.0/22 | 12 2%low visibility |
| 190.97.175.0/24 | Valid | Nonecovered by 190.97.172.0/22 | 12 2%low visibility |
| 45.173.120.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.173.121.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.173.122.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.173.123.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.173.120.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 190.97.172.0/22 | Valid | RIR databaseLACNIC | 672 100% |
AS-SET
AS267818'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 10 are in fix.csv.
- Route object: none4
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.97.172.0/24 | No route object for it. A route object for 190.97.172.0/22 with origin AS267818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267818 in the RIR database for the space. |
| Route object: none | 190.97.173.0/24 | No route object for it. A route object for 190.97.172.0/22 with origin AS267818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267818 in the RIR database for the space. |
| Route object: none | 190.97.174.0/24 | No route object for it. A route object for 190.97.172.0/22 with origin AS267818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267818 in the RIR database for the space. |
| Route object: none | 190.97.175.0/24 | No route object for it. A route object for 190.97.172.0/22 with origin AS267818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267818 in the RIR database for the space. |
| Route object: RIR | 45.173.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267818 whose prefix no peer sees AS267818 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.173.120.0/23 | RADB | Valid |
| 45.173.122.0/23 | 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.