Data as of Nov 12, 2026

87.253.0.0/19

1,949 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1,949
24% of its addresses · 30 days
Always-on exits
1
0.05% of its exits
Spread
31 of 32
/24s with at least one exit
Providers
110
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

105K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.253.0.0/20
since Jan 2008
AS13118Residential863
1 always on
PJSC Rostelecom
87.253.0.0/21
since Oct 2017
AS12389Residential520PJSC Rostelecom
87.253.8.0/22
since Oct 2017
AS12389Residential258PJSC Rostelecom
87.253.13.0/24
since Mar 2008
AS13118ResidentialPJSC Rostelecom
87.253.15.0/24
since Oct 2017
AS12389Residential72PJSC Rostelecom
87.253.16.0/21
since May 2008
AS13118Residential587PJSC Rostelecom
87.253.16.0/22
since Oct 2017
AS12389Residential296PJSC Rostelecom
87.253.20.0/23
since Oct 2017
AS12389Residential153PJSC Rostelecom
87.253.22.0/24
since Oct 2018
AS12389Residential66PJSC Rostelecom
87.253.23.0/24
since Oct 2018
AS12389Residential72PJSC Rostelecom
87.253.24.0/21
since Apr 2008
AS13118Residential499PJSC Rostelecom
87.253.24.0/22
since Oct 2017
AS12389Residential265PJSC Rostelecom
87.253.28.0/22
since Oct 2017
AS12389Residential234PJSC Rostelecom

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
87.253.0.0/198,192RU-RTK-20071212PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 12, 2007abuse@rt.ru
└ 87.253.0.0/204,096MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl branchASSIGNED PADec 20, 2024abuse@rt.ru
via RU-RTK-20071212
└ 87.253.16.0/212,048MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl branchASSIGNED PADec 20, 2024abuse@rt.ru
via RU-RTK-20071212
└ 87.253.24.0/221,024MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl BranchASSIGNED PAApr 10, 2026abuse@rt.ru
via RU-RTK-20071212
└ 87.253.28.0/221,024MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl BranchASSIGNED PAApr 10, 2026abuse@rt.ru
via RU-RTK-20071212

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
Oct 2005
Current origin since
Apr 2017 · 9.6 yr
Origin networks
2
Last change of origin
Feb 2016
Recorded history

History

Handoffs
1