Network · data from 2026-11-12

AS201117 ZeroPlex

Registry name: ZeroPlex ZeroPlex B.V., NL · PeeringDB

7IPv4 routes 100.0% RPKI valid · 28.6% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 5 with no route object for this origin

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

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

Announced routes

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


185.245.156.0/23	Valid	Nonecovered by 185.245.156.0/22	673 100%	66
185.245.156.0/24	Valid	Nonecovered by 185.245.156.0/22	673 100%	66
185.245.158.0/23	Valid	Nonecovered by 185.245.156.0/22	673 100%	66
185.245.158.0/24	Valid	Nonecovered by 185.245.156.0/22	673 100%	66
185.245.159.0/24	Valid	Nonecovered by 185.245.156.0/22	673 100%	66
185.245.156.0/22	Valid	RIR databaseRIPE	673 100%	66
185.245.157.0/24	Valid	RIR databaseRIPE	673 100%	66

AS-SET

AS201117'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 5 are in fix.csv.

Route object: none5

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.245.156.0/23	No route object for it. A route object for 185.245.156.0/22 with origin AS201117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201117 in the RIR database for the space.	673 of 673
Route object: none	185.245.156.0/24	No route object for it. A route object for 185.245.156.0/22 with origin AS201117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201117 in the RIR database for the space.	673 of 673
Route object: none	185.245.158.0/23	No route object for it. A route object for 185.245.156.0/22 with origin AS201117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201117 in the RIR database for the space.	673 of 673
Route object: none	185.245.158.0/24	No route object for it. A route object for 185.245.156.0/22 with origin AS201117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201117 in the RIR database for the space.	673 of 673
Route object: none	185.245.159.0/24	No route object for it. A route object for 185.245.156.0/22 with origin AS201117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201117 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.245.156.0/23

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

673 of 673

Route object: none

185.245.156.0/24

673 of 673

Route object: none

185.245.158.0/23

673 of 673

Route object: none

185.245.158.0/24

673 of 673

Route object: none

185.245.159.0/24

673 of 673

Route objects not announced

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