Data as of Nov 10, 2026

62.109.167.0/24

24 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Always-on exits
1
4.2% of its exits
Providers
47
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.109.160.0/198,192RU-RTK-20020301PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 4, 2002abuse@rt.ru
└ 62.109.167.0/24256MELS-NETMurmanelecrtosviazASSIGNED PAJun 3, 2005abuse@rt.ru
via RU-RTK-20020301

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 62.109.160.0/19

62.109.160.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1