Network · data from 2026-11-12
AS137691 CHINATELECOM-HEILONGJIANG-IDC - Heilongjiang Province, P.R.China.
Registry name: CHINATELECOM-HEILONGJIANG-IDC - Heilongjiang Province, P.R.China., CN · not in PeeringDB
37IPv4 routes
97.3% RPKI valid · 0.0% with a route object
18IPv6 routes
100.0% RPKI valid · 0.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
55 with no route object for this origin
34Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS137691, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS137691, 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.
| 43.225.208.0/22 | Invalid: origin | None | 125 19% |
| 123.166.123.0/24 | Valid | None | 673 100% |
| 222.171.248.0/24 | Valid | None | 672 100% |
| 240e:1:800::/37 | Valid | None | 636 100% |
| 240e:85:8000::/37 | Valid | None | 636 100% |
| 240e:85:8010::/48 | Valid | None | 636 100% |
| 240e:108:4061::/48 | Valid | None | 636 100% |
| 240e:108:4861::/48 | Valid | None | 636 100% |
| 240e:308::/36 | Valid | None | 636 100% |
| 240e:308:1000::/39 | Valid | None | 636 100% |
| 240e:309::/36 | Valid | None | 636 100% |
| 240e:309:1000::/39 | Valid | None | 636 100% |
| 240e:30a::/36 | Valid | None | 636 100% |
| 240e:30a:1000::/39 | Valid | None | 636 100% |
| 240e:30b::/36 | Valid | None | 636 100% |
| 240e:30b:1000::/39 | Valid | None | 636 100% |
| 240e:608::/36 | Valid | None | 636 100% |
| 240e:608:d04::/48 | Valid | None | 636 100% |
| 240e:608:d05::/48 | Valid | None | 636 100% |
| 240e:608:d07::/48 | Valid | None | 636 100% |
| 240e:608:1000::/39 | Valid | None | 636 100% |
| 42.100.0.0/18 | Valid | None | 7 1%low visibility |
| 42.101.208.0/20 | Valid | None | 7 1%low visibility |
| 42.103.32.0/19 | Valid | None | 7 1%low visibility |
| 42.184.0.0/18 | Valid | None | 7 1%low visibility |
| 42.185.0.0/18 | Valid | None | 7 1%low visibility |
| 42.185.64.0/20 | Valid | None | 7 1%low visibility |
| 42.185.112.0/20 | Valid | None | 7 1%low visibility |
| 42.185.144.0/20 | Valid | None | 7 1%low visibility |
| 112.99.112.0/20 | Valid | None | 7 1%low visibility |
| 112.99.116.0/24 | Valid | None | 7 1%low visibility |
| 112.99.240.0/20 | Valid | None | 7 1%low visibility |
| 112.100.4.0/22 | Valid | None | 7 1%low visibility |
| 112.100.102.0/24 | Valid | None | 7 1%low visibility |
| 112.100.103.0/24 | Valid | None | 7 1%low visibility |
| 112.100.116.0/24 | Valid | None | 7 1%low visibility |
| 112.102.0.0/16 | Valid | None | 7 1%low visibility |
| 112.103.0.0/16 | Valid | None | 7 1%low visibility |
| 123.165.0.0/16 | Valid | None | 7 1%low visibility |
| 123.166.0.0/16 | Valid | None | 7 1%low visibility |
| 123.166.124.0/24 | Valid | None | 7 1%low visibility |
| 123.167.128.0/21 | Valid | None | 7 1%low visibility |
| 123.167.136.0/21 | Valid | None | 7 1%low visibility |
| 123.167.188.0/24 | Valid | None | 7 1%low visibility |
| 219.147.160.0/19 | Valid | None | 7 1%low visibility |
| 222.171.0.0/19 | Valid | None | 7 1%low visibility |
| 222.171.32.0/19 | Valid | None | 7 1%low visibility |
| 222.171.64.0/19 | Valid | None | 7 1%low visibility |
| 222.171.96.0/19 | Valid | None | 7 1%low visibility |
| 222.171.128.0/19 | Valid | None | 7 1%low visibility |
| 222.171.160.0/19 | Valid | None | 7 1%low visibility |
| 222.171.192.0/20 | Valid | None | 7 1%low visibility |
| 222.171.208.0/20 | Valid | None | 7 1%low visibility |
| 222.171.224.0/20 | Valid | None | 7 1%low visibility |
| 222.171.240.0/20 | Valid | None | 7 1%low visibility |
AS-SET
AS137691 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 56 are in fix.csv.
- ROA: origin1
- Route object: none55
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 43.225.208.0/22 | ROAs covering it name AS131506, not AS137691. If AS137691 should announce it, add a ROA for AS137691. |
| Route object: none | 43.225.208.0/22 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.166.123.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.248.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:1:800::/37 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:85:8000::/37 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:85:8010::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:108:4061::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:108:4861::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:308::/36 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:308:1000::/39 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:309::/36 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:309:1000::/39 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:30a::/36 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:30a:1000::/39 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:30b::/36 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:30b:1000::/39 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:608::/36 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:608:d04::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:608:d05::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:608:d07::/48 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 240e:608:1000::/39 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.100.0.0/18 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.101.208.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.103.32.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.184.0.0/18 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.185.0.0/18 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.185.64.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.185.112.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 42.185.144.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.99.112.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.99.116.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.99.240.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.100.4.0/22 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.100.102.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.100.103.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.100.116.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.102.0.0/16 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 112.103.0.0/16 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.165.0.0/16 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.166.0.0/16 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.166.124.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.167.128.0/21 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.167.136.0/21 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 123.167.188.0/24 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 219.147.160.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.0.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.32.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.64.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.96.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.128.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.160.0/19 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.192.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.208.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.224.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
| Route object: none | 222.171.240.0/20 | No route object for it. Add a route object with origin AS137691 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS137691 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.