COMEZOLO

Handle
Cluster stats
Netblocks8
Registered in Japan (2) · Hong Kong (1) · Thailand (1)
All fragments 10 blocks across 2 clusters
Cluster ID213186261
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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
101.203.89.152/32 COMEZOLO PEERINGDB ASSIGNED ● high
103.127.88.23/32 COMEZOLO PEERINGDB ASSIGNED ● high
103.203.158.170/32 COMEZOLO PEERINGDB ASSIGNED ● high
103.231.152.179/32 COMEZOLO PEERINGDB ASSIGNED ● high
2001:de8:c::13:9836:1/128 COMEZOLO PEERINGDB ASSIGNED ● high
2001:df5:b800:bb00:0:13:9836:1/128 COMEZOLO PEERINGDB ASSIGNED ● high
2001:df7:6500:1:0:13:9836:1/128 COMEZOLO PEERINGDB ASSIGNED ● high
2403:c780:b800:bb00:0:13:9836:1/128 COMEZOLO PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

Network trust

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

NIC Handles

AS139836