bgpreport

Network · data from 2026-11-12

AS133322 XIM-HK - XIMBO Internet Limited

Registry name: XIM-HK - XIMBO Internet Limited, HK · not in PeeringDB

11IPv4 routes 0.0% RPKI valid · 45.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
11No ROA 6 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS133322, seen from no peer

Announced routes

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

43.228.124.243/32 No ROA Nonecovered by 43.228.124.0/24 2 0%low visibility 5
43.228.125.136/32 No ROA Nonecovered by 43.228.125.0/24 2 0%low visibility 5
43.228.125.194/32 No ROA Nonecovered by 43.228.125.0/24 2 0%low visibility 5
43.228.126.9/32 No ROA Nonecovered by 43.228.126.0/24 2 0%low visibility 5
43.228.126.24/32 No ROA Nonecovered by 43.228.126.0/24 2 0%low visibility 5
45.115.38.117/32 No ROA Nonecovered by 45.115.38.0/24 2 0%low visibility 5
43.228.124.0/24 No ROA Other IRR onlyRADB 673 100% 68
43.228.125.0/24 No ROA Other IRR onlyRADB 673 100% 68
43.228.126.0/24 No ROA Other IRR onlyRADB 673 100% 68
43.228.127.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
45.115.38.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68

AS-SET

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

  • ROA: none11
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none43.228.124.243/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none43.228.124.243/32No route object for it. A route object for 43.228.124.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none43.228.125.136/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none43.228.125.136/32No route object for it. A route object for 43.228.125.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none43.228.125.194/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none43.228.125.194/32No route object for it. A route object for 43.228.125.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none43.228.126.9/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none43.228.126.9/32No route object for it. A route object for 43.228.126.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none43.228.126.24/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none43.228.126.24/32No route object for it. A route object for 43.228.126.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none45.115.38.117/32No ROA covers it. Add a ROA for AS133322, maxLength 32.2 of 673
Route object: none45.115.38.117/32No route object for it. A route object for 45.115.38.0/24 with origin AS133322 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS133322 in the RIR database for the space.2 of 673
ROA: none43.228.124.0/24No ROA covers it. Add a ROA for AS133322, maxLength 24.673 of 673
Route object: RIR43.228.124.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none43.228.125.0/24No ROA covers it. Add a ROA for AS133322, maxLength 24.673 of 673
Route object: RIR43.228.125.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none43.228.126.0/24No ROA covers it. Add a ROA for AS133322, maxLength 24.673 of 673
Route object: RIR43.228.126.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none43.228.127.0/24No ROA covers it. Add a ROA for AS133322, maxLength 24.673 of 673
ROA: none45.115.38.0/24No ROA covers it. Add a ROA for AS133322, maxLength 24.673 of 673

Route objects not announced

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

103.30.16.0/22RADBNo ROA
103.225.8.0/24NTTCOM, RADBNo ROA
103.225.9.0/24NTTCOM, RADBNo ROA
103.251.115.0/24RADBNo 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
203.86.234.0/24RADBNo ROA
2001:470:326::/48ARINValid

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.