LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

5.141.83.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
2
67% of its exits
Providers
23
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.136.0.0/13
since Sep 2018
AS12389Residential115,075
840 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.141.0.0/1665,536Ural_BranchunknownLIR-PARTITIONED PADec 1, 2022abuse@rt.ru
via RU-RTK-20120703
└ 5.141.0.0/1732,768Ural_BranchunknownASSIGNED PADec 1, 2022abuse@rt.ru
via Ural_Branch

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

5.141.82.0/23

Routing history

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

History

Handoffs
1