VIPRINET-V6-RUGGEDVPN-HOMEOFFICES

Handle

Cluster stats

Netblocks	1
All fragments	5 blocks across 5 clusters
Cluster ID	206084438
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	RIR handle
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

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2a02:2980:4::/48	VIPRINET-V6-RUGGEDVPN-HOMEOFFICES	RIPE	ASSIGNED	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “VIPRINET V6” — 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.

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.

VIPRINET-OFFICE3 via 23M GmbH sub-allocation
VIPRINET-RUGGEDVPN-STAFF-TEST via 23M GmbH sub-allocation
VIPRINET-LAB via 23M GmbH sub-allocation
VIPRINET-EVENT-PIRATEPARTY via 23M GmbH sub-allocation
VIPRINET-TESTNET-2 sub-allocation
VIPRINET-V6-PUBLIC-SERVICES via 23M GmbH sub-allocation
VIPRINET-V6-VPN-HUBS via 23M GmbH sub-allocation
VIPRINET-V6-DEMOROUTERS via 23M GmbH sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

RPKI-inferred operator 23M GmbH

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE VIPRINET-MNT