Data as of Nov 17, 2026

5.142.138.0/24

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
11
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

49 observations

Proxy providers listing exits

  • Byteful
  • GSocks
  • Geonix
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.142.128.0/18
since Jan 2017
AS12389Residential1,650
11 always on
PJSC Rostelecom
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.128.0/1816,384RU-AVANGARD-DSLOJSC "North-West Telecom"ASSIGNED PAJul 11, 2012abuse@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.128.0/20

Routing history

Pattern
Stable
First seen
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1