Data as of Nov 16, 2026

176.176.13.0/24

3 residential-proxy exits · 30 days

Bouygues Telecom SA

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
39
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Novada
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • TrueProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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.176.0.0/1665,536BOUYGTEL-ISP-WIRELESSPool for Enterprise customersASSIGNED PAMar 23, 2016abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20110706

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