bgpreport

Network · data from 2026-11-12

AS58046 HKOM-AS The Ministry of Digital Transformation

Registry name: HKOM-AS The Ministry of Digital Transformation, SI · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS58046, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58046, 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.
84.39.208.0/20 No ROA RIR databaseRIPE 673 100% 68
163.159.0.0/17 No ROA RIR databaseRIPE 673 100% 68
163.159.0.0/18 No ROA RIR databaseRIPE 673 100% 68
163.159.63.0/24 No ROA RIR databaseRIPE 673 100% 66
163.159.64.0/18 No ROA RIR databaseRIPE 673 100% 68
185.221.56.0/22 No ROA RIR databaseRIPE 673 100% 68
2a00:d440::/29 No ROA RIR databaseRIPE 633 100% 68

AS-SET

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

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none84.39.208.0/20No ROA covers it. Add a ROA for AS58046, maxLength 20.673 of 673
ROA: none163.159.0.0/17No ROA covers it. Add a ROA for AS58046, maxLength 17.673 of 673
ROA: none163.159.0.0/18No ROA covers it. Add a ROA for AS58046, maxLength 18.673 of 673
ROA: none163.159.63.0/24No ROA covers it. Add a ROA for AS58046, maxLength 24.673 of 673
ROA: none163.159.64.0/18No ROA covers it. Add a ROA for AS58046, maxLength 18.673 of 673
ROA: none185.221.56.0/22No ROA covers it. Add a ROA for AS58046, maxLength 22.673 of 673
ROA: none2a00:d440::/29No ROA covers it. Add a ROA for AS58046, maxLength 29.633 of 636

Route objects not announced

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