Data as of Nov 7, 2026

82.196.128.0/19

88 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
89% of it

Residential-proxy exits

Proxy exits
88
1.1% of its addresses · 30 days
Always-on exits
12
14% of its exits
Spread
20 of 32
/24s with at least one exit
Providers
84
selling exits here
Oct 8, 2026 – Nov 6, 2026

Exits seen per day

26K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYWING_BASIC
  • PacketStream
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare

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
82.196.128.0/198,192RU-RTK-20031031PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 5, 2024abuse@rt.ru
└ 82.196.128.0/24256CTCS-M10unknownASSIGNED PAMay 25, 2005abuse@rt.ru
via RU-RTK-20031031
└ 82.196.129.0/24256CTCS-M9Centertelecom ServiceASSIGNED PAMay 20, 2005abuse@rt.ru
via RU-RTK-20031031
└ 82.196.130.0/2732VOENTELECOMFGUP "Voentelecom"ASSIGNED PAJun 29, 2005abuse@rt.ru
via RU-RTK-20031031
└ 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
└ 82.196.132.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.132.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.133.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.133.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.134.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.134.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.135.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.135.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.136.0/24256RTL-VRN-PRFXOJSC "RTLabs"ASSIGNED PAApr 5, 2016abuse@rt.ru
via RU-RTK-20031031
└ 82.196.137.0/24256RTL-VRN-PRFXOJSC "RTLabs"ASSIGNED PAJul 1, 2005abuse@rt.ru
via RU-RTK-20031031
└ 82.196.138.0/24256RTL-RUM-PRFXOJSC "RTLabs"ASSIGNED PASep 9, 2004abuse@rt.ru
via RU-RTK-20031031
└ 82.196.139.0/24256RTL-RUM-PRFXOJSC "RTLabs"ASSIGNED PADec 7, 2016abuse@rt.ru
via RU-RTK-20031031
└ 82.196.140.0/24256CTCSCentertelecom ServiceASSIGNED PASep 9, 2004abuse@rt.ru
via RU-RTK-20031031
└ 82.196.141.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.141.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.142.0/24256CTCSCentertelecom ServiceASSIGNED PASep 9, 2004abuse@rt.ru
via RU-RTK-20031031
└ 82.196.143.0/24256RU-RTK-20031031PJSC Rostelecom (ORG-JR8-RIPE) · RUSUB-ALLOCATED PADec 12, 2025abuse@rt.ru
└ 82.196.143.0/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.143.64/2664CTCSCentertelecom ServiceASSIGNED PADec 18, 2003abuse@rt.ru
via RU-RTK-20031031
└ 82.196.144.0/24256CTCS-M10Centertelecom ServiceASSIGNED PAFeb 5, 2026abuse@rt.ru
via RU-RTK-20031031
└ 82.196.145.0/24256RT-NETunknownASSIGNED PAJan 13, 2026abuse@rt.ru
via RU-RTK-20031031
└ 82.196.152.0/221,024RTL-OFFCES-PRFXOJSC "RTLabs"ASSIGNED PASep 9, 2004abuse@rt.ru
via RU-RTK-20031031
└ 82.196.156.0/24256NN-JSC-BryansktelBryansktel JSCASSIGNED PAOct 6, 2005abuse@rt.ru
via RU-RTK-20031031
└ 82.196.157.0/24256RTK-NETunknownASSIGNED PAJul 24, 2026abuse@rt.ru
via RU-RTK-20031031
└ 82.196.158.0/24256CTCS-TECH-LOOPBACKS-1Centertelecom Service Corporate NetworkASSIGNED PAMar 14, 2006abuse@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

8,192 addresses
TypeAddressesShareRanges
Residential7,26489%9
Business92811%15

Network & registry

Origin network

AS12389

RU
Name
PJSC Rostelecom
Type
Internet provider
Registered
Jul 1, 2005
Domain
rt.ru
Website
www.company.rt.ru/en/
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed