Network · data from 2026-11-12
AS59009 WXData - QingDao WangXin Telcom Corp. Limited
Registry name: WXData - QingDao WangXin Telcom Corp. Limited, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59009, 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.
| 103.233.228.0/22 | No ROA | None | 24 4%low visibility |
| 150.242.152.0/22 | No ROA | None | 24 4%low visibility |
| 43.240.60.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.36.36.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.235.136.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.235.137.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.235.138.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.235.139.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.254.76.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.254.79.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.254.77.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 88 13% |
| 103.254.78.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 88 13% |
| 103.254.76.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 4 1%low visibility |
AS-SET
AS59009 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.
- ROA: none2
- Route object: none2
- Route object: RIR11
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.233.228.0/22 | No ROA covers it. Add a ROA for AS59009, maxLength 22. |
| Route object: none | 103.233.228.0/22 | No route object for it. Add a route object with origin AS59009 in the RIR database for the space. |
| ROA: none | 150.242.152.0/22 | No ROA covers it. Add a ROA for AS59009, maxLength 22. |
| Route object: none | 150.242.152.0/22 | No route object for it. Add a route object with origin AS59009 in the RIR database for the space. |
| Route object: RIR | 43.240.60.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.36.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.136.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.137.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.138.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.235.139.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.76.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.79.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.77.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.78.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.254.76.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59009 whose prefix no peer sees AS59009 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.240.60.0/24 | RADB | Valid |
| 43.240.61.0/24 | RADB | Valid |
| 43.240.62.0/24 | RADB | Valid |
| 43.240.63.0/24 | RADB | Valid |
| 2402:36e0::/32 | 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.