ZUX NET E.A.S.

BGP inherited
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID207720385
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
9 -2 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-13

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.201.32/32 ZUX PEERINGDB ASSIGNED ● high
187.16.204.17/32 ZUX PEERINGDB ASSIGNED ● high
187.16.218.123/32 ZUX PEERINGDB ASSIGNED ● high
187.16.218.239/32 ZUX PEERINGDB ASSIGNED ● high
2001:12f8::218:123/128 ZUX PEERINGDB ASSIGNED ● high
2001:12f8::218:239/128 ZUX PEERINGDB ASSIGNED ● high
2001:12f8:0:24::32/128 ZUX PEERINGDB ASSIGNED ● high
2001:12f8:0:27::17/128 ZUX PEERINGDB ASSIGNED ● high
2803:8930::/32 ZUX NET E.A.S. ARIN ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to ZUX NET E.A.S. but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2803:8930::/32 /32 authorized for AS64179 — AS64179

NIC Handles

AS271203 CBM38 CBM38 CBM38 PY-ZUNE-LACNIC