bgpreport

Network · data from 2026-11-12

AS271997 AS271997 - BIOCABLE SUR E I R L

Registry name: AS271997 - BIOCABLE SUR E I R L, CL · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS271997, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271997, 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.

181.232.148.0/24 Valid Nonecovered by 181.232.148.0/22 671 100% 67
181.232.149.0/24 Valid Nonecovered by 181.232.148.0/22 671 100% 67
181.232.150.0/24 Valid Nonecovered by 181.232.148.0/22 671 100% 67
181.232.151.0/24 Valid Other IRR onlyRADB 671 100% 67
168.196.2.0/24 Valid RIR databaseLACNIC 671 100% 67
181.232.148.0/22 Valid RIR databaseLACNIC 671 100% 67

AS-SET

AS271997 isn't in PeeringDB, where networks name their 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.

  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none181.232.148.0/24No route object for it. A route object for 181.232.148.0/22 with origin AS271997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271997 in the RIR database for the space.671 of 673
Route object: none181.232.149.0/24No route object for it. A route object for 181.232.148.0/22 with origin AS271997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271997 in the RIR database for the space.671 of 673
Route object: none181.232.150.0/24No route object for it. A route object for 181.232.148.0/22 with origin AS271997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271997 in the RIR database for the space.671 of 673
Route object: RIR181.232.151.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS271997 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.