Network · data from 2026-11-12
AS17897 CHINATELECOM-HLJ-AS-AP - asn for Heilongjiang Provincial Net of CT
Registry name: CHINATELECOM-HLJ-AS-AP - asn for Heilongjiang Provincial Net of CT, CN · not in PeeringDB
16IPv4 routes
93.8% RPKI valid · 25.0% with a route object
9IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
21 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS17897, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17897, 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.
| 123.167.128.0/18 | No ROA | Other IRR onlyRADB | 672 100% |
| 112.100.92.0/24 | Valid | Nonecovered by 112.100.0.0/15 | 672 100% |
| 112.100.101.0/24 | Valid | Nonecovered by 112.100.0.0/15 | 672 100% |
| 219.147.71.0/24 | Valid | None | 672 100% |
| 219.147.72.0/24 | Valid | None | 672 100% |
| 219.147.128.0/20 | Valid | None | 672 100% |
| 219.147.129.0/24 | Valid | None | 672 100% |
| 219.147.130.0/24 | Valid | None | 672 100% |
| 219.147.133.0/24 | Valid | None | 672 100% |
| 219.147.136.0/24 | Valid | None | 672 100% |
| 219.147.137.0/24 | Valid | None | 672 100% |
| 219.147.144.0/20 | Valid | None | 672 100% |
| 219.147.248.0/21 | Valid | None | 672 100% |
| 240e:1::/37 | Valid | None | 636 100% |
| 240e:41::/37 | Valid | None | 636 100% |
| 240e:41:4000::/37 | Valid | None | 636 100% |
| 240e:981:1109::/48 | Valid | None | 636 100% |
| 240e:981:110a::/48 | Valid | None | 636 100% |
| 240e:981:1500::/40 | Valid | None | 636 100% |
| 240e:981:1600::/40 | Valid | None | 636 100% |
| 240e:983:103::/48 | Valid | None | 636 100% |
| 240e:983:104::/48 | Valid | None | 636 100% |
| 112.100.0.0/15 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 112.100.96.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 112.100.100.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS17897 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 26 are in fix.csv.
- ROA: none1
- Route object: none21
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 123.167.128.0/18 | No ROA covers it. Add a ROA for AS17897, maxLength 18. |
| Route object: RIR | 123.167.128.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 112.100.92.0/24 | No route object for it. A route object for 112.100.0.0/15 with origin AS17897 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 112.100.101.0/24 | No route object for it. A route object for 112.100.0.0/15 with origin AS17897 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.71.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.72.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.128.0/20 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.129.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.130.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.133.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.136.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.137.0/24 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.144.0/20 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 219.147.248.0/21 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:1::/37 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:41::/37 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:41:4000::/37 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:981:1109::/48 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:981:110a::/48 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:981:1500::/40 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:981:1600::/40 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:983:103::/48 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: none | 240e:983:104::/48 | No route object for it. Add a route object with origin AS17897 in the RIR database for the space. |
| Route object: RIR | 112.100.0.0/15 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 112.100.96.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 112.100.100.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17897 is announced.
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.