Data as of Nov 16, 2026

5.141.234.0/23

27 residential-proxy exits · 30 days

LLC 'KomTehCentr' · space held by PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
27
5.3% of its addresses · 30 days
Always-on exits
6
22% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
72
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

10K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.141.234.0/24414
5.141.235.0/24213

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.136.0.0/13
since Sep 2018
AS12389Residential116,825
944 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.234.0/23512PLANETA_B2CunknownSUB-ALLOCATED PANov 23, 2021abuse@rt.ru
via Ural_Branch
└ 5.141.234.0/24256MIRALOGIC-NETLLC "KomTehCentr" (ORG-EP3-RIPE) · RUASSIGNED PANov 23, 2021noc@itmh.ru
└ 5.141.235.0/2664MIRALOGIC-NETLLC KOMTEHCENTR FTTB CustomersASSIGNED PAJan 19, 2022abuse@rt.ru
via PLANETA_B2C
└ 5.141.235.64/2664MIRALOGIC-NETLLC KOMTEHCENTR FTTB CustomersASSIGNED PAJan 19, 2022abuse@rt.ru
via PLANETA_B2C
└ 5.141.235.128/2664MIRALOGIC-NETLLC KOMTEHCENTR FTTB CustomersASSIGNED PAJan 19, 2022abuse@rt.ru
via PLANETA_B2C
└ 5.141.235.192/2664MIRALOGIC-NETLLC KOMTEHCENTR FTTB CustomersASSIGNED PAJan 19, 2022abuse@rt.ru
via PLANETA_B2C

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
Rotating
First seen
Mar 2014
Current origin since
Dec 2021 · 4.9 yr
Origin networks
3
Last change of origin
Dec 2021
Recorded history

History

Handoffs
2