bgpreport

Network · data from 2026-11-12

AS17619 Powernetix

Registry name: POWERNETIX-AS - POWERNETIX, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17619, 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.
202.85.224.0/20 No ROA RIR databaseAPNIC 673 100% 67

AS-SET

AS17619's PeeringDB record names no 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 44 are in fix.csv.

  • ROA: none1
  • Route object: not announced43
ChangePrefix or setDetailFull-table peers
ROA: none202.85.224.0/20No ROA covers it. Add a ROA for AS17619, maxLength 20.673 of 673

Route objects not announced

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

103.13.243.0/24NTTCOMNo ROA
116.68.184.0/21NTTCOM, RADBNo ROA
116.68.184.0/24NTTCOM, RADBNo ROA
116.68.185.0/24NTTCOM, RADBNo ROA
116.68.186.0/24NTTCOM, RADBNo ROA
116.68.187.0/24NTTCOM, RADBNo ROA
116.68.188.0/24NTTCOM, RADBNo ROA
116.68.189.0/24NTTCOM, RADBNo ROA
116.68.190.0/24NTTCOM, RADBNo ROA
116.68.191.0/24NTTCOM, RADBNo ROA
202.51.128.0/19NTTCOM, RADBNo ROA
202.51.128.0/20NTTCOM, RADBNo ROA
202.51.128.0/21NTTCOM, RADBNo ROA
202.51.128.0/22NTTCOM, RADBNo ROA
202.51.128.0/23NTTCOM, RADBNo ROA
202.51.130.0/23NTTCOMNo ROA
202.51.132.0/22NTTCOMNo ROA
202.51.132.0/23NTTCOMNo ROA
202.51.134.0/23NTTCOMNo ROA
202.51.136.0/21NTTCOMNo ROA
202.51.136.0/22NTTCOMNo ROA
202.51.136.0/23NTTCOMNo ROA
202.51.138.0/23NTTCOMNo ROA
202.51.140.0/22NTTCOMNo ROA
202.51.140.0/23NTTCOMNo ROA
202.51.142.0/23NTTCOMNo ROA
202.51.144.0/20NTTCOM, RADBNo ROA
202.51.144.0/21NTTCOM, RADBNo ROA
202.51.144.0/22NTTCOM, RADBNo ROA
202.51.144.0/23NTTCOM, RADBNo ROA
202.51.146.0/23NTTCOM, RADBNo ROA
202.51.148.0/22NTTCOM, RADBNo ROA
202.51.148.0/23NTTCOM, RADBNo ROA
202.51.150.0/23NTTCOM, RADBNo ROA
202.51.152.0/21NTTCOM, RADBNo ROA
202.51.152.0/22NTTCOM, RADBNo ROA
202.51.152.0/23NTTCOM, RADBNo ROA
202.51.154.0/23NTTCOM, RADBNo ROA
202.51.156.0/22NTTCOM, RADBNo ROA
202.51.156.0/23NTTCOM, RADBNo ROA
202.51.158.0/23NTTCOM, RADBNo ROA
202.170.0.0/19NTTCOM, RADBNo ROA
203.89.133.0/24NTTCOMNo 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.