FICOM PERU
Cluster stats
Netblocks16
All fragments 38 blocks across 2 clusters
Cluster ID193392319
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 (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.24.246/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.26.239/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.28.246/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.30.247/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.31.107/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.36.243/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.68.38.248/32 FICOM PERU PEERINGDB ASSIGNED ● high
45.183.47.240/32 FICOM PERU PEERINGDB ASSIGNED ● high
2801:1a:5800:140::d8/128 FICOM PERU PEERINGDB ASSIGNED ● high
2801:1a:5800:141::77/128 FICOM PERU PEERINGDB ASSIGNED ● high
2801:1a:5800:142::68/128 FICOM PERU PEERINGDB ASSIGNED ● high
2801:1a:5800:148::5b/128 FICOM PERU PEERINGDB ASSIGNED ● high
2801:1a:5800:149::75/128 FICOM PERU PEERINGDB ASSIGNED ● high
2803:cd60:57ff::a7/128 FICOM PERU PEERINGDB ASSIGNED ● high
2803:cd60:6411:5::d0/128 FICOM PERU PEERINGDB ASSIGNED ● high
2803:cd60:6414:7::d1/128 FICOM PERU PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS273976