Data as of Nov 16, 2026

185.205.128.0/22

3 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
3
0.29% of its addresses · 30 days
Always-on exits
2
67% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • Maskify
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • VitalData
  • VitalExclusive

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
185.205.128.0/221,024RU-RTK-20170526PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAAug 18, 2020abuse@rt.ru
└ 185.205.131.0/24256RU-RTK-20170526unknownASSIGNED PAMar 5, 2025abuse@rt.ru
via RU-RTK-20170526

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
Sep 2019
Current origin since
Sep 2021 · 5.1 yr
Origin networks
2
Last change of origin
Sep 2021
Recorded history

History

Handoffs
1