Data as of Nov 13, 2026

5.142.187.0/24

9 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Providers
24
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

444 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • FastProxy
  • GSocks
  • IPFly
  • Infatica
  • Kookey
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.142.0.0/16
since Jul 2017
AS12389Residential8,902
138 always on
PJSC Rostelecom
5.136.0.0/13
since Sep 2018
AS12389Residential115,270
867 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/18

Routing history

Pattern
Stable
First seen
Dec 2012
Current origin since
Jan 2017 · 9.8 yr
Origin networks
2
Last change of origin
Jan 2017
Recorded history

History

Handoffs
1