Transneft Telecom

Data as of 2026-10-18
BGP inherited
This organisation
Netblocks11
IPv6 4 prefixes (largest 2001:7f8:20:101::208:224/128)
Record ID250280857
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.44.187.28/32 Transneft Telecom PEERINGDB ASSIGNED ● high
185.1.152.78/32 Transneft Telecom PEERINGDB ASSIGNED ● high
185.232.60.120/32 Transneft Telecom PEERINGDB ASSIGNED ● high
193.106.112.57/32 Transneft Telecom PEERINGDB ASSIGNED ● high
193.232.87.40/32 Transneft Telecom PEERINGDB ASSIGNED ● high
195.208.208.224/32 Transneft Telecom PEERINGDB ASSIGNED ● high
2001:7f8:20:101::208:224/128 Transneft Telecom PEERINGDB ASSIGNED ● high
2001:7f8:20:401::87:40/128 Transneft Telecom PEERINGDB ASSIGNED ● high
2a00:1b30::57/128 Transneft Telecom PEERINGDB ASSIGNED ● high
2a0d:e180::60:120/128 Transneft Telecom PEERINGDB ASSIGNED ● high
84.204.75.20/30 TRANSNEFT-LAN RIPE ASSIGNED PA ● low

IPv6 ranges (4)

Footprint over time

17 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-10-18

Network trust

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

NIC Handles

AS60388 DUMY-RIPE DUMY-RIPE PSTAR-MNT