DATA CENTER PROVIDER

BGP inherited
Cluster stats
Netblocks4
All fragments 158 blocks across 35 clusters
Cluster ID213188912
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

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
49.213.56.102/32 DATA CENTER PROVIDER PEERINGDB ASSIGNED ● high
103.162.254.176/32 DATA CENTER PROVIDER PEERINGDB ASSIGNED ● high
2001:df5:7880:0:2:56e5:0:1/128 DATA CENTER PROVIDER PEERINGDB ASSIGNED ● high
2001:df6:480:0:2:56e5:0:1/128 DATA CENTER PROVIDER PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (3 of 4)
No discrepancies found among checked blocks.

NIC Handles

AS153317