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

82.209.85.0/24

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
2
33% of its exits
Providers
39
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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