Data as of Nov 10, 2026

176.139.167.0/24

12 residential-proxy exits · 30 days

Bouygues Telecom SA

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
2
17% of its exits
Providers
43
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.128.0.0/104,194,304FR-BOUYGTEL-20110706Bouygues Telecom SA (ORG-BT2-RIPE) · FRALLOCATED PAJul 6, 2011abuse@bouyguestelecom.fr
└ 176.128.0.0/112,097,152BOUYGTELBouygues Telecom Fixe and Mobile DivisionLIR-PARTITIONED PAOct 12, 2015abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20110706
└ 176.139.128.0/1732,768BOUYGTEL-ISP-WIRELINEPool for Broadband DSL customersASSIGNED PAMar 23, 2016abuse@bouyguestelecom.fr
via BOUYGTEL

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 176.128.0.0/10

176.128.0.0/10

Routing history

Pattern
Stable
First seen
Jul 2011
Current origin since
Mar 2017 · 9.6 yr
Origin networks
2
Last change of origin
Mar 2017
Recorded history

History

Handoffs
1