Data as of Nov 16, 2026

213.178.32.0/21

113 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
113
5.5% of its addresses · 30 days
Always-on exits
3
2.7% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
104
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

18K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RolaProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
213.178.32.0/198,192RU-RTK-20080117PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 14, 2022abuse@rt.ru
└ 213.178.33.160/2732AIST-TAUAIST ISP, Client TAUASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.34.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 20, 2010abuse@rt.ru
via RU-RTK-20080117
└ 213.178.37.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.38.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.39.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2010
Current origin since
Sep 2010 · 16 yr
Origin networks
1