Network · data from 2026-11-12

AS199144 HEXCORECLOUD-AS HexCore cloud s.r.o.

Registry name: HEXCORECLOUD-AS HexCore cloud s.r.o., SK · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 77.8% with a route object

4IPv6 routes 50.0% RPKI valid · 75.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No 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 AS199144, seen from no peer

Announced routes

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


154.59.110.0/23	No ROA	None	673 100%	67
154.59.225.0/24	No ROA	None	673 100%	67
2001:978:3c0f::/48	No ROA	None	605 95%	67
2001:978:1001::/48	No ROA	Other IRR onlyRADB	635 100%	67
138.249.207.0/24	Valid	RIR databaseRIPE	673 100%	67
185.23.236.0/24	Valid	RIR databaseRIPE	673 100%	67
188.119.112.0/24	Valid	RIR databaseRIPE	673 100%	67
193.42.112.0/24	Valid	RIR databaseRIPE	673 100%	67
209.131.70.0/24	Valid	RIR databaseRIPE	673 100%	67
217.78.239.0/24	Valid	RIR databaseRIPE	673 100%	67
45.129.197.0/24	Valid	RIR databaseRIPE	672 100%	67
2a06:1301:4100::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:48a0:4301::/48	Valid	RIR databaseRIPE	605 95%	67

AS-SET

AS199144 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 8 are in fix.csv.

ROA: none4
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	154.59.110.0/23	No ROA covers it. Add a ROA for AS199144, maxLength 23.	673 of 673
Route object: none	154.59.110.0/23	No route object for it. Add a route object with origin AS199144 in the RIR database for the space.	673 of 673
ROA: none	154.59.225.0/24	No ROA covers it. Add a ROA for AS199144, maxLength 24.	673 of 673
Route object: none	154.59.225.0/24	No route object for it. Add a route object with origin AS199144 in the RIR database for the space.	673 of 673
ROA: none	2001:978:3c0f::/48	No ROA covers it. Add a ROA for AS199144, maxLength 48.	605 of 636
Route object: none	2001:978:3c0f::/48	No route object for it. Add a route object with origin AS199144 in the RIR database for the space.	605 of 636
ROA: none	2001:978:1001::/48	No ROA covers it. Add a ROA for AS199144, maxLength 48.	635 of 636
Route object: RIR	2001:978:1001::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

154.59.110.0/23

No ROA covers it. Add a ROA for AS199144, maxLength 23.

673 of 673

Route object: none

154.59.110.0/23

No route object for it. Add a route object with origin AS199144 in the RIR database for the space.

673 of 673

ROA: none

154.59.225.0/24

No ROA covers it. Add a ROA for AS199144, maxLength 24.

673 of 673

Route object: none

154.59.225.0/24

No route object for it. Add a route object with origin AS199144 in the RIR database for the space.

673 of 673

ROA: none

2001:978:3c0f::/48

No ROA covers it. Add a ROA for AS199144, maxLength 48.

605 of 636

Route object: none

2001:978:3c0f::/48

No route object for it. Add a route object with origin AS199144 in the RIR database for the space.

605 of 636

ROA: none

2001:978:1001::/48

No ROA covers it. Add a ROA for AS199144, maxLength 48.

635 of 636

Route object: RIR

2001:978:1001::/48

Route object only in RADB. Add it in the RIR database for the space.

635 of 636

Route objects not announced

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