Network · data from 2026-11-12

AS201702 skHosting.eu s.r.o.

Registry name: SKHOSTING-EU skHosting.eu s.r.o., SK · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

0Route objects not announced registered with origin AS201702, seen from no peer

Announced routes

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


185.66.200.0/24	Valid	Nonecovered by 185.66.200.0/23	672 100%	66
185.66.201.0/24	Valid	Nonecovered by 185.66.200.0/23	672 100%	66
2a05:980::/30	Valid	Nonecovered by 2a05:980::/29	635 100%	69
185.66.200.0/23	Valid	RIR databaseRIPE	673 100%	66
2a05:980::/29	Valid	RIR databaseRIPE	634 100%	69

AS-SET

AS201702's PeeringDB record names no 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 3 are in fix.csv.

Route object: none3

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.66.200.0/24	No route object for it. A route object for 185.66.200.0/23 with origin AS201702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201702 in the RIR database for the space.	672 of 673
Route object: none	185.66.201.0/24	No route object for it. A route object for 185.66.200.0/23 with origin AS201702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201702 in the RIR database for the space.	672 of 673
Route object: none	2a05:980::/30	No route object for it. A route object for 2a05:980::/29 with origin AS201702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201702 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.66.200.0/24

No route object for it. A route object for 185.66.200.0/23 with origin AS201702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201702 in the RIR database for the space.

672 of 673

Route object: none

185.66.201.0/24

672 of 673

Route object: none

2a05:980::/30

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

635 of 636

Route objects not announced

Every route object with origin AS201702 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.