Network · data from 2026-11-12
AS267685 SIRIO TELECOMUNICACIONES
Registry name: AS267685 - SIRIO TELECOMUNICACIONES S.R.L, BO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267685, 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.46.145.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 45.163.18.0/24 | Valid | Nonecovered by 45.163.18.0/23 | 673 100% |
| 45.163.19.0/24 | Valid | Nonecovered by 45.163.18.0/23 | 673 100% |
| 160.20.225.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 38.75.210.0/24 | Valid | RIR databaseARIN | 672 100% |
| 2803:3ea0::/32 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
AS267685'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 4 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.46.145.0/24 | No ROA covers it. Add a ROA for AS267685, maxLength 24. |
| Route object: none | 45.163.18.0/24 | No route object for it. A route object for 45.163.18.0/23 with origin AS267685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267685 in the RIR database for the space. |
| Route object: none | 45.163.19.0/24 | No route object for it. A route object for 45.163.18.0/23 with origin AS267685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267685 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267685 whose prefix no peer sees AS267685 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.163.18.0/23 | 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.