Network · data from 2026-11-12
AS17633 CHINATELECOM-SD-AS-AP - ASN for Shandong Provincial Net of CT
Registry name: CHINATELECOM-SD-AS-AP - ASN for Shandong Provincial Net of CT, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17633, 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.
| 202.111.247.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 219.146.0.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.0.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.1.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.2.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.3.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.4.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.10.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.11.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.12.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.13.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.14.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.15.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 219.146.23.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 240e:e:a800::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:4e::/37 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:4e::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:4e:4::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:4e:5::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 202.111.230.0/24 | Valid | Other IRR onlyRADB | 603 90% |
AS-SET
AS17633 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 20 are in fix.csv.
- Route object: RIR20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 202.111.247.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.0.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.1.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.3.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.146.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:e:a800::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:4e::/37 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:4e::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:4e:4::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:4e:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.111.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS17633 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.