Network · data from 2026-11-12

AS204213 netmihan Netmihan Communication Company Ltd

Registry name: netmihan Netmihan Communication Company Ltd, IR · not in PeeringDB

21IPv4 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

7Route objects not announced registered with origin AS204213, seen from no peer

Announced routes

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


89.32.248.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.32.249.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.32.251.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.39.208.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.42.208.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.42.211.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
185.94.96.0/24	Valid	RIR databaseRIPE	673 100%	66
185.94.97.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
185.94.98.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
188.212.22.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
217.144.105.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
217.144.106.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
89.32.250.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
89.42.209.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
89.42.210.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
86.106.142.0/24	Valid	RIR databaseRADB, RIPE	671 100%	66
86.107.47.0/24	Valid	RIR databaseRIPE	671 100%	66
89.45.89.0/24	Valid	RIR databaseRADB, RIPE	671 100%	66
185.94.99.0/24	Valid	RIR databaseRADB, RIPE	671 100%	66
217.144.107.0/24	Valid	RIR databaseRADB, RIPE	670 100%	66
217.144.104.0/24	Valid	RIR databaseRADB, RIPE	668 99%	67

AS-SET

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

Route object: not announced7

Route objects not announced

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


86.107.184.0/24	RIPE	Valid
89.33.87.0/24	RIPE	Valid
89.35.172.0/24	RIPE	Valid
89.40.65.0/24	RIPE	Valid
185.94.96.0/22	RIPE	No ROA
185.94.96.0/23	RIPE	No ROA
185.94.96.157/32	RIPE	Invalid: maxLength

86.107.184.0/24

RIPE

Valid

89.33.87.0/24

RIPE

Valid

89.35.172.0/24

RIPE

Valid

89.40.65.0/24

RIPE

Valid

185.94.96.0/22

RIPE

No ROA

185.94.96.0/23

RIPE

No ROA

185.94.96.157/32

RIPE

Invalid: maxLength

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.