Network · data from 2026-11-12
AS4813 BACKBONE-GUANGDONG-AP - China Telecom(Group)
Registry name: BACKBONE-GUANGDONG-AP - China Telecom(Group), CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4813, 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.
| 14.22.56.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 14.22.60.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 14.22.64.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 240e:982:ec00::/40 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS4813 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.
- Route object: RIR4
- Route object: not announced30
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 14.22.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 14.22.60.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 14.22.64.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:982:ec00::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4813 whose prefix no peer sees AS4813 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.52.236.0/22 | RADB | No ROA |
| 121.10.40.0/24 | APNIC | Valid |
| 125.88.15.0/24 | APNIC | Valid |
| 125.88.58.0/24 | APNIC | Valid |
| 125.88.59.0/24 | APNIC | Valid |
| 125.88.60.0/23 | APNIC | Valid |
| 125.88.88.0/24 | APNIC | Valid |
| 125.88.103.0/24 | APNIC | Valid |
| 125.88.108.0/23 | APNIC | Valid |
| 125.88.114.0/24 | APNIC | Valid |
| 125.88.115.0/24 | APNIC | Valid |
| 125.88.116.0/22 | APNIC | Valid |
| 125.88.120.0/23 | APNIC | Valid |
| 125.88.124.0/22 | APNIC | Valid |
| 125.88.128.0/20 | APNIC | Valid |
| 202.96.168.0/24 | APNIC | Valid |
| 202.103.182.0/24 | APNIC | Valid |
| 202.105.2.0/23 | APNIC | Valid |
| 202.105.5.0/24 | APNIC | Valid |
| 202.105.7.0/24 | APNIC | Valid |
| 202.105.80.0/22 | APNIC | Valid |
| 202.105.212.0/23 | APNIC | Valid |
| 202.105.214.0/24 | APNIC | Valid |
| 202.105.215.0/24 | APNIC | Valid |
| 202.105.240.0/22 | APNIC | Valid |
| 218.13.104.0/22 | APNIC | Valid |
| 218.13.108.0/22 | APNIC | Valid |
| 218.13.112.0/22 | APNIC | Valid |
| 218.13.118.0/23 | APNIC | Valid |
| 218.13.120.0/21 | APNIC | Valid |
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.