Network · data from 2026-11-12
AS218797 CHEUNGZIT-TRADE-LIMITED CHEUNGZIT TRADE LIMITED
Registry name: CHEUNGZIT-TRADE-LIMITED CHEUNGZIT TRADE LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218797, 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.
| 5.199.18.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 5.199.29.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 5.199.51.0/24 | Invalid: origin | None | 2 0%low visibility |
| 68.164.134.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 83.245.40.0/24 | Invalid: origin | None | 2 0%low visibility |
| 147.125.195.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 147.125.231.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 87.83.2.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 91.124.210.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 82.40.52.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 82.40.53.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
AS218797 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 34 are in fix.csv.
- ROA: origin5
- Route object: none5
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.199.18.0/24 | ROAs covering it name AS834, not AS218797. If AS218797 should announce it, add a ROA for AS218797. |
| Route object: none | 5.199.18.0/24 | Route objects for it name AS834. Add a route object with origin AS218797 in the RIR database for the space. |
| ROA: origin | 5.199.29.0/24 | ROAs covering it name AS834, not AS218797. If AS218797 should announce it, add a ROA for AS218797. |
| Route object: none | 5.199.29.0/24 | Route objects for it name AS834. Add a route object with origin AS218797 in the RIR database for the space. |
| ROA: origin | 5.199.51.0/24 | ROAs covering it name AS834, not AS218797. If AS218797 should announce it, add a ROA for AS218797. |
| Route object: none | 5.199.51.0/24 | No route object for it. Add a route object with origin AS218797 in the RIR database for the space. |
| ROA: origin | 68.164.134.0/24 | ROAs covering it name AS834, not AS218797. If AS218797 should announce it, add a ROA for AS218797. |
| Route object: none | 68.164.134.0/24 | Route objects for it name AS834. Add a route object with origin AS218797 in the RIR database for the space. |
| ROA: origin | 83.245.40.0/24 | ROAs covering it name AS834, AS3257, not AS218797. If AS218797 should announce it, add a ROA for AS218797. |
| Route object: none | 83.245.40.0/24 | No route object for it. Add a route object with origin AS218797 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218797 whose prefix no peer sees AS218797 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.202.222.0/24 | RADB, RIPE | Valid |
| 61.15.192.0/24 | APNIC | Invalid: origin |
| 61.15.194.0/24 | APNIC | Invalid: origin |
| 61.18.161.0/24 | APNIC | Invalid: origin |
| 61.18.163.0/24 | APNIC | Invalid: origin |
| 61.18.165.0/24 | APNIC | Invalid: origin |
| 61.18.171.0/24 | APNIC | Invalid: origin |
| 61.18.173.0/24 | APNIC | Invalid: origin |
| 61.18.175.0/24 | APNIC | Invalid: origin |
| 82.40.54.0/24 | RADB, RIPE | Valid |
| 82.47.184.0/24 | RADB, RIPE | Valid |
| 82.47.206.0/24 | RADB, RIPE | Valid |
| 82.139.216.0/24 | RADB, RIPE | Valid |
| 91.124.211.0/24 | RADB, RIPE | Valid |
| 95.135.6.0/24 | RADB, RIPE | Valid |
| 104.140.120.0/24 | ARIN, RADB | Valid |
| 147.90.47.0/24 | RADB, RIPE | Valid |
| 147.90.65.0/24 | RADB, RIPE | Valid |
| 147.125.132.0/24 | RADB, RIPE | Valid |
| 147.125.159.0/24 | RADB, RIPE | Valid |
| 147.125.161.0/24 | RADB, RIPE | Valid |
| 147.125.229.0/24 | RADB, RIPE | Valid |
| 178.94.1.0/24 | RADB, RIPE | Valid |
| 217.216.132.0/24 | RADB, RIPE | Valid |
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.