BACKBONE.direct
Cluster stats
Netblocks12
Cluster ID193389638
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.18.236.125/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
178.18.237.60/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
185.1.160.16/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
185.1.240.52/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
185.1.240.121/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
193.192.12.13/32 BACKBONE.direct PEERINGDB ASSIGNED ● high
2001:7f8:10f::c6e5:16/128 BACKBONE.direct PEERINGDB ASSIGNED ● high
2001:7f8:12a::52/128 BACKBONE.direct PEERINGDB ASSIGNED ● high
2001:7f8:12a::121/128 BACKBONE.direct PEERINGDB ASSIGNED ● high
2001:7f8:130::c6e5:1/128 BACKBONE.direct PEERINGDB ASSIGNED ● high
2a03:5f80:4:2::236:125/128 BACKBONE.direct PEERINGDB ASSIGNED ● high
2a03:5f80:4:2::237:60/128 BACKBONE.direct PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (10 of 12)
No discrepancies found among checked blocks.

NIC Handles

AS50917