bgpreport

Network · data from 2026-11-12

AS266840 CMP WILL TELECOMUNICACIONES

Registry name: AS266840 - CMP WILL TELECOMUNICACIONES SPA, CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266840, 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.
45.239.28.0/22 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS266840'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 9 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR45.239.28.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

45.238.28.0/22RADBNo ROA
45.239.28.0/24RADBValid
45.239.29.0/24RADBValid
45.239.30.0/24RADBValid
45.239.31.0/24RADBValid
2803:1ca0::/32RADBValid
2a00:fd41::/32RADBNo ROA
2a00:fd41::/48RADBNo ROA

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.