COMUNIDAD 3 PLAY

BGP inherited
Cluster stats
Netblocks6 · 1,276 IPv4 addresses
Cluster ID211074216
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
12 -1 netblocks since 2026-07-05
2026-07-05 peak 13 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.8.29/32 COMUNIDAD 3 PLAY PEERINGDB ASSIGNED ● high
2001:13c7:6001::29/128 COMUNIDAD 3 PLAY PEERINGDB ASSIGNED ● high
200.63.108.0/23 COMUNIDAD 3 PLAY BGP ANNOUNCED ● low
200.63.109.0/24 COMUNIDAD 3 PLAY BGP ANNOUNCED ● low
200.63.110.0/24 COMUNIDAD 3 PLAY BGP ANNOUNCED ● low
200.63.111.0/24 COMUNIDAD 3 PLAY BGP ANNOUNCED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (4)

These blocks are registered to COMUNIDAD 3 PLAY but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

200.63.108.0/23 /23 authorized for AS265804 — AS265804
200.63.109.0/24 /24 authorized for AS265804 — AS265804
200.63.110.0/24 /24 authorized for AS265804 — AS265804
200.63.111.0/24 /24 authorized for AS265804 — AS265804

NIC Handles

AS265804 AS265804