Data as of Nov 10, 2026

5.140.231.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
Providers
27
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.136.0.0/13
since Sep 2018
AS12389Residential114,604
1,260 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.230.0/23

Routing history

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

History

Handoffs
1