Network · data from 2026-11-12
AS133952 Zhengzhou Longling Technology Co., Ltd.
Registry name: ZLTL-AS-AP - Zhengzhou longling technology ltd., CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133952, 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.
| 206.54.1.128/25 | Valid | None | 31 5%low visibility |
| 150.107.61.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 43.230.137.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.230.138.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.49.196.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.49.198.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.90.81.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.90.82.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.230.136.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.230.139.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.49.199.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.80.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.83.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 112.196.208.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS133952's PeeringDB record names no 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.
- Route object: none1
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 206.54.1.128/25 | No route object for it. Add a route object with origin AS133952 in the RIR database for the space. |
| Route object: RIR | 150.107.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133952 whose prefix no peer sees AS133952 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.230.136.0/22 | APNIC | Valid |
| 43.230.136.0/23 | APNIC | Valid |
| 43.230.138.0/23 | APNIC | Valid |
| 103.49.196.0/22 | APNIC | Valid |
| 103.49.196.0/23 | APNIC | Valid |
| 103.49.197.0/24 | APNIC | Valid |
| 103.49.198.0/23 | APNIC | Valid |
| 123.253.168.0/24 | APNIC | No ROA |
| 2400:f7c0::/32 | APNIC | 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.