bgpreport

Network · data from 2026-11-12

AS2042 zhelet

Registry name: GCT-HK - HK Global Cloud DataCenter, HK · PeeringDB

12IPv4 routes 16.7% RPKI valid · 41.7% with a route object
0IPv6 routes
7RPKI invalid 3 origin · 4 maxLength
3No ROA 7 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS2042, seen from no peer

Announced routes

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

106.3.84.0/22 Invalid: origin Other origin only 7 1%low visibility 4
106.3.84.0/24 Invalid: origin None 4 1%low visibility 3
106.3.87.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.235.172.0/24 Invalid: maxLength Other origin onlycovered by 103.235.172.0/22 4 1%low visibility 3
103.235.174.0/24 Invalid: maxLength Other origin onlycovered by 103.235.172.0/22 4 1%low visibility 3
150.242.218.0/24 Invalid: maxLength Other origin onlycovered by 150.242.216.0/22 4 1%low visibility 3
150.242.219.0/24 Invalid: maxLength Other origin onlycovered by 150.242.216.0/22 4 1%low visibility 3
103.30.200.0/23 No ROA Other IRR onlyRADB 672 100% 67
119.252.251.0/24 No ROA Other IRR onlyRADB 672 100% 67
119.252.254.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.235.172.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
150.242.216.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67

AS-SET

AS2042'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 29 are in fix.csv.

  • ROA: origin3
  • ROA: maxLength4
  • ROA: none3
  • Route object: none7
  • Route object: RIR3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin106.3.84.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS2042 should announce it, add a ROA for AS2042.7 of 673
Route object: none106.3.84.0/22Route objects for it name AS4058, AS9269, AS17554. Add a route object with origin AS2042 in the RIR database for the space.7 of 673
ROA: origin106.3.84.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS2042 should announce it, add a ROA for AS2042.4 of 673
Route object: none106.3.84.0/24No route object for it. Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: origin106.3.87.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS2042 should announce it, add a ROA for AS2042.4 of 673
Route object: none106.3.87.0/24Route objects for it name AS17554. Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: maxLength103.235.172.0/24ROA 103.235.172.0/22 AS2042 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.235.172.0/24.4 of 673
Route object: none103.235.172.0/24Route objects for it name AS17554. A route object for 103.235.172.0/22 with origin AS2042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: maxLength103.235.174.0/24ROA 103.235.172.0/22 AS2042 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 103.235.174.0/24.4 of 673
Route object: none103.235.174.0/24Route objects for it name AS17554. A route object for 103.235.172.0/22 with origin AS2042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: maxLength150.242.218.0/24ROA 150.242.216.0/22 AS2042 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 150.242.218.0/24.4 of 673
Route object: none150.242.218.0/24Route objects for it name AS17554. A route object for 150.242.216.0/22 with origin AS2042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: maxLength150.242.219.0/24ROA 150.242.216.0/22 AS2042 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 150.242.219.0/24.4 of 673
Route object: none150.242.219.0/24Route objects for it name AS17554. A route object for 150.242.216.0/22 with origin AS2042 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2042 in the RIR database for the space.4 of 673
ROA: none103.30.200.0/23No ROA covers it. Add a ROA for AS2042, maxLength 23.672 of 673
Route object: RIR103.30.200.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none119.252.251.0/24No ROA covers it. Add a ROA for AS2042, maxLength 24.672 of 673
Route object: RIR119.252.251.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none119.252.254.0/24No ROA covers it. Add a ROA for AS2042, maxLength 24.672 of 673
Route object: RIR119.252.254.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.31.8.0/22RADBNo ROA
119.252.254.0/23RADBNo ROA
150.242.216.0/23APNICValid
150.242.216.0/24APNICValid
150.242.217.0/24APNIC, RADBValid
202.45.132.0/22NTTCOM, RADBNo ROA
202.75.4.0/22NTTCOMNo ROA
202.184.0.0/14RADBNo ROA
2001:328::/32NTTCOMNo 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.