Data as of Nov 19, 2026

213.167.201.0/24

70 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
70
27% of its addresses · 30 days
Providers
88
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.167.192.0/198,192RU-RTK-20081121PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 21, 2008abuse@rt.ru
└ 213.167.192.0/204,096MACROREGIONAL_CENTEROJSC Rostelecom, Vladimir branchASSIGNED PANov 20, 2025abuse@rt.ru
via RU-RTK-20081121

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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
213.167.192.0/19AS12389/19RIPERPKI valid
IRR

Route objects on 213.167.192.0/19

OriginRegistryDescriptionMaintainerModified
AS12389 RIPERostelecom networksROSTELECOM-MNTOct 30, 2018