Data as of Nov 16, 2026

85.28.216.0/21

96 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
96
4.7% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
97
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LITPORT_LIMA
  • LOKIPROXY
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXORA
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PacketStream
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.28.192.0/18
since Jul 2005
AS34974Residential590PJSC 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
85.28.192.0/1816,384RU-RTK-20050511PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 11, 2005abuse@rt.ru
└ 85.28.216.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.217.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.218.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.219.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.220.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.221.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.222.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511
└ 85.28.223.0/24256RU-KAMCHATKAFar East Telecommunications CompanyASSIGNED PAJan 13, 2025abuse@rt.ru
via RU-RTK-20050511

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2017
Current origin since
Nov 2017 · 9.0 yr
Origin networks
1