Data as of Nov 10, 2026

2.60.0.0/14

9 anonymizer addresses · <0.01% · VPN

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
47,441
18% of its addresses · listed by providers
Always-on exits
542
1.1% of its exits
Spread
944 of 1,024
/24s with at least one exit
Providers
128
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
record created Oct 8, 2010
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Aug 2016 · 10.2 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 2.60.0.0/14/24s
VPN GateUniversity of Tsukuba
9<0.01%
9

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

2.60.0.0/14

From the registry to its use

  1. Oct 8, 2010
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    2.60.0.0/14
  2. Jan 1, 2011– Jun 15, 2016
    Announced
    AS41440 PJSC Rostelecom
  3. Jun 22, 2016– Jun 27, 2016
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  4. Aug 15, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  5. Sep 20, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  6. Apr 3, 2025
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
    2.63.198.0/23
  7. today
    Used
    VPN Gate
    VPN

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

Arrived
PrefixOriginTypeAnonymizer addressesOperatorProxy exitsHolderRPKI
2.60.0.0/16
since Dec 2015
AS12389Residential10,721
41 always on
PJSC Rostelecom
2.60.0.0/18
since Jul 2020
AS12389Residential3,038PJSC Rostelecom
2.60.64.0/19
since Jul 2020
AS12389Residential1,458
2 always on
PJSC Rostelecom
2.60.96.0/20
since Jul 2020
AS12389Residential805PJSC Rostelecom
via OJSC "Sibirtelecom"
2.60.112.0/20
since Mar 2024
AS12389Residential56
30 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
2.60.128.0/19
since Jul 2020
AS12389Residential1,508
6 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
2.60.143.0/24
since Mar 2024
AS12389Residential14
6 always on
PJSC Rostelecom
2.60.160.0/19
since Jul 2020
AS12389Residential1,499PJSC Rostelecom
2.60.192.0/19
since Jul 2020
AS12389Residential1,541PJSC Rostelecom
via OJSC "Sibirtelecom"
2.60.224.0/20
since Jul 2020
AS12389Residential799
1 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
2.60.240.0/20
since Mar 2025
AS12389Residential17
2 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
2.61.0.0/16
since Dec 2014
AS12389Residential3<0.01%VPNVPN servicesoperated by VPN Gate16,324
2 always on
PJSC Rostelecom
2.62.0.0/16
since Feb 2018
AS12389Residential2<0.01%VPNVPN servicesoperated by VPN Gate10,035
2 always on
PJSC Rostelecom
2.62.0.0/17
since Feb 2016
AS12389Residential3,984PJSC Rostelecom
2.63.0.0/17
since Mar 2016
AS12389Residential6,132
3 always on
PJSC Rostelecom
2.63.0.0/18
since Mar 2016
AS12389Residential1<0.01%VPNVPN servicesoperated by VPN Gate3,203
2 always on
PJSC Rostelecom
2.63.64.0/18
since Mar 2016
AS12389Residential2,929
1 always on
PJSC Rostelecom
2.63.134.0/24
since Mar 2025
AS12389ResidentialPJSC Rostelecom
2.63.135.0/24
since Mar 2025
AS12389ResidentialPJSC Rostelecom
2.63.136.0/24
since Mar 2025
AS12389Residential2PJSC Rostelecom
2.63.144.0/20
since Jul 2022
AS201776Residential24
2 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.158.0/24
since Oct 10, 2026
AS201776Residential2PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.159.0/24
since Oct 10, 2026
AS201776Residential3PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.160.0/24
since Mar 2025
AS12389ResidentialPJSC Rostelecom
2.63.161.0/24
since Mar 2025
AS12389Residential2PJSC Rostelecom
2.63.162.0/24
since Mar 2025
AS12389Residential1PJSC Rostelecom
2.63.163.0/24
since Mar 2025
AS12389Residential2PJSC Rostelecom
2.63.170.0/24
since Mar 2024
AS57580Business1PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.174.0/24
since Mar 2024
AS12389Residential1PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.176.0/20
since Dec 2021
AS201776Residential1,593
47 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.176.0/24
since May 2026
AS201776Residential256
12 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.180.0/22
since May 2026
AS201776Residential10.10%VPNVPN servicesoperated by VPN Gate1,024
25 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.184.0/24
since May 2026
AS201776Residential256PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.192.0/24
since Mar 2022
AS48421ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.200.0/23
since Jul 2024
AS12389Residential511
406 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.200.0/24
since Jul 2024
AS12389Residential10.39%VPNVPN servicesoperated by VPN Gate255
202 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.201.0/24
since Jul 2024
AS12389Residential10.39%VPNVPN servicesoperated by VPN Gate256
204 always on
PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.204.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.205.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.213.0/24
since Mar 2025
AS12389Residential2PJSC Rostelecom
2.63.214.0/24
since Mar 2025
AS12389Residential3PJSC Rostelecom
2.63.220.0/24
since Mar 2025
AS12389ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.221.0/24
since Mar 2025
AS12389Residential3PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.222.0/24
since Mar 2025
AS12389Residential1PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.223.0/24
since Mar 2025
AS12389Residential1PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.224.0/20
since Jul 2022
AS201776Residential553
5 always on
PJSC Rostelecom
2.63.225.0/24
since Oct 2025
AS201776ResidentialPJSC Rostelecom
2.63.231.0/24
since May 2026
AS201776Residential256
1 always on
PJSC Rostelecom
2.63.232.0/24
since May 2026
AS201776Residential256PJSC Rostelecom
2.63.240.0/24
since Mar 2025
AS12389ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.241.0/24
since Apr 2026
AS12389Residential2PJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.242.0/24
since Mar 2025
AS12389Residential3
2 always on
PJSC Rostelecom
2.63.243.0/24
since Mar 2025
AS12389Residential1PJSC Rostelecom
2.63.244.0/24
since May 2025
AS12389ResidentialPJSC Rostelecom
2.63.253.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
via JSC Rostelecom . Rostov
2.63.254.0/24
since Apr 2024
AS12389Residential2PJSC Rostelecom
via JSC Rostelecom . Rostov

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.60.0.0/14262,144RU-RTK-20101008PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 8, 2010abuse@rt.ru
└ 2.60.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-RTK-20101008
└ 2.60.0.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 29, 2010abuse@rt.ru
via RU-SIBNET
└ 2.60.32.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 29, 2010abuse@rt.ru
via RU-SIBNET
└ 2.60.64.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 29, 2010abuse@rt.ru
via RU-SIBNET
└ 2.60.96.0/198,192WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAMay 30, 2023abuse@rt.ru
via RU-SIBNET
└ 2.60.112.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.113.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.114.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.115.0/24256WEBSTREAMunknownSUB-ALLOCATED PAMay 30, 2023abuse@rt.ru
via WEBSTREAM
└ 2.60.116.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.117.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.118.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.119.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.120.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.121.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.122.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.123.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.124.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.125.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.126.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.127.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.128.0/198,192WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-SIBNET
└ 2.60.143.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.160.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.60.192.0/1816,384WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-SIBNET
└ 2.60.240.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.241.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.242.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.243.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.244.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.245.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.246.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.247.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.248.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.249.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.250.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.251.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.252.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.253.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.254.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.255.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.61.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-RTK-20101008
└ 2.61.0.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.32.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.64.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.96.0/204,096WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.112.0/212,048WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.120.0/212,048WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAFeb 1, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.128.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-SIBNET
└ 2.61.160.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.61.192.0/1816,384WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.62.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PAMar 29, 2011abuse@rt.ru
via RU-RTK-20101008
└ 2.62.0.0 - 2.62.47.25512,288WEBSTREAMOJSC "Rostelecom"ASSIGNED PAJul 5, 2012abuse@rt.ru
via RU-SIBNET
└ 2.62.48.0/204,096WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAApr 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.62.64.0/1816,384WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-SIBNET
└ 2.62.112.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.113.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.114.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.115.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.116.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.117.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.118.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.119.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.120.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.121.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.122.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.123.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.124.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.125.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.126.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.127.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.62.128.0/1732,768RU-SIBNETunknownLIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-SIBNET
└ 2.62.128.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-SIBNET
└ 2.62.160.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.62.192.0/1816,384WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.63.0.0/1732,768RU-SIBNETunknownLIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-RTK-20101008
└ 2.63.0.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-SIBNET
└ 2.63.32.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.63.64.0/1816,384WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-SIBNET
└ 2.63.128.0/1732,768Rostelecom_netJSC Rostelecom . RostovSUB-ALLOCATED PAOct 7, 2021abuse@rt.ru
via RU-RTK-20101008
└ 2.63.132.0 - 2.63.132.67Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.132.7 - 2.63.132.137Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.132.14/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.132.16 - 2.63.132.227Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.132.23 - 2.63.132.297Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.132.30/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.133.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 27, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.134.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.135.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.136.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.137.224 - 2.63.137.2307Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.137.231 - 2.63.137.2377Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.137.238/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.137.240 - 2.63.137.2467Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.137.247 - 2.63.137.2537Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.137.254/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.0 - 2.63.138.67Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.7 - 2.63.138.137Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.14/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.16 - 2.63.138.227Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.23 - 2.63.138.297Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.30/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.32 - 2.63.138.387Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.39 - 2.63.138.457Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.46/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.48 - 2.63.138.547Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.55 - 2.63.138.617Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.62/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.64 - 2.63.138.707Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.71 - 2.63.138.777Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.78/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.80 - 2.63.138.867Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.87 - 2.63.138.937Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.94/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.96 - 2.63.138.1027Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.103 - 2.63.138.1097Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.110/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.112 - 2.63.138.1187Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.119 - 2.63.138.1257Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.126/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.128 - 2.63.138.1347Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.135 - 2.63.138.1417Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.142/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.144 - 2.63.138.1507Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.151 - 2.63.138.1577Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.158/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.160 - 2.63.138.1667Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.167 - 2.63.138.1737Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.174/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.176 - 2.63.138.1827Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.183 - 2.63.138.1897Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.190/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.192 - 2.63.138.1987Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.199 - 2.63.138.2057Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.206/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.208 - 2.63.138.2147Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.215 - 2.63.138.2217Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.222/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.224 - 2.63.138.2307Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.231 - 2.63.138.2377Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.238/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.240 - 2.63.138.2467Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.247 - 2.63.138.2537Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.138.254/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.0 - 2.63.139.67Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.7 - 2.63.139.137Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.14/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.16 - 2.63.139.227Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.23 - 2.63.139.297Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.30/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.32 - 2.63.139.387Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.39 - 2.63.139.457Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.46/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.48 - 2.63.139.547Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.55 - 2.63.139.617Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.62/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.64 - 2.63.139.707Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.71 - 2.63.139.777Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.78/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.80 - 2.63.139.867Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.87 - 2.63.139.937Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.94/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.96 - 2.63.139.1027Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.103 - 2.63.139.1097Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.110/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.112 - 2.63.139.1187Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.119 - 2.63.139.1257Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.126/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.128 - 2.63.139.1347Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.135 - 2.63.139.1417Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.142/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.144 - 2.63.139.1507Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.151 - 2.63.139.1577Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.158/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.160 - 2.63.139.1667Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.167 - 2.63.139.1737Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.174/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.176 - 2.63.139.1827Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.183 - 2.63.139.1897Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.190/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 21, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.192 - 2.63.139.1987Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.199 - 2.63.139.2057Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.206/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.208 - 2.63.139.2147Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.215 - 2.63.139.2217Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.139.222/312Rostelecom_netunknownSUB-ALLOCATED PAFeb 26, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.140.0/221,024RezervunknownASSIGNED PADec 5, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.144.0/204,096Miranda_Media_netunknownASSIGNED PAOct 7, 2021abuse@rt.ru
via Rostelecom_net
└ 2.63.160.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.161.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.162.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.163.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.168.0/2664Rostelecom_netunknownASSIGNED PAMar 2, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.169.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 2.63.170.0/24256Rostelecom-clientunknownASSIGNED PAMar 16, 2022abuse@rt.ru
via Rostelecom_net
└ 2.63.176.0/204,096Miranda_Media_netunknownASSIGNED PADec 22, 2021abuse@rt.ru
via Rostelecom_net
└ 2.63.196.0/24256Rostelecom_netunknownAGGREGATED-BY-LIRNov 9, 2026abuse@rt.ru
via Rostelecom_net
└ 2.63.204.0/24256MNCAP_AssignedunknownASSIGNED PANov 14, 2023abuse@rt.ru
via Rostelecom_net
└ 2.63.211.0/24256Rostelecom_netunknownSUB-ALLOCATED PAMay 23, 2024abuse@rt.ru
via Rostelecom_net
└ 2.63.213.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 25, 2025abuse@rt.ru
via Rostelecom_net
← Previous1–200 of 216 · page 1 of 2Next →

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

262,144 addresses
TypeAddressesShareRanges
Residential261,863>99%82
Business2720.10%2
VPNanonymizer9<0.01%9

Network & registry

Origin network

AS12389

RU
Name
PJSC Rostelecom
Type
Internet provider
Registered
Jul 1, 2005
Domain
rt.ru
Website
www.company.rt.ru/en/
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed