Network · data from 2026-11-12

AS52048 RixHost SIA RixHost

Registry name: RixHost SIA RixHost, LV · not in PeeringDB

17IPv4 routes 76.5% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

4No ROA 0 with no route object for this origin

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

1Route objects not announced registered with origin AS52048, seen from no peer

Announced routes

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


109.248.147.0/24	No ROA	RIR databaseRIPE	671 100%	68
109.248.148.0/24	No ROA	RIR databaseRIPE	671 100%	68
109.248.149.0/24	No ROA	RIR databaseRIPE	671 100%	68
109.248.151.0/24	No ROA	RIR databaseRIPE	671 100%	68
46.183.216.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.217.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.218.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.219.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.220.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.221.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.222.0/24	Valid	RIR databaseRIPE	671 100%	68
46.183.223.0/24	Valid	RIR databaseRIPE	671 100%	68
84.38.130.0/24	Valid	RIR databaseRIPE	671 100%	68
84.38.132.0/24	Valid	RIR databaseRIPE	671 100%	68
84.38.134.0/24	Valid	RIR databaseRIPE	671 100%	68
84.38.135.0/24	Valid	RIR databaseRIPE	671 100%	68
185.28.47.0/24	Valid	RIR databaseRIPE	671 100%	68
2a02:4840::/48	Valid	RIR databaseRIPE	635 100%	69
2a02:4840:1::/48	Valid	RIR databaseRIPE	635 100%	69
2a02:4840:2::/48	Valid	RIR databaseRIPE	635 100%	69
2a02:4840:1000::/48	Valid	RIR databaseRIPE	635 100%	69
2a09:d000::/48	Valid	RIR databaseRIPE	635 100%	69

AS-SET

AS52048 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.

ROA: none4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	109.248.147.0/24	No ROA covers it. Add a ROA for AS52048, maxLength 24.	671 of 673
ROA: none	109.248.148.0/24	No ROA covers it. Add a ROA for AS52048, maxLength 24.	671 of 673
ROA: none	109.248.149.0/24	No ROA covers it. Add a ROA for AS52048, maxLength 24.	671 of 673
ROA: none	109.248.151.0/24	No ROA covers it. Add a ROA for AS52048, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

109.248.147.0/24

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

671 of 673

ROA: none

109.248.148.0/24

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

671 of 673

ROA: none

109.248.149.0/24

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

671 of 673

ROA: none

109.248.151.0/24

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

671 of 673

Route objects not announced

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


46.183.216.0/21	RIPE	Valid

46.183.216.0/21

RIPE

Valid

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.