Data as of Nov 17, 2026

176.162.240.0/20

22 residential-proxy exits · 30 days

Bouygues Telecom SA

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
22
0.54% of its addresses · 30 days
Always-on exits
1
4.5% of its exits
Spread
12 of 16
/24s with at least one exit
Providers
55
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9HTTP
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • 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.162.240.0/204,096BOUYGTELBouygues Telecom Division MobileASSIGNED PAMay 3, 2021abuse@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