bgpreport

Network · data from 2026-11-12

AS59217 Azonne Limited

Registry name: AZONNELIMITED-AS-AP - Azonne Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59217, 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.
63.222.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
103.114.44.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.114.46.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.114.46.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.114.47.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
209.8.118.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
43.248.248.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.248.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.248.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.249.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.250.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.250.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
43.248.251.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.114.44.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.114.44.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.114.45.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.164.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.164.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.164.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.165.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.166.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.166.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
103.243.167.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 653 97% 67
2402:c940::/32 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 69
2402:cac0::/32 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS59217: RADB::AS-AZONNE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS59217 isn't in the set, or no route object for AS59217 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS59217 in itNot covered
RADB::AS-AZONNE RADB 61236 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS59217 is announced.

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.