Six Degrees - Datahop

BGP inherited
Cluster stats
Netblocks8
All fragments 140 blocks across 4 clusters
Cluster ID211394477
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.81.21/32 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
185.1.104.71/32 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
195.66.225.32/32 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
195.66.244.13/32 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
2001:7f8:4::1afc:1/128 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
2001:7f8:4:2::1afc:1/128 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
2001:7f8:17::1afc:1/128 Six Degrees - Datahop PEERINGDB ASSIGNED ● high
2001:7f8:be::6908:1/128 Six Degrees - Datahop PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Six Degrees” — 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS6908