Network · data from 2026-11-12

AS203396 MinEZ-DICTU Ministerie van Economische Zaken

Registry name: MinEZ-DICTU Ministerie van Economische Zaken, NL · not in PeeringDB

55IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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

9Route objects not announced registered with origin AS203396, seen from no peer

Announced routes

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


145.69.0.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.25.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.42.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.47.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.100.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.101.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.102.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.103.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.104.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.105.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.106.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.107.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.108.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.109.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.110.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.210.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.216.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.218.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.219.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.220.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.221.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.227.0/24	Valid	RIR databaseRIPE	673 100%	67
145.69.242.0/24	Valid	RIR databaseRIPE	673 100%	67
193.176.148.0/22	Valid	RIR databaseRIPE	672 100%	67
193.176.152.0/24	Valid	RIR databaseRIPE	672 100%	67
145.12.0.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.10.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.20.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.26.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.27.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.31.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.34.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.36.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.37.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.40.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.46.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.47.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.68.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.69.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.100.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.101.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.102.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.103.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.104.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.105.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.137.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.210.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.216.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.218.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.219.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.220.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.221.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.227.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.242.0/24	Valid	RIR databaseRIPE	671 100%	67
145.12.243.0/24	Valid	RIR databaseRIPE	671 100%	67
2a04:9a00:1022::/48	Valid	RIR databaseNTTCOM, RIPE	634 100%	67
2a04:9a00:1021::/48	Valid	RIR databaseNTTCOM, RIPE	633 100%	67

AS-SET

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

Route object: not announced9

Route objects not announced

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


145.12.0.0/16	RIPE	Valid
145.12.1.0/24	RIPE	Valid
145.69.0.0/16	RIPE	Valid
145.69.0.0/19	RIPE	Valid
145.69.1.0/24	RIPE	Valid
145.69.40.0/21	RIPE	Valid
145.69.56.0/21	RIPE	Valid
145.69.96.0/19	RIPE	Valid
145.69.128.0/17	RIPE	Valid

145.12.0.0/16

RIPE

Valid

145.12.1.0/24

RIPE

Valid

145.69.0.0/16

RIPE

Valid

145.69.0.0/19

RIPE

Valid

145.69.1.0/24

RIPE

Valid

145.69.40.0/21

RIPE

Valid

145.69.56.0/21

RIPE

Valid

145.69.96.0/19

RIPE

Valid

145.69.128.0/17

RIPE

Valid

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.