Network · data from 2026-11-12
AS17799 CHINATELECOM-LN-AS-AP - asn for Liaoning Provincial Net of CT
Registry name: CHINATELECOM-LN-AS-AP - asn for Liaoning Provincial Net of CT, CN · not in PeeringDB
27IPv4 routes
100.0% RPKI valid · 100.0% with a route object
5IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
11Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS17799, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17799, 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.
| 42.248.152.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 115.168.37.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 115.168.69.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 182.201.201.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.194.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.196.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.200.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.202.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.203.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.204.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.205.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.206.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.207.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.209.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.148.210.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 240e:1:f800::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:41:c000::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:86:8000::/36 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:981:2600::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:983:203::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 123.177.0.0/22 | Valid | Other IRR onlyRADB | 11 2%low visibility |
| 42.249.128.0/19 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 123.177.128.0/18 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 123.177.192.0/18 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 123.246.255.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 123.247.128.0/17 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 182.205.0.0/16 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 182.205.0.0/18 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 182.205.128.0/17 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 182.206.0.0/16 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 182.206.0.0/17 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 218.30.170.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
AS17799 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: RIR31
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 42.248.152.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.168.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.168.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.201.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.194.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.200.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.204.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.209.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.148.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:1:f800::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:41:c000::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:86:8000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:981:2600::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:983:203::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.177.0.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 42.249.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.177.128.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.177.192.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.246.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.247.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.205.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.205.0.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.205.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.206.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 182.206.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17799 whose prefix no peer sees AS17799 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.39.104.0/22 | RADB | No ROA |
| 116.196.0.0/21 | NTTCOM, RADB | No ROA |
| 118.85.214.0/24 | RADB | No ROA |
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.