Data as of Nov 13, 2026

79.172.16.0/21

28 residential-proxy exits · 30 days

LLC Cifrovie Seti Urala

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
28
1.4% of its addresses · 30 days
Always-on exits
19
68% of its exits
Spread
5 of 8
/24s with at least one exit
Providers
51
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

71K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NovaProxy
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalData
  • 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
79.172.16.0/212,048RU-CSU-20070927LLC Cifrovie Seti Urala (ORG-LCSU1-RIPE) · RUALLOCATED PAApr 24, 2019abuse@convex.ru
└ 79.172.16.0/24256convex-kirovgradKirovgrad broadbandASSIGNED PAApr 24, 2019abuse@convex.ru
via RU-CSU-20070927
└ 79.172.17.0/24256convex-kirovgradKirovgrad b2b static poolASSIGNED PAApr 24, 2019abuse@convex.ru
via RU-CSU-20070927
└ 79.172.18.0/23512convex-kirovgradKirovgrad static poolASSIGNED PAApr 24, 2019abuse@convex.ru
via RU-CSU-20070927
└ 79.172.20.0/221,024convex-kirovgradunknownASSIGNED PAApr 24, 2019abuse@convex.ru
via RU-CSU-20070927

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
Aug 2009
Current origin since
Dec 2018 · 7.9 yr
Origin networks
2
Last change of origin
Dec 2018
Recorded history

History

Handoffs
1