Data as of Nov 21, 2026

109.172.58.0/24

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
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
23
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

4.9K observations

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • 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
109.172.56.0 - 109.172.73.2554,608RU-RTK-20091118PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 11, 2020abuse@rt.ru
└ 109.172.56.0/212,048SUMTEL-COMMON-NETPJSC Rostelecom (ORG-JR8-RIPE) · RULIR-PARTITIONED PAMay 19, 2025abuse@rt.ru
└ 109.172.58.0/24256SUMTEL-COMMON-NETunknownSUB-ALLOCATED PAMay 19, 2025abuse@rt.ru
via SUMTEL-COMMON-NET

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
Reactivated
First seen
Sep 2014
Current origin since
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Jun 2025
Recorded history

History

Handoffs
1