Data as of Nov 16, 2026

5.141.244.0/24

1 residential-proxy exit · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

371 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.136.0.0/13
since Sep 2018
AS12389Residential116,366
922 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.240.0/204,096Ural_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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jun 2014
Current origin since
Aug 2017 · 9.2 yr
Origin networks
2
Last change of origin
Aug 2017
Recorded history

History

Handoffs
1