Balticom

Registry
Cluster stats
Netblocks10
All fragments 16 blocks across 7 clusters
Cluster ID205153272
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.241.206.94/32 Balticom PEERINGDB ASSIGNED ● high
185.1.236.30/32 Balticom PEERINGDB ASSIGNED ● high
185.1.236.150/32 Balticom PEERINGDB ASSIGNED ● high
195.246.227.158/32 Balticom PEERINGDB ASSIGNED ● high
2001:7f8:16::2:4651:1/128 Balticom PEERINGDB ASSIGNED ● high
2001:7f8:126::30/128 Balticom PEERINGDB ASSIGNED ● high
2001:7f8:126::150/128 Balticom PEERINGDB ASSIGNED ● high
2001:1ab8:8486::94/128 Balticom PEERINGDB ASSIGNED ● high
185.141.52.0/23 BALTICOM-Net RIPE ASSIGNED PA ● low
185.141.54.0/23 BALTICOM-Net RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS24651 DUMY-RIPE DUMY-RIPE LVBALTICOM-MNT VB96178-MNT