Data as of Nov 16, 2026

5.142.62.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
35
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

554 observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • Decodo
  • EnigmaProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxio
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.142.0.0/16
since Jul 2017
AS12389Residential8,845
126 always on
PJSC Rostelecom
5.136.0.0/13
since Sep 2018
AS12389Residential116,825
944 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.136.0.0/13524,288RU-RTK-20120703PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 3, 2012abuse@rt.ru
└ 5.142.60.0/221,024RU-AVANGARD-DSLPJSC RostelecomASSIGNED PAAug 27, 2021abuse@rt.ru
via RU-RTK-20120703

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

Covering aggregate above, the prefix's own history below

5.142.0.0/18

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
May 2017 · 9.5 yr
Origin networks
2
Last change of origin
May 2017
Recorded history

History

Handoffs
1