Data as of Nov 20, 2026

82.196.134.64/26

2 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
3.1% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
37
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

50 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.196.128.0/198,192RU-RTK-20031031PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 5, 2024abuse@rt.ru
└ 82.196.134.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031

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.196.128.0/19

82.196.128.0/19

Routing history

Pattern
Reactivated
First seen
May 2005
Current origin since
Oct 2025 · 1.1 yr
Origin networks
2
Last change of origin
Oct 2025
Recorded history

History

Handoffs
1