Data as of Nov 10, 2026

82.196.131.0/24

11 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
50% of it

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Providers
31
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

316 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYWING_BASIC
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalData
  • 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.131.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.131.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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business12850%2
Residential12850%1

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.0 yr
Origin networks
2
Last change of origin
Oct 2025
Recorded history

History

Handoffs
1