Network · data from 2026-11-12
AS267831 INVERSIONES EN TELECOMUNICACIONES DIGITALES
Registry name: AS267831 - INVERSIONES EN TELECOMUNICACIONES DIGITALES S.A.C, PE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267831, 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.
| 45.173.202.0/23 | Valid | Nonecovered by 45.173.200.0/22 | 673 100% |
| 45.173.200.0/24 | Valid | Nonecovered by 45.173.200.0/23 | 0 0%low visibility |
| 45.173.200.0/23 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 45.173.202.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 45.173.203.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 45.173.200.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 2803:8460::/32 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
AS267831'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 11 are in fix.csv.
- Route object: none2
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.173.202.0/23 | No route object for it. A route object for 45.173.200.0/22 with origin AS267831 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267831 in the RIR database for the space. |
| Route object: none | 45.173.200.0/24 | No route object for it. A route object for 45.173.200.0/23 with origin AS267831 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267831 in the RIR database for the space. |
| Route object: RIR | 45.173.200.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267831 whose prefix no peer sees AS267831 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.173.201.0/24 | RADB | Valid |
| 2803:8460::/35 | LACNIC | Valid |
| 2803:8460::/36 | RADB | Valid |
| 2803:8460:2000::/36 | LACNIC | Valid |
| 2803:8460:3000::/36 | LACNIC | Valid |
| 2803:8460:4000::/36 | LACNIC | 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.