217.23.16.0/20

AS12389 · PJSC Rostelecom

Summary

BGP Prefix
217.23.16.0/20
Domain
rt.ru
Registry
RIPE_NCC
ID
RU-RTK-20040120
Allocation
assigned on 2004-01-20

WHOIS

Network
217.23.16.0/20
Name
PJSC Rostelecom
Net name
RU-RTK-20040120
Organization type
allocated pa
Registry
RIPE_NCC
Country
RU
Abuse contact
PJSC Rostelecom Technical Team
Abuse email
abuse@rt.ru

Overlapping Ranges

RangeSourceHolderCountry
217.23.16.0/20BGP routeAS12389 PJSC Rostelecom—
217.23.16.0/20WHOIS (RIPE_NCC)PJSC RostelecomRU
217.23.16.0/20RIPE_NCC assigned—RU
217.23.16.0/24WHOIS (RIPE_NCC)Nizhegorodsky TeleSrvice common blockRU
217.23.17.0/24WHOIS (RIPE_NCC)Nizhegorodsky TeleSrvice common blockRU
217.23.18.0/24WHOIS (RIPE_NCC)Nizhegorodsky TeleSrvice common blockRU
217.23.19.0/24WHOIS (RIPE_NCC)Nizhegorodsky TeleSrvice common blockRU
217.23.20.0/24WHOIS (RIPE_NCC)Nizhegorodsky TeleSrvice common blockRU
217.23.31.0/24WHOIS (RIPE_NCC)Public Enterprise Volga River Communication Company blockRU
217.23.23.192/26WHOIS (RIPE_NCC)Net for clients Nizhegorodsky TeleservisRU
217.23.28.64/26WHOIS (RIPE_NCC)MACCENTER-NETRU
217.23.28.128/26WHOIS (RIPE_NCC)MACCENTER-NETRU
217.23.28.192/26WHOIS (RIPE_NCC)NNTS-NETRU
217.23.29.192/26WHOIS (RIPE_NCC)Node in ATS-66, COMMON BLOCKRU
217.23.21.0/27WHOIS (RIPE_NCC)Node in ATS-41, COMMON-BLOCKRU
217.23.21.32/27WHOIS (RIPE_NCC)Node in NMGTS, COMMON-BLOCKRU
217.23.21.96/27WHOIS (RIPE_NCC)Node in Airport, COMMON-BLOCKRU
217.23.21.128/27WHOIS (RIPE_NCC)Node in VolgoVyatka, COMMON-BLOCKRU
217.23.21.160/27WHOIS (RIPE_NCC)Node in ATS23, COMMON BLOCKRU
217.23.21.224/27WHOIS (RIPE_NCC)Node in ATS-36, COMMON BLOCKRU
217.23.22.0/27WHOIS (RIPE_NCC)Node in ATS-23, COMMON BLOCKRU
217.23.22.32/27WHOIS (RIPE_NCC)Node in NMGTS, COMMON BLOCK (PPPoE)RU
217.23.22.64/27WHOIS (RIPE_NCC)Node in NMGTS, COMMON BLOCK (PPPoE)RU
217.23.22.128/27WHOIS (RIPE_NCC)Node in ATS-42, COMMON BLOCKRU
217.23.22.160/27WHOIS (RIPE_NCC)Node in Airport, COMMON BLOCKRU
217.23.22.224/27WHOIS (RIPE_NCC)Net for IPVPN over VolgaTelecomRU
217.23.23.0/27WHOIS (RIPE_NCC)Net of ZMZRU
217.23.23.32/27WHOIS (RIPE_NCC)Net of Airport in Airport siteRU
217.23.23.64/27WHOIS (RIPE_NCC)Node in NMTS, COMMON BLOCKRU
217.23.23.96/27WHOIS (RIPE_NCC)Node in NMTS, COMMON BLOCKRU
217.23.23.128/27WHOIS (RIPE_NCC)Node in ATS-24, COMMON BLOCKRU
217.23.23.160/27WHOIS (RIPE_NCC)Net for clients Nizhegorodsky TeleservisRU
217.23.24.0/27WHOIS (RIPE_NCC)Node in ATS-36, COMMON BLOCKRU
217.23.24.32/27WHOIS (RIPE_NCC)Node in ZKPD4, COMMON BLOCKRU
217.23.24.64/27WHOIS (RIPE_NCC)Node in VolgoVyatka, COMMON BLOCKRU
217.23.24.96/27WHOIS (RIPE_NCC)Node in Fedoseenko, COMMON BLOCKRU
217.23.24.128/27WHOIS (RIPE_NCC)Node in ATS-52, COMMON BLOCKRU
217.23.24.160/27WHOIS (RIPE_NCC)Node in ATS-66, COMMON BLOCKRU
217.23.24.224/27WHOIS (RIPE_NCC)Node in ZKPD4, COMMON BLOCKRU
217.23.25.0/27WHOIS (RIPE_NCC)Node in ATS-66, COMMON BLOCKRU
217.23.25.32/27WHOIS (RIPE_NCC)Node in VolgoVyatka, COMMON BLOCKRU
217.23.25.64/27WHOIS (RIPE_NCC)Node in Kuzbasskaya, COMMON BLOCKRU
217.23.25.96/27WHOIS (RIPE_NCC)Node in Fedoseenko, COMMON BLOCKRU
217.23.25.160/27WHOIS (RIPE_NCC)Node in ATS-66, COMMON BLOCKRU
217.23.25.192/27WHOIS (RIPE_NCC)Node in hotel Oka, COMMON BLOCKRU
217.23.25.224/27WHOIS (RIPE_NCC)Node in ZKPD4, COMMON BLOCKRU
217.23.26.0/27WHOIS (RIPE_NCC)Node in VolgoVyatka, COMMON BLOCKRU
217.23.26.32/27WHOIS (RIPE_NCC)Node in hotel Oka, COMMON BLOCKRU
217.23.26.64/27WHOIS (RIPE_NCC)Node in ATS-24, COMMON BLOCKRU
217.23.26.96/27WHOIS (RIPE_NCC)Node in ATS-66, COMMON BLOCKRU
217.23.26.160/27WHOIS (RIPE_NCC)Node in ATS-24, COMMON BLOCKRU
217.23.26.192/27WHOIS (RIPE_NCC)Node in NMGTS, COMMON BLOCKRU

Nearby Ranges