HOPUS

BGP inherited

Cluster stats

Netblocks	5
All fragments	40 blocks across 18 clusters
Cluster ID	205026851
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (5)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
37.77.34.1/32	Hopus	PEERINGDB	ASSIGNED	● high
2a02:e5c:1::2/128	Hopus	PEERINGDB	ASSIGNED	● high
85.118.38.128/28	HOPUS	RIPE	ASSIGNED PA	● low
2a02:e5c::/32	HOPUS	RIPE	ALLOCATED-BY-LIR	● low
2a02:2178:1001::/48	HOPUS	RIPE	ASSIGNED	● low

Possibly related to this organisation

what's this?

Same name family

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

HOPUS SAS 15 blocks
HOPUS-TH2 2 blocks
HOPUS-DC3OP2 2 blocks
HOPUS-PA3 2 blocks
HOPUS-SERVICES 2 blocks
HOPUS-CH 1 blocks
HOPUS-FR 1 blocks
HOPUS-NL 1 blocks

Combined view of all 18 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.

Intercos via HOPUS SAS sub-allocation
HOPUS-FR via HOPUS SAS sub-allocation
HOPUS-CH via HOPUS SAS sub-allocation
HOPUS-NL via HOPUS SAS sub-allocation
HOPUS-DE via HOPUS SAS sub-allocation
Advanced Services via HOPUS SAS sub-allocation
Net Tests via HOPUS SAS sub-allocation
Net Tests 2 via HOPUS SAS sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

AS44530 DUMY-RIPE DUMY-RIPE HOPUS-MNT