Network · data from 2026-11-12

AS266852 SOCIEDAD PIRQUE NET

Registry name: AS266852 - SOCIEDAD PIRQUE NET LIMITADA, CL · PeeringDB

2IPv4 routes 100.0% RPKI valid · 50.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS266852, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266852, 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.123.0/24	Valid	Nonecovered by 45.239.120.0/22	668 99%	67
45.239.120.0/22	Valid	Other IRR onlyRADB	669 99%	67

AS-SET

AS266852'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 2 are in fix.csv.

Route object: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: none	45.239.123.0/24	No route object for it. A route object for 45.239.120.0/22 with origin AS266852 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266852 in the RIR database for the space.	668 of 673
Route object: RIR	45.239.120.0/22	Route object only in RADB. Add it in the RIR database for the space.	669 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

45.239.123.0/24

No route object for it. A route object for 45.239.120.0/22 with origin AS266852 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266852 in the RIR database for the space.

668 of 673

Route object: RIR

45.239.120.0/22

Route object only in RADB. Add it in the RIR database for the space.

669 of 673

Route objects not announced

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