Data as of Nov 17, 2026

217.171.0.0/20

2 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
97% of it

Residential-proxy exits

Proxy exits
2
0.05% of its addresses · 30 days
Spread
2 of 16
/24s with at least one exit
Providers
22
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

198 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.171.4.0/2401
217.171.9.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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.171.0.0/204,096RU-RTK-20010330PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 25, 2002abuse@rt.ru
└ 217.171.0.0/23512AEROCOM-RUAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PASep 10, 2002abuse@rt.ru
via RU-RTK-20010330
└ 217.171.2.0 - 217.171.3.127384aerocom-ruAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PA—abuse@rt.ru
via RU-RTK-20010330
└ 217.171.3.128/25128aerocom-ruAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PAOct 16, 2001abuse@rt.ru
via RU-RTK-20010330
└ 217.171.4.0/24256AEROCOM-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 4, 2007abuse@rt.ru
via RU-RTK-20010330
└ 217.171.5.0/24256aerocom-ruAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PAMar 19, 2002abuse@rt.ru
via RU-RTK-20010330
└ 217.171.6.0/24256aerocom-ruAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PAJun 9, 2003abuse@rt.ru
via RU-RTK-20010330
└ 217.171.7.0/24256aerocom-ruAEROCOM,117437, build. 108, Profsoyuznaya streetASSIGNED PAOct 21, 2003abuse@rt.ru
via RU-RTK-20010330
└ 217.171.8.0/24256AEROCOM-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 4, 2007abuse@rt.ru
via RU-RTK-20010330
└ 217.171.9.0/24256aerocom-ruAEROCOM,117437, build. 108ASSIGNED PAFeb 4, 2004abuse@rt.ru
via RU-RTK-20010330
└ 217.171.10.0/24256aerocom-ruAEROCOM,117437, build. 108ASSIGNED PAApr 5, 2004abuse@rt.ru
via RU-RTK-20010330
└ 217.171.11.0/24256aerocom-ruAEROCOM,117437, build. 108ASSIGNED PAJul 14, 2004abuse@rt.ru
via RU-RTK-20010330
└ 217.171.12.0/24256AEROCOM-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 4, 2007abuse@rt.ru
via RU-RTK-20010330
└ 217.171.13.0/24256AEROCOM-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 4, 2007abuse@rt.ru
via RU-RTK-20010330
└ 217.171.14.0/24256aerocom-ruAEROCOM,117437, build. 108ASSIGNED PAJul 12, 2006abuse@rt.ru
via RU-RTK-20010330
└ 217.171.15.0/24256AEROCOM-VSERosnet ( Russian Data Communication Company )ASSIGNED PAOct 4, 2007abuse@rt.ru
via RU-RTK-20010330

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,96897%2
Business1283.1%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

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

History

Handoffs
1