Network · data from 2026-11-12
AS271916 271916
Registry name: AS271916 - TELECABLE BANILEJO S.R.L, DO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271916, 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.
| 154.205.24.0/22 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 45.194.48.0/22 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 38.46.28.0/22 | Valid | RIR databaseARIN | 672 100% |
| 45.182.190.0/23 | Valid | RIR databaseLACNIC | 672 100% |
| 45.183.40.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 201.131.112.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 45.207.16.0/22 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 2803:4a10::/32 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
AS271916'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 3 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.205.24.0/22 | ROAs covering it name AS17561, not AS271916. If AS271916 should announce it, add a ROA for AS271916. |
| ROA: none | 45.194.48.0/22 | No ROA covers it. Add a ROA for AS271916, maxLength 22. |
| Route object: RIR | 45.194.48.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 AS271916 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.