TR-AATELEKOM

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks14
Also registered under this name 15 netblocks across 2 separate records
Record ID242293000
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.254.50.152/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.51.32/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.52.224/28 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.52.240/28 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.160/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.168/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.176/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.184/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.192/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.200/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.208/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.216/29 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.224/28 TR-AATELEKOM RIPE ASSIGNED PA ● low
46.254.53.240/28 TR-AATELEKOM RIPE ASSIGNED PA ● low

Footprint over time

2 weekly snapshots · JSON
14 0 netblocks since 2026-09-06
2026-09-06 peak 14 2026-09-13

Network trust

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

NIC Handles

AATELEKOM-MNT DUMY-RIPE DUMY-RIPE