bgpreport

Network · data from 2026-11-12

AS63527 China Telecom Global IPX

Registry name: CTGL-AS - China Telecom Global Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63527, 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.
203.12.88.0/24 Valid Other IRR onlyRADB 672 100% 66
203.12.89.0/24 Valid Other IRR onlyRADB 672 100% 66
63.140.1.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
63.140.2.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
210.5.57.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66

AS-SET

AS63527'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 10 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR203.12.88.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.12.89.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 AS63527 whose prefix no peer sees AS63527 announce. Many are kept on purpose (backup routes, space announced only in some places).

63.140.12.0/24APNIC, RADBValid
203.12.88.0/23RADBNo ROA
203.12.90.0/24RADBNo ROA
203.89.13.0/24APNIC, RADBValid
2400:9380:801a::/48APNICValid
2400:9380:801b::/48APNICValid
2400:9380:801c::/48APNICValid
2400:9380:801d::/48APNICValid

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.