bgpreport

Network · data from 2026-11-12

AS133384 GTCL-AS-AP - Global Technology Co., Ltd.

Registry name: GTCL-AS-AP - Global Technology Co., Ltd., MM · not in PeeringDB

23IPv4 routes 52.2% RPKI valid · 87.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS133384, seen from no peer

Announced routes

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

38.47.44.0/24 No ROA Other origin only 672 100% 67
38.47.45.0/24 No ROA Other origin only 672 100% 67
38.47.47.0/24 No ROA Other origin only 671 100% 67
38.21.44.0/24 No ROA Other IRR onlyRADB 673 100% 68
38.21.45.0/24 No ROA Other IRR onlyRADB 673 100% 68
38.21.46.0/24 No ROA Other IRR onlyRADB 673 100% 68
38.21.47.0/24 No ROA Other IRR onlyRADB 673 100% 68
204.157.172.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
204.157.173.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
204.157.175.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
204.157.174.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
45.125.4.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.125.5.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.125.6.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
45.125.7.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.25.240.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.25.241.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.231.92.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.231.93.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.231.94.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.25.242.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.25.243.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.231.95.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
2001:df0:9200::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:6ec0::/48 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

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

  • ROA: none11
  • Route object: none3
  • Route object: RIR8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none38.47.44.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.672 of 673
Route object: none38.47.44.0/24Route objects for it name AS133524, AS136975. Add a route object with origin AS133384 in the RIR database for the space.672 of 673
ROA: none38.47.45.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.672 of 673
Route object: none38.47.45.0/24Route objects for it name AS133524, AS136975. Add a route object with origin AS133384 in the RIR database for the space.672 of 673
ROA: none38.47.47.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.671 of 673
Route object: none38.47.47.0/24Route objects for it name AS133524, AS136975. Add a route object with origin AS133384 in the RIR database for the space.671 of 673
ROA: none38.21.44.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR38.21.44.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.21.45.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR38.21.45.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.21.46.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR38.21.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.21.47.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR38.21.47.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.157.172.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR204.157.172.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.157.173.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR204.157.173.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.157.175.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.673 of 673
Route object: RIR204.157.175.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.157.174.0/24No ROA covers it. Add a ROA for AS133384, maxLength 24.672 of 673
Route object: RIR204.157.174.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.21.44.0/22RADBNo ROA
45.125.4.0/22APNIC, RADBValid
103.25.240.0/22APNIC, NTTCOM, RADBValid
103.231.92.0/22APNIC, NTTCOM, RADBValid
204.157.172.0/22NTTCOM, RADBNo ROA
204.157.172.0/23NTTCOM, RADBNo ROA
204.157.174.0/23NTTCOM, RADBNo ROA
2407:6ec0::/32APNIC, RADBValid

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.