Data as of Nov 21, 2026

176.139.114.0/24

3 residential-proxy exits · 30 days

Bouygues Telecom SA

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
2
67% of its exits
Providers
22
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

15K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • B2Proxy
  • BottingTools
  • Decodo
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • IPFly
  • IPMUSK
  • IPRoyal
  • KindProxy
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • ProxyWing
  • PuraRoute
  • RainProxy
  • YumiProxy

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.0.0/1732,768BOUYGTEL-ISP-WIRELINEPool for retail FTTH 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.7 yr
Origin networks
2
Last change of origin
Mar 2017
Recorded history

History

Handoffs
1