bgpreport

Network · data from 2026-11-12

AS27925 entel PCS

Registry name: AS27925 - Entel PCS Telecomunicaciones S.A., CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27925, 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.
200.111.200.0/22 Valid Nonecovered by 200.111.200.0/21 670 100% 67
200.111.204.0/22 Valid Nonecovered by 200.111.200.0/21 670 100% 67
186.9.32.0/19 Valid Other IRR onlyRADB 673 100% 67
186.9.128.0/22 Valid Other IRR onlyRADB 673 100% 67
186.9.0.0/19 Valid Other IRR onlyRADB 672 100% 67
186.9.128.0/17 Valid Other IRR onlyRADB 672 100% 67
186.9.132.0/22 Valid Other IRR onlyRADB 672 100% 67
186.11.128.0/17 Valid Other IRR onlyRADB 672 100% 67
186.37.0.0/17 Valid Other IRR onlyRADB 672 100% 67
186.37.128.0/17 Valid Other IRR onlyRADB 672 100% 67
186.9.0.0/17 Valid Other IRR onlyRADB 671 100% 67
186.11.134.0/23 Valid Other IRR onlyRADB 671 100% 67
190.91.128.0/17 Valid Other IRR onlyRADB 671 100% 67
200.63.56.0/21 Valid Other IRR onlyRADB 670 100% 67
200.11.94.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
200.72.211.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
200.111.86.0/23 Valid RIR databaseLACNIC, RADB 670 100% 67
200.111.208.0/22 Valid RIR databaseLACNIC 670 100% 67

AS-SET

AS27925'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 16 are in fix.csv.

  • Route object: none2
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none200.111.200.0/22No route object for it. A route object for 200.111.200.0/21 with origin AS27925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27925 in the RIR database for the space.670 of 673
Route object: none200.111.204.0/22No route object for it. A route object for 200.111.200.0/21 with origin AS27925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27925 in the RIR database for the space.670 of 673
Route object: RIR186.9.32.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR186.9.128.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR186.9.0.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.9.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.9.132.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.11.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.37.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.37.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.9.0.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.11.134.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.91.128.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.63.56.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS27925 whose prefix no peer sees AS27925 announce. Many are kept on purpose (backup routes, space announced only in some places).

190.91.0.0/17RADBValid
200.111.200.0/21LACNICValid

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.