Data as of Nov 10, 2026

178.167.116.0/24

27 residential-proxy exits · 30 days

Flex Ltd.

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

Residential-proxy exits

Proxy exits
27
11% of its addresses · 30 days
Providers
40
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

604 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • IPFly
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • TrueProxies
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.167.0.0/17
since Mar 2010
AS21453Residential6,724
1 always on
Flex Ltd.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.167.0.0/1732,768RU-FLEX-20100315Flex Ltd. (ORG-FI3-RIPE) · RUALLOCATED PAMar 15, 2010abuse@flex.ru
└ 178.167.96.0/198,192FLEXNETFlex broadband usersASSIGNED PAMar 23, 2014abuse@flex.ru
via RU-FLEX-20100315

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

178.167.96.0/19

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Apr 2014 · 13 yr
Origin networks
1