bgpreport

Network · data from 2026-11-12

AS64079 CTGL-IPX - China Telecom Global Limited

Registry name: CTGL-IPX - China Telecom Global Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64079, 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.
2400:9380:f267::/48 Invalid: maxLength Other origin onlycovered by 2400:9380:f200::/40 115 18% 43
203.56.50.0/24 Valid None 672 100% 66
203.86.121.0/24 Valid Other IRR onlyRADB 672 100% 66
203.86.125.0/24 Valid Other IRR onlyRADB 672 100% 66
203.86.118.0/24 Valid Other IRR onlyRADB 671 100% 66
203.86.119.0/24 Valid Other IRR onlyRADB 671 100% 66
203.86.122.0/24 Valid Other IRR onlyRADB 671 100% 66
203.86.123.0/24 Valid Other IRR onlyRADB 671 100% 66
203.86.124.0/24 Valid Other IRR onlyRADB 671 100% 66
220.247.138.0/24 Valid Other IRR onlyRADB 671 100% 66
220.247.139.0/24 Valid Other IRR onlyRADB 671 100% 66
61.29.254.0/23 Valid RIR databaseAPNIC 672 100% 66
146.196.78.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
146.196.79.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
61.29.244.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
61.29.254.0/24 Valid RIR databaseAPNIC 671 100% 66
103.211.193.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.211.192.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
2400:9380:f1ff::/48 Valid RIR databaseAPNIC 635 100% 67
2400:9380:f2ff::/48 Valid RIR databaseAPNIC 635 100% 69
2400:9380:9265::/48 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:f105::/48 Valid RIR databaseAPNIC 634 100% 67
2400:9380:f14f::/48 Valid RIR databaseAPNIC 634 100% 67
101.47.189.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • ROA: maxLength1
  • Route object: none2
  • Route object: RIR9
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: maxLength2400:9380:f267::/48ROA 2400:9380:f200::/40 AS64079 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2400:9380:f267::/48.115 of 636
Route object: none2400:9380:f267::/48Route objects for it name AS23764. A route object for 2400:9380:f200::/40 with origin AS64079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64079 in the RIR database for the space.115 of 636
Route object: none203.56.50.0/24No route object for it. Add a route object with origin AS64079 in the RIR database for the space.672 of 673
Route object: RIR203.86.121.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.86.125.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.86.118.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.86.119.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.86.122.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.86.123.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.86.124.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR220.247.138.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR220.247.139.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

23.139.244.0/24ARINValid
23.144.172.0/24ARINValid
61.29.244.0/22APNICValid
61.29.244.0/23APNICValid
61.29.245.0/24APNIC, RADBValid
61.29.246.0/23APNICValid
61.29.246.0/24APNIC, RADBValid
61.29.247.0/24APNIC, RADBValid
69.194.169.0/24APNIC, RADBValid
146.196.78.0/23APNICValid
203.86.120.0/24RADBValid
2400:9380:f000::/40APNIC, RADBValid
2400:9380:f100::/40APNIC, RADBValid
2400:9380:f1bc::/48APNICValid
2400:9380:f200::/40RADBValid
2400:9380:f245::/48APNICValid
2400:9380:f300::/40APNIC, 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.