Network · data from 2026-11-12
AS24413 Shanghai263 - 263 Shanghai Communications Ltd.
Registry name: Shanghai263 - 263 Shanghai Communications Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24413, 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.
| 114.28.229.0/24 | No ROA | Nonecovered by 114.28.224.0/20 | 673 100% |
| 202.46.39.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 156.230.11.0/24 | Valid | RIR databaseAFRINIC, RADB | 282 42% |
AS-SET
AS24413 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 24 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 114.28.229.0/24 | No ROA covers it. Add a ROA for AS24413, maxLength 24. |
| Route object: none | 114.28.229.0/24 | No route object for it. A route object for 114.28.224.0/20 with origin AS24413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24413 in the RIR database for the space. |
| ROA: none | 202.46.39.0/24 | No ROA covers it. Add a ROA for AS24413, maxLength 24. |
| Route object: RIR | 202.46.39.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24413 whose prefix no peer sees AS24413 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.166.174.0/24 | APNIC, RADB | Valid |
| 103.166.175.0/24 | APNIC | Valid |
| 114.28.193.0/24 | RADB | No ROA |
| 114.28.200.0/24 | RADB | Valid |
| 114.28.201.0/24 | RADB | Valid |
| 114.28.224.0/20 | NTTCOM, RADB | No ROA |
| 114.28.228.0/24 | RADB | Valid |
| 114.28.232.0/24 | RADB | Valid |
| 114.28.236.0/22 | NTTCOM, RADB | No ROA |
| 114.28.238.0/24 | RADB | Valid |
| 153.254.119.0/24 | NTTCOM | Valid |
| 202.46.32.0/19 | NTTCOM | No ROA |
| 202.46.32.0/20 | NTTCOM | No ROA |
| 202.46.32.0/24 | NTTCOM, RADB | Valid |
| 202.46.33.0/24 | RADB | Valid |
| 202.46.34.0/24 | RADB | Valid |
| 202.46.41.0/24 | RADB | Valid |
| 202.46.42.0/24 | RADB | Valid |
| 202.46.47.0/24 | NTTCOM | No ROA |
| 2402:33c0::/32 | NTTCOM, 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.