Network · data from 2026-11-12
AS141025 CT-LIAONING-SHENYANG-MAN - Shenyang MAN, Liaoning, China Telecom
Registry name: CT-LIAONING-SHENYANG-MAN - Shenyang MAN, Liaoning, China Telecom, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141025, 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.
| 59.47.246.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 240e:60c:8000::/48 | Valid | None | 635 100% |
| 59.46.34.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 240e:981:240c::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 240e:981:2500::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 59.44.46.0/24 | Valid | Other IRR onlyRADB | 6 1%low visibility |
| 123.177.56.0/22 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS141025 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 10 are in fix.csv.
- ROA: origin1
- Route object: none2
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 59.47.246.0/24 | ROAs covering it name AS58777, not AS141025. If AS141025 should announce it, add a ROA for AS141025. |
| Route object: none | 59.47.246.0/24 | Route objects for it name AS58777. Add a route object with origin AS141025 in the RIR database for the space. |
| Route object: none | 240e:60c:8000::/48 | No route object for it. Add a route object with origin AS141025 in the RIR database for the space. |
| Route object: RIR | 59.46.34.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:981:240c::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 240e:981:2500::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 59.44.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.177.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141025 whose prefix no peer sees AS141025 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 240e:983:201::/48 | RADB | No ROA |
| 240e:983:202::/48 | 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.