Network · data from 2026-11-12

AS64179 Zux PY

Registry name: AS64179 - ZUX NET E.A.S., PY · PeeringDB

3IPv4 routes 66.7% RPKI valid · 33.3% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

0No ROA 2 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS64179, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS64179, 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.


96.126.162.0/23	Invalid: origin	Other origin only	2 0%low visibility	2
206.62.119.0/24	Valid	Nonecovered by 206.62.116.0/22	669 99%	67
2803:8930::/32	Valid	RIR databaseLACNIC, RADB	630 99%	67
206.62.116.0/22	Valid	RIR databaseARIN	123 18%	44

96.126.162.0/23

Invalid: origin

Other origin only

2 0%low visibility

206.62.119.0/24

Valid

Nonecovered by 206.62.116.0/22

669 99%

2803:8930::/32

Valid

RIR databaseLACNIC, RADB

630 99%

206.62.116.0/22

Valid

RIR databaseARIN

123 18%

AS-SET

AS64179'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 3 are in fix.csv.

ROA: origin1
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	96.126.162.0/23	ROAs covering it name AS3561, not AS64179. If AS64179 should announce it, add a ROA for AS64179.	2 of 673
Route object: none	96.126.162.0/23	Route objects for it name AS3561. Add a route object with origin AS64179 in the RIR database for the space.	2 of 673
Route object: none	206.62.119.0/24	No route object for it. A route object for 206.62.116.0/22 with origin AS64179 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64179 in the RIR database for the space.	669 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

96.126.162.0/23

ROAs covering it name AS3561, not AS64179. If AS64179 should announce it, add a ROA for AS64179.

2 of 673

Route object: none

96.126.162.0/23

Route objects for it name AS3561. Add a route object with origin AS64179 in the RIR database for the space.

2 of 673

Route object: none

206.62.119.0/24

No route object for it. A route object for 206.62.116.0/22 with origin AS64179 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64179 in the RIR database for the space.

669 of 673

Route objects not announced

Every route object with origin AS64179 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.