Network · data from 2026-11-12
AS264605 TELEVIADUCTO
Registry name: AS264605 - TELEVIADUCTO S.R.L., DO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264605, 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.254.96.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 154.88.192.0/18 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 45.6.40.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 138.255.248.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 170.245.164.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 170.254.64.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 2803:19c0::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2803:9640::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
AS-SET
AS264605'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 2 are in fix.csv.
- ROA: none1
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.254.96.0/22 | No ROA covers it. Add a ROA for AS264605, maxLength 22. |
| Route object: RIR | 38.254.96.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264605 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.