CIBER-TATAC

BGP inherited
Cluster stats
Netblocks9 · 1,695 IPv4 addresses
Cluster ID209889646
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.231.37.0/25 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.38.128/27 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.38.224/27 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.39.0/24 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.96.0/22 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.103.32/27 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.103.64/26 CIBER-TATAC RIPE ASSIGNED PA ● low
80.231.103.128/25 CIBER-TATAC RIPE ASSIGNED PA ● low
195.219.49.128/29 CIBER-TATAC RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS8297-MNT DUMY-RIPE DUMY-RIPE