LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

84.17.0.0/19

7 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS8359
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
7
0.09% of its addresses · 30 days
Spread
5 of 32
/24s with at least one exit
Providers
31
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

807 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.17.1.0/2402
84.17.15.0/2402
84.17.4.0/2401
84.17.14.0/2401
84.17.27.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NovProxy
  • NovaProxy
  • PROXYFALL
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PrivateProxy
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RolaProxy
  • VantageProxies
  • YumiProxy

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
84.17.0.0/198,192RU-MTU-20040722MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 22, 2004abuse@mtu.ru
└ 84.17.0.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 15, 2005abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.1.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAAug 30, 2005abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.2.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.3.0/24256GIPROPRIBOR-NETGipropribor networkASSIGNED PAMar 27, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.5.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAMay 13, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.6.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAMay 13, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.7.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PADec 19, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.8.0/221,024MTS-SPB-4MTS leased lines clientsASSIGNED PAMay 13, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.12.0/221,024MTS-SPB-2MTS leased lines clientsASSIGNED PAApr 2, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.16.0/212,048LANCK-LL3lanck.net leased lines clientsASSIGNED PAApr 3, 2008abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.26.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.27.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.28.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.29.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.30.0/24256MTS-SPBRussia, Saint-PetersburgASSIGNED PAJun 29, 2006abuse@mtu.ru
via RU-MTU-20040722
└ 84.17.31.0 - 84.17.31.128129ETSExpress TeleserviceASSIGNED PASep 27, 2004abuse@mtu.ru
via RU-MTU-20040722

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

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2013 · 14 yr
Origin networks
2
Last change of origin
May 2013
Recorded history

History

Handoffs
1