Data as of Nov 13, 2026

80.252.128.0/19

60 residential-proxy exits · 30 days

Flex Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
60
0.73% of its addresses · 30 days
Always-on exits
5
8.3% of its exits
Spread
23 of 32
/24s with at least one exit
Providers
81
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • 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
80.252.128.0/198,192RU-FLEX-20011210Flex Ltd. (ORG-FI3-RIPE) · RUALLOCATED PASep 17, 2004abuse@flex.ru
└ 80.252.128.0/212,048FlexNetWireless network in Moscow regionASSIGNED PADec 10, 2001abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.136.0/24256VegaNetVegaNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.137.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.138.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.139.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.140.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.141.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.142.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.143.0/24256FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210
└ 80.252.144.0/204,096FlexNetFlexNet customers networkASSIGNED PANov 29, 2022abuse@flex.ru
via RU-FLEX-20011210

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1