Network · data from 2026-11-12

AS34689 hosteroid

Registry name: hosteroid Castlegem SRL, RO · PeeringDB

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

6IPv6 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 AS34689, seen from no peer

Announced routes

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


95.131.202.0/24	Valid	RIR databaseRIPE	673 100%	66
162.254.84.0/24	Valid	RIR databaseARIN	673 100%	67
162.254.86.0/24	Valid	RIR databaseARIN	673 100%	66
162.254.87.0/24	Valid	RIR databaseARIN	673 100%	67
162.255.152.0/24	Valid	RIR databaseARIN	673 100%	67
185.75.242.0/24	Valid	RIR databaseRIPE	673 100%	67
185.75.243.0/24	Valid	RIR databaseRIPE	667 99%	67
2a05:5502::/32	Valid	RIR databaseRIPE	636 100%	67
2a13:9401::/32	Valid	RIR databaseRIPE	636 100%	69
2a13:9403::/32	Valid	RIR databaseRIPE	635 100%	69
2a13:9400::/32	Valid	RIR databaseRIPE	634 100%	67
2a13:9404::/32	Valid	RIR databaseRIPE	634 100%	69
2a13:9402::/32	Valid	RIR databaseRIPE	594 93%	66

AS-SET

AS34689'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 AS34689 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.