UNICAMP

Data as of 2026-08-16
Handle
Cluster stats
Netblocks8
IPv6 4 prefixes (largest 2001:12f8:0:11::43/128)
All fragments 11 blocks across 2 clusters
Cluster ID222462931
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 · report an issue

Footprint over time

8 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-08-16

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.211.204/32 UNICAMP PEERINGDB ASSIGNED ● high
187.16.217.85/32 UNICAMP PEERINGDB ASSIGNED ● high
200.192.108.43/32 UNICAMP PEERINGDB ASSIGNED ● high
200.192.108.63/32 UNICAMP PEERINGDB ASSIGNED ● high
2001:12f8::211:204/128 UNICAMP PEERINGDB ASSIGNED ● high
2001:12f8::217:85/128 UNICAMP PEERINGDB ASSIGNED ● high
2001:12f8:0:11::43/128 UNICAMP PEERINGDB ASSIGNED ● high
2001:12f8:0:11::63/128 UNICAMP PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

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

AS53187