G3NS-CLIENT-WSH

BGP inherited
Cluster stats
Netblocks6
All fragments 615 blocks across 188 clusters
Cluster ID210215585
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.83.36.136/31 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low
45.145.31.246/31 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low
83.151.197.24/31 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low
185.33.211.108/30 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low
185.33.211.132/30 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low
194.15.49.30/31 G3NS-CLIENT-WSH RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “G3NS CLIENT” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 188 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

NIC Handles

DUMY-RIPE DUMY-RIPE G3NS-MNT