UNICA TELECOM

BGP inherited
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID213186201
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

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-13
2026-07-13 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.74.164/32 UNICA TELECOM PEERINGDB ASSIGNED ● high
45.68.82.168/32 UNICA TELECOM PEERINGDB ASSIGNED ● high
187.16.213.71/32 UNICA TELECOM PEERINGDB ASSIGNED ● high
200.219.147.115/32 UNICA TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::213:71/128 UNICA TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:2::54:168/128 UNICA TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:164/128 UNICA TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:10::115/128 UNICA TELECOM PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

AS273568