LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

217.174.4.0/24

10 residential-proxy exits · 30 days

'Resurs-Svyaz' Ltd

Announcement
217.174.0.0/20
No RPKI
Announced by
AS34629
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
2
20% of its exits
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.174.0.0/204,096RU-ORN-20081121"Resurs-Svyaz" Ltd (ORG-LA49-RIPE) · RUALLOCATED PANov 21, 2008abuse@orn.ru
└ 217.174.0.0/212,048ORNRUNETResurs-Svyaz Ltd.ASSIGNED PAFeb 2, 2009abuse@orn.ru
via RU-ORN-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 217.174.0.0/20

217.174.0.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jan 2009 · 18 yr
Origin networks
2
Last change of origin
Jan 2009
Recorded history

History

Handoffs
1