bgpreport

Network · data from 2026-11-12

AS55953 XIM-HK - Room A03, 22/F, NCB Innovation Centre 888 Lai Chi Kok Road, Cheung Sha Wan, Kowloon, Hong Kong

Registry name: XIM-HK - Room A03, 22/F, NCB Innovation Centre 888 Lai Chi Kok Road, Cheung Sha Wan, Kowloon, Hong Kong, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55953, 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.230.15.11/32 Invalid: maxLength Nonecovered by 103.230.15.0/24 3 0%low visibility 3
103.230.15.146/32 Invalid: maxLength Nonecovered by 103.230.15.0/24 3 0%low visibility 3
103.230.13.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.230.14.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.230.15.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67

AS-SET

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

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.230.15.11/32ROA 103.230.15.0/24 AS55953 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.230.15.11/32.3 of 673
Route object: none103.230.15.11/32No route object for it. A route object for 103.230.15.0/24 with origin AS55953 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55953 in the RIR database for the space.3 of 673
ROA: maxLength103.230.15.146/32ROA 103.230.15.0/24 AS55953 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.230.15.146/32.3 of 673
Route object: none103.230.15.146/32No route object for it. A route object for 103.230.15.0/24 with origin AS55953 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55953 in the RIR database for the space.3 of 673

Route objects not announced

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

103.225.8.0/24NTTCOM, RADBNo ROA
103.225.9.0/24NTTCOM, RADBNo ROA
103.254.209.0/24NTTCOM, RADBNo ROA
103.254.210.0/24NTTCOM, RADBNo ROA
103.254.211.0/24NTTCOM, RADBNo ROA
113.52.132.0/24NTTCOM, RADBNo ROA
113.52.133.0/24NTTCOM, RADBNo ROA
113.52.134.0/24NTTCOM, RADBNo ROA
113.52.135.0/24NTTCOM, RADBNo ROA
122.128.109.0/24NTTCOM, RADBNo ROA

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.