Network · data from 2026-11-12
AS151397 CT-eSurfingCloud-CDN - China Telecom
Registry name: CT-eSurfingCloud-CDN - China Telecom, CN · not in PeeringDB
19IPv4 routes
100.0% RPKI valid · 100.0% with a route object
5IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
5 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
52Route objects not announced
registered with origin AS151397, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS151397, 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.
| 240e:983:2022::/48 | Valid | Nonecovered by 240e:983:2000::/42 | 635 100% |
| 240e:983:2010::/48 | Valid | Nonecovered by 240e:983:2000::/42 | 634 100% |
| 240e:983:2013::/48 | Valid | Nonecovered by 240e:983:2000::/42 | 634 100% |
| 240e:983:2020::/48 | Valid | Nonecovered by 240e:983:2000::/42 | 634 100% |
| 240e:983:2030::/48 | Valid | Nonecovered by 240e:983:2000::/42 | 634 100% |
| 193.119.13.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 193.119.25.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 193.119.6.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.7.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.8.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.9.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.10.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.20.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.21.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.22.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.28.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.30.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 193.119.4.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 193.119.11.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 193.119.15.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 193.119.17.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 193.119.19.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 193.119.12.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 193.119.0.0/24 | Valid | RIR databaseAPNIC | 668 99% |
AS-SET
AS151397 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 57 are in fix.csv.
- Route object: none5
- Route object: not announced52
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 240e:983:2022::/48 | No route object for it. A route object for 240e:983:2000::/42 with origin AS151397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151397 in the RIR database for the space. |
| Route object: none | 240e:983:2010::/48 | No route object for it. A route object for 240e:983:2000::/42 with origin AS151397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151397 in the RIR database for the space. |
| Route object: none | 240e:983:2013::/48 | No route object for it. A route object for 240e:983:2000::/42 with origin AS151397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151397 in the RIR database for the space. |
| Route object: none | 240e:983:2020::/48 | No route object for it. A route object for 240e:983:2000::/42 with origin AS151397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151397 in the RIR database for the space. |
| Route object: none | 240e:983:2030::/48 | No route object for it. A route object for 240e:983:2000::/42 with origin AS151397 covers it (filters allowing more-specifics accept it). Add a route object with origin AS151397 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151397 whose prefix no peer sees AS151397 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 128.1.12.0/24 | RADB | Valid |
| 128.1.13.0/24 | RADB | Valid |
| 128.1.15.0/24 | RADB | Valid |
| 193.119.0.0/19 | APNIC, RADB | Valid |
| 193.119.0.0/20 | APNIC | Valid |
| 193.119.0.0/21 | APNIC | Valid |
| 193.119.0.0/22 | APNIC | Valid |
| 193.119.0.0/23 | APNIC | Valid |
| 193.119.1.0/24 | APNIC | Valid |
| 193.119.2.0/23 | APNIC | Valid |
| 193.119.2.0/24 | APNIC | Valid |
| 193.119.3.0/24 | APNIC | Valid |
| 193.119.4.0/22 | APNIC | Valid |
| 193.119.4.0/23 | APNIC | Valid |
| 193.119.5.0/24 | APNIC | Valid |
| 193.119.6.0/23 | APNIC | Valid |
| 193.119.8.0/21 | APNIC | Valid |
| 193.119.8.0/22 | APNIC | Valid |
| 193.119.8.0/23 | APNIC | Valid |
| 193.119.10.0/23 | APNIC | Valid |
| 193.119.12.0/22 | APNIC | Valid |
| 193.119.12.0/23 | APNIC | Valid |
| 193.119.14.0/23 | APNIC | Valid |
| 193.119.14.0/24 | APNIC | Valid |
| 193.119.16.0/20 | APNIC | Valid |
| 193.119.16.0/21 | APNIC | Valid |
| 193.119.16.0/22 | APNIC | Valid |
| 193.119.16.0/23 | APNIC | Valid |
| 193.119.16.0/24 | APNIC | Valid |
| 193.119.18.0/23 | APNIC | Valid |
| 193.119.18.0/24 | APNIC | Valid |
| 193.119.20.0/22 | APNIC | Valid |
| 193.119.20.0/23 | APNIC | Valid |
| 193.119.22.0/23 | APNIC | Valid |
| 193.119.23.0/24 | APNIC | Valid |
| 193.119.24.0/21 | APNIC | Valid |
| 193.119.24.0/22 | APNIC | Valid |
| 193.119.24.0/23 | APNIC | Valid |
| 193.119.24.0/24 | APNIC | Valid |
| 193.119.26.0/23 | APNIC | Valid |
| 193.119.26.0/24 | APNIC | Valid |
| 193.119.27.0/24 | APNIC | Valid |
| 193.119.28.0/22 | APNIC | Valid |
| 193.119.28.0/23 | APNIC | Valid |
| 193.119.29.0/24 | APNIC | Valid |
| 193.119.30.0/23 | APNIC | Valid |
| 193.119.31.0/24 | APNIC | Valid |
| 203.86.116.0/24 | APNIC, RADB | Valid |
| 240e:983:2000::/42 | RADB | No ROA |
| 2602:ffe4:c5f::/48 | RADB | Valid |
| 2602:ffe4:c60::/48 | RADB | Valid |
| 2602:ffe4:c61::/48 | RADB | 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.