Network · data from 2026-11-12

AS207728 Virterion EUROHOSTER Ltd.

Registry name: Virterion EUROHOSTER Ltd., BG · not in PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS207728, seen from no peer

Announced routes

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


2a12:9cc0::/48	Valid	Nonecovered by 2a12:9cc0::/29	632 99%	67
31.10.5.0/24	Valid	RIR databaseRIPE	673 100%	66
31.210.170.0/23	Valid	RIR databaseRIPE	673 100%	66
31.210.172.0/24	Valid	RIR databaseRIPE	673 100%	66
31.210.173.0/24	Valid	RIR databaseRIPE	673 100%	66
62.171.228.0/24	Valid	RIR databaseRIPE	673 100%	66
62.171.229.0/24	Valid	RIR databaseRIPE	673 100%	66
62.171.230.0/24	Valid	RIR databaseRIPE	673 100%	66
62.204.42.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.112.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.113.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.114.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.180.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.181.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.182.0/24	Valid	RIR databaseRIPE	673 100%	66
85.136.183.0/24	Valid	RIR databaseRIPE	673 100%	66
87.236.177.0/24	Valid	RIR databaseRIPE	673 100%	66
93.88.74.0/24	Valid	RIR databaseRIPE	673 100%	66
93.88.75.0/24	Valid	RIR databaseRIPE	673 100%	66
103.65.231.0/24	Valid	RIR databaseRIPE	673 100%	66
104.192.42.0/24	Valid	RIR databaseRIPE	673 100%	66
138.226.220.0/24	Valid	RIR databaseRIPE	673 100%	66
138.226.222.0/24	Valid	RIR databaseRIPE	673 100%	66
138.226.223.0/24	Valid	RIR databaseRIPE	673 100%	66
148.227.170.0/24	Valid	RIR databaseRIPE	673 100%	66
185.162.8.0/24	Valid	RIR databaseRIPE	673 100%	66
185.162.9.0/24	Valid	RIR databaseRIPE	673 100%	66
185.162.11.0/24	Valid	RIR databaseRIPE	673 100%	66
185.204.52.0/24	Valid	RIR databaseRIPE	673 100%	66
185.204.55.0/24	Valid	RIR databaseRIPE	673 100%	66
194.146.127.0/24	Valid	RIR databaseRIPE	673 100%	66
46.28.234.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

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

Route object: none1
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a12:9cc0::/48	No route object for it. A route object for 2a12:9cc0::/29 with origin AS207728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207728 in the RIR database for the space.	632 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a12:9cc0::/48

No route object for it. A route object for 2a12:9cc0::/29 with origin AS207728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207728 in the RIR database for the space.

632 of 636

Route objects not announced

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


103.65.230.0/24	RIPE	Invalid: origin
138.226.221.0/24	RIPE	Invalid: origin
185.204.54.0/24	RIPE	Invalid: origin
2a12:9cc0::/29	RIPE	No ROA

103.65.230.0/24

RIPE

Invalid: origin

138.226.221.0/24

RIPE

Invalid: origin

185.204.54.0/24

RIPE

Invalid: origin

2a12:9cc0::/29

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.