Network · data from 2026-11-12
AS59068 SPDB-CN - Shanghai Pudong Development Bank Co.,Ltd.
Registry name: SPDB-CN - Shanghai Pudong Development Bank Co.,Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59068, 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.
| 2405:3140:3a::/48 | No ROA | Other IRR onlyRADB | 636 100% |
| 101.49.206.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 101.49.207.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS59068 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 11 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2405:3140:3a::/48 | No ROA covers it. Add a ROA for AS59068, maxLength 48. |
| Route object: RIR | 2405:3140:3a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.49.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.49.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59068 whose prefix no peer sees AS59068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.49.196.0/22 | RADB | No ROA |
| 101.49.196.0/24 | RADB | No ROA |
| 101.49.200.0/22 | RADB | No ROA |
| 101.49.204.0/23 | RADB | No ROA |
| 101.49.216.0/22 | RADB | No ROA |
| 101.49.220.0/23 | RADB | No ROA |
| 101.49.224.0/19 | 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.