Network · data from 2026-11-12

AS214673 mijnhost

Registry name: mijnhost mijn.host B.V., NL · PeeringDB

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

5IPv6 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

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

Announced routes

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


62.129.138.0/24	Valid	RIR databaseRIPE	673 100%	66
62.129.142.0/24	Valid	RIR databaseRIPE	673 100%	66
178.251.232.0/24	Valid	RIR databaseRIPE	673 100%	66
217.180.14.0/24	Valid	RIR databaseRIPE	673 100%	66
62.129.140.0/24	Valid	RIR databaseRIPE	672 100%	67
62.129.143.0/24	Valid	RIR databaseRIPE	672 100%	67
149.245.246.0/24	Valid	RIR databaseRIPE	672 100%	66
149.245.247.0/24	Valid	RIR databaseRIPE	672 100%	67
92.62.118.0/24	Valid	RIR databaseRIPE	667 99%	67
193.143.69.0/24	Valid	RIR databaseRIPE	667 99%	67
2a11:4882:100::/48	Valid	RIR databaseRIPE	634 100%	67
2a11:4880::/32	Valid	RIR databaseRIPE	633 100%	67
2a11:4882::/48	Valid	RIR databaseRIPE	633 100%	67
2a11:4882:200::/48	Valid	RIR databaseRIPE	633 100%	67
2a11:4881::/32	Valid	RIR databaseRIPE	632 99%	67

AS-SET

AS214673's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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