Data as of Nov 16, 2026

213.135.131.0/24

20 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Always-on exits
2
10% of its exits
Providers
56
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PSBProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • TalorData
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.135.96.0 - 213.135.159.25516,384RU-RTK-20000218PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 1, 2011abuse@rt.ru
└ 213.135.128.0/198,192MACROREGIONAL_CENTERPJSC Rostelecom, Tambov branchASSIGNED PADec 20, 2024abuse@rt.ru
via RU-RTK-20000218

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 213.135.128.0/19

213.135.128.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1