bgpreport

Network · data from 2026-11-12

AS17649 DMZGLOBAL-AP - DMZGlobal Ltd

Registry name: DMZGLOBAL-AP - DMZGlobal Ltd, NZ · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS17649, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17649, 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.
116.89.224.0/20 Valid RIR databaseAPNIC 671 100% 68
203.144.32.0/20 Valid RIR databaseAPNIC 671 100% 68
2406:9a00::/32 Valid RIR databaseAPNIC 635 100% 69
203.97.224.0/24 Valid RIR databaseAPNIC 2 0%low visibility 1
203.97.225.0/24 Valid RIR databaseAPNIC 2 0%low visibility 1
203.97.226.0/24 Valid RIR databaseAPNIC 2 0%low visibility 1
203.97.227.0/24 Valid RIR databaseAPNIC 2 0%low visibility 1
203.97.229.0/24 Valid RIR databaseAPNIC 2 0%low visibility 1

AS-SET

AS17649 isn't in PeeringDB, where networks name their AS-SET.

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 AS17649 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.