bgpreport

Network · data from 2026-11-12

AS218200 APPMAX-LIMITED HONGKONG APPMAX LIMITED

Registry name: APPMAX-LIMITED HONGKONG APPMAX LIMITED, HK · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 66.7% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS218200, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS218200, 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.
217.8.20.0/24 Invalid: origin None 62 9%low visibility 33
217.8.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
143.203.135.0/24 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS218200 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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin217.8.20.0/24ROAs covering it name AS13285, AS19905, not AS218200. If AS218200 should announce it, add a ROA for AS218200.62 of 673
Route object: none217.8.20.0/24No route object for it. Add a route object with origin AS218200 in the RIR database for the space.62 of 673

Route objects not announced

Route objects with origin AS218200 whose prefix no peer sees AS218200 announce. Many are kept on purpose (backup routes, space announced only in some places).

144.56.116.0/24RADB, RIPEValid
154.16.222.0/24RADBValid
178.92.178.0/24RADB, RIPEValid
178.93.191.0/24RADB, RIPEValid
194.231.142.0/24RADB, RIPEValid
217.8.204.0/24RADB, RIPEValid
217.8.206.0/24RADB, RIPEValid
217.8.207.0/24RADB, RIPEValid

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.