Network · data from 2026-11-12
AS135293 EZCHK-AS-AP - Ezlink Cloud Technology Co., Limted
Registry name: EZCHK-AS-AP - Ezlink Cloud Technology Co., Limted, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135293, 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.104.150.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 137.83.0.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.139.199.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 156.227.2.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.227.3.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
AS-SET
AS135293 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 6 are in fix.csv.
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.104.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135293 whose prefix no peer sees AS135293 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.104.148.0/24 | APNIC | Invalid: origin |
| 103.104.149.0/24 | APNIC | Invalid: origin |
| 103.139.198.0/23 | RADB | No ROA |
| 156.227.2.0/23 | RADB | No ROA |
| 2001:df0:8f80::/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.