Network · data from 2026-11-12

AS215136 Ryzehosting Finn Hess trading as Ryzehosting

Registry name: Ryzehosting Finn Hess trading as Ryzehosting, AT · not in PeeringDB

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

4IPv6 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 AS215136, seen from no peer

Announced routes

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


5.175.140.0/24	Valid	RIR databaseRIPE	671 100%	66
5.175.222.0/24	Valid	RIR databaseRIPE	671 100%	66
5.83.133.0/24	Valid	RIR databaseRIPE	670 100%	66
5.83.134.0/24	Valid	RIR databaseRIPE	670 100%	66
5.83.136.0/24	Valid	RIR databaseRIPE	669 99%	66
2a06:1283:8d00::/40	Valid	RIR databaseRIPE	633 100%	69
2a14:1ec1:1101::/48	Valid	RIR databaseRIPE	633 100%	69
2a14:1ec1:1200::/40	Valid	RIR databaseRIPE	633 100%	69
2a14:1ec1:1102::/48	Valid	RIR databaseRIPE	632 99%	67

AS-SET

AS215136 isn't in PeeringDB, where networks name their 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 AS215136 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.