Data as of Nov 16, 2026

217.168.68.0/24

24 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
24
9.4% of its addresses · 30 days
Providers
40
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RealProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.168.64.0/20
since Dec 2021
AS12389Residential64
1 always on
PJSC 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
217.168.64.0/204,096RU-RTK-20010320PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 23, 2002abuse@rt.ru
└ 217.168.68.0/24256BALTNET-NETJSC "Elektrosvyaz" Kaliningradskoy oblastiASSIGNED PAJun 8, 2023abuse@rt.ru
via RU-RTK-20010320

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
May 2005
Current origin since
Feb 2020 · 6.8 yr
Origin networks
2
Last change of origin
Feb 2020
Recorded history

History

Handoffs
1