Data as of Nov 20, 2026

82.209.88.0/24

5 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
34
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.209.64.0/1816,384RU-MTU-20090929MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PASep 29, 2009abuse@mtu.ru
└ 82.209.64.0/198,192PTCOMMNETMTS PenzaASSIGNED PAJun 17, 2010abuse@mtu.ru
via RU-MTU-20090929

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

Routing timeline

Who has announced 82.209.64.0/18

82.209.64.0/18

Routing history

Pattern
Stable
First seen
Oct 2009
Current origin since
Oct 2009 · 17 yr
Origin networks
1