Data as of Nov 18, 2026

5.140.171.0/24

2 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
22
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

8.8K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Decodo
  • Evomi
  • Geonode
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • Kookey
  • Maskify
  • Oxylabs
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • StrikeProxy
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.136.0.0/13
since Sep 2018
AS12389Residential117,668
1,005 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.140.112.0 - 5.140.255.25536,864USI_ADSL_USERSDynamic distribution IP's for broadband servicesSUB-ALLOCATED PAAug 26, 2025abuse@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.140.168.0/22

Routing history

Pattern
Stable
First seen
Apr 2013
Current origin since
Nov 2017 · 9.0 yr
Origin networks
2
Last change of origin
Nov 2017
Recorded history

History

Handoffs
1