Network · data from 2026-11-12

AS39756 ROHOSTWAY-AS EASYHOST SRL

Registry name: ROHOSTWAY-AS EASYHOST SRL, RO · not in PeeringDB

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

28Route objects not announced registered with origin AS39756, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39756, 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.36.30.0/24	Valid	RIR databaseRIPE	673 100%	66
89.33.207.0/24	Valid	RIR databaseRIPE	672 100%	67
89.36.24.0/21	Valid	RIR databaseRIPE	672 100%	67
89.41.60.0/23	Valid	RIR databaseRIPE	672 100%	67
89.47.247.0/24	Valid	RIR databaseRIPE	672 100%	67
91.209.102.0/24	Valid	RIR databaseRIPE	672 100%	67
176.223.224.0/20	Valid	RIR databaseRIPE	672 100%	67
176.223.240.0/21	Valid	RIR databaseRIPE	672 100%	67
193.223.101.0/24	Valid	RIR databaseRIPE	672 100%	67
194.126.253.0/24	Valid	RIR databaseRIPE	672 100%	67
176.223.192.0/19	Valid	RIR databaseRIPE	671 100%	67
46.102.248.0/24	Valid	RIR databaseRIPE	670 100%	67

AS-SET

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

Route object: not announced28

Route objects not announced

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


66.232.129.0/24	RIPE-NONAUTH	No ROA
66.232.130.0/24	RIPE-NONAUTH	No ROA
66.232.131.0/24	RIPE-NONAUTH	No ROA
66.232.133.0/24	RIPE-NONAUTH	No ROA
66.232.134.0/24	RIPE-NONAUTH	No ROA
66.232.135.0/24	RIPE-NONAUTH	No ROA
84.40.1.0/24	RIPE	Invalid: origin
84.40.2.0/24	RIPE	Invalid: origin
84.40.5.0/24	RIPE	Invalid: origin
84.40.6.0/24	RIPE	Invalid: origin
84.40.7.0/24	RIPE	Invalid: origin
84.40.8.0/24	RIPE	Invalid: origin
84.40.9.0/24	RIPE	Invalid: origin
84.40.10.0/24	RIPE	Invalid: origin
84.40.11.0/24	RIPE	Invalid: origin
84.40.13.0/24	RIPE	Invalid: origin
89.36.24.0/24	RIPE	Valid
89.36.25.0/24	RIPE	Valid
89.36.26.0/24	RIPE	Valid
89.36.27.0/24	RIPE	Valid
89.36.28.0/24	RIPE	Valid
89.36.29.0/24	RIPE	Valid
89.36.31.0/24	RIPE	Valid
89.41.60.0/24	RIPE	Valid
89.41.61.0/24	RIPE	Valid
176.223.192.0/18	RIPE	No ROA
176.223.247.0/24	RIPE	Valid
188.215.38.0/24	RIPE	No ROA

66.232.129.0/24

RIPE-NONAUTH

No ROA

66.232.130.0/24

RIPE-NONAUTH

No ROA

66.232.131.0/24

RIPE-NONAUTH

No ROA

66.232.133.0/24

RIPE-NONAUTH

No ROA

66.232.134.0/24

RIPE-NONAUTH

No ROA

66.232.135.0/24

RIPE-NONAUTH

No ROA

84.40.1.0/24

RIPE

Invalid: origin

84.40.2.0/24

RIPE

Invalid: origin

84.40.5.0/24

RIPE

Invalid: origin

84.40.6.0/24

RIPE

Invalid: origin

84.40.7.0/24

RIPE

Invalid: origin

84.40.8.0/24

RIPE

Invalid: origin

84.40.9.0/24

RIPE

Invalid: origin

84.40.10.0/24

RIPE

Invalid: origin

84.40.11.0/24

RIPE

Invalid: origin

84.40.13.0/24

RIPE

Invalid: origin

89.36.24.0/24

RIPE

Valid

89.36.25.0/24

RIPE

Valid

89.36.26.0/24

RIPE

Valid

89.36.27.0/24

RIPE

Valid

89.36.28.0/24

RIPE

Valid

89.36.29.0/24

RIPE

Valid

89.36.31.0/24

RIPE

Valid

89.41.60.0/24

RIPE

Valid

89.41.61.0/24

RIPE

Valid

176.223.192.0/18

RIPE

No ROA

176.223.247.0/24

RIPE

Valid

188.215.38.0/24

RIPE

No ROA

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.