bgpreport

Network · data from 2026-11-12

AS4594 Internet Solutions Limited

Registry name: HKISL-ASN - Internet Solutions Limited, HK · PeeringDB

12IPv4 routes 91.7% RPKI valid · 91.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS4594, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4594, 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.
103.44.60.0/24 Invalid: origin Other origin onlycovered by 103.44.60.0/23 15 2%low visibility 10
43.225.100.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
103.44.61.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.74.0.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
103.224.20.0/24 Valid RIR databaseAPNIC 670 100% 69
43.225.100.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
43.225.102.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
43.225.103.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
202.74.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
202.74.1.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
202.74.2.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
202.74.3.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 96 14% 45
2407:880::/32 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS4594'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 12 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin103.44.60.0/24ROAs covering it name AS9304, not AS4594. If AS4594 should announce it, add a ROA for AS4594.15 of 673
Route object: none103.44.60.0/24Route objects for it name AS9304. A route object for 103.44.60.0/23 with origin AS4594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4594 in the RIR database for the space.15 of 673

Route objects not announced

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

103.44.60.0/22NTTCOM, RADBNo ROA
103.44.60.0/23NTTCOM, RADBNo ROA
103.44.62.0/23NTTCOM, RADBNo ROA
103.248.77.0/24NTTCOM, RADBNo ROA
103.248.78.0/23NTTCOM, RADBNo ROA
103.248.78.0/24NTTCOM, RADBNo ROA
103.248.79.0/24NTTCOM, RADBNo ROA
171.33.242.0/23NTTCOM, RADBNo ROA
171.33.242.0/24NTTCOM, RADBNo ROA
202.74.0.0/23APNICInvalid: maxLength

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.