Data as of Nov 13, 2026

84.17.240.0/20

14 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
81% of it

Residential-proxy exits

Proxy exits
14
0.34% of its addresses · 30 days
Always-on exits
1
7.1% of its exits
Spread
7 of 16
/24s with at least one exit
Providers
26
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.2K observations
  • Residential
  • Business

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BottingTools
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • HELODATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • LudaxProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • StrikeProxy
  • TrueProxies
  • VantageProxies
  • YumiProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
84.17.246.0/24
since Mar 2019
AS197023ResidentialMTS PJSC
84.17.248.0/24
since Dec 2013
AS16256Residential3MTS PJSC
84.17.249.0/24
since Apr 2022
AS16256Residential3MTS PJSC
84.17.252.0/24
since May 2017
AS62461Business3MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.17.224.0/198,192RU-MTU-20040804MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAAug 4, 2004abuse@mtu.ru
└ 84.17.240.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.241.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.242.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.243.0 - 84.17.244.255512ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.245.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.246.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.247.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.248.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.249.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.250.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAMay 19, 2022abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.251.0/24256b2bhub-orel-01unknownASSIGNED PAMay 19, 2022abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.252.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.253.0/24256ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804
└ 84.17.254.0/23512RECOM-GPRSMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804

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

4,096 addresses
TypeAddressesShareRanges
Residential3,32881%7
Mobile51213%1
Business2566.3%1

Network & registry

Routing timeline

Who has announced 84.17.224.0/19

84.17.224.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1