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

5.43.128.0/19

1,959 residential-proxy exits · 30 days

Joint stock company 'For'

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

Residential-proxy exits

Proxy exits
1,959
24% of its addresses · 30 days
Always-on exits
1
0.05% of its exits
Spread
31 of 32
/24s with at least one exit
Providers
114
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

81K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.43.128.0/2419
5.43.153.0/24074
5.43.131.0/24073
5.43.143.0/24073
5.43.130.0/24072
5.43.142.0/24071
5.43.157.0/24071
5.43.150.0/24070
5.43.138.0/24070
5.43.139.0/24070
5.43.133.0/24070
5.43.140.0/24069
5.43.152.0/24068
5.43.141.0/24067
5.43.155.0/24067
5.43.151.0/24067
5.43.149.0/24065
5.43.137.0/24065
5.43.156.0/24063
5.43.136.0/24062
5.43.148.0/24062
5.43.146.0/24062
5.43.134.0/24061
5.43.145.0/24060

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.43.128.0/198,192RU-FOR-20120521Joint stock company "For" (ORG-JSC13-RIPE) · RUALLOCATED PASep 7, 2017abuse_contact@mail.ru
└ 5.43.128.0/24256UKES-NETUKES Ltd., Nevskogo 4 str., Bulanash, Sverdlovsk regionASSIGNED PAMay 29, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.129.0/24256K-TELECOMK-TELECOM, NvASSIGNED PAJun 19, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.130.0/23512VI-LINEVI-LINE, EkaterinburgASSIGNED PAJul 17, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.132.0/24256REST-SVKREST-SVK, SeverouralskASSIGNED PAJul 19, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.133.0/24256MIZARPROJECT-NET_K-TMizar-Project Ltd.ASSIGNED PAJul 23, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.134.0/23512SA-NETSA-net, Baranchinskiy u.t.c., Sverdlovsk reg.ASSIGNED PAJul 19, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.136.0/23512K-TELECOMK-TELECOM, EkASSIGNED PAJul 26, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.138.0/24256K-TELECOMK-TELECOM, KrASSIGNED PAJul 26, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.139.0/24256K-TELECOMK-TELECOM, VlASSIGNED PAJul 26, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.140.0/24256VI-LINEVI-LINE, EkaterinburgASSIGNED PAAug 15, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.141.0/24256VI-LINEVI-LINE, EkaterinburgASSIGNED PANov 8, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.142.0/23512MIZARPROJECT-NET_K-TMizar-Project Ltd.ASSIGNED PASep 3, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.144.0/23512K-TELECOMK-TELECOM, SeverouralskASSIGNED PAMay 21, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.146.0/23512K-TELECOMK-TELECOM, SuASSIGNED PAMay 21, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.148.0/24256MIZARPROJECT-NET_K-TMizar-Project Ltd.ASSIGNED PAMay 30, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.149.0/24256K-TELECOMunknownASSIGNED PAJun 4, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.150.0/24256K-TELECOMunknownASSIGNED PAJun 4, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.151.0/24256K-TELECOMunknownASSIGNED PAJun 4, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.152.0/23512REST-SVKREST-SVK, SeverouralskASSIGNED PAJun 7, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.154.0/24256MIZARPROJECT-NET_K-TMizar-Project Ltd.ASSIGNED PAJun 14, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.155.0/24256K-TELECOMK-TELECOM, SuASSIGNED PAJun 19, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.156.0/23512K-TELECOMK-TELECOM, SuASSIGNED PAJun 14, 2012abuse_contact@mail.ru
via RU-FOR-20120521
└ 5.43.158.0/23512K-TELECOMK-TELECOM, KsASSIGNED PAJun 18, 2012abuse_contact@mail.ru
via RU-FOR-20120521

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2012
Current origin since
May 2012 · 14 yr
Origin networks
1