Data as of Nov 21, 2026

164.177.0.0/17

79 residential-proxy exits · 30 days

Bouygues Telecom SA

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
79
0.24% of its addresses · 30 days
Always-on exits
1
1.3% of its exits
Spread
51 of 128
/24s with at least one exit
Providers
94
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

10K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9HTTP
  • AETHYN_BASIC
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LOKIPROXY
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
164.177.0.0/1732,768FR-BOUYGTEL-20111118Bouygues Telecom SA (ORG-BT2-RIPE) · FRALLOCATED PANov 18, 2011abuse@bouyguestelecom.fr
└ 164.177.0.0 - 164.177.26.1276,784BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 22, 2016abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.26.128/2664ARVALISINFRASTRUCTUREASSIGNED PAJan 12, 2015abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.26.192/2732ARVALISINFRASTRUCTUREASSIGNED PAJan 12, 2015abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.26.224/2732BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 22, 2016abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.27.0/2664CTIFLINFRASTRUCTUREASSIGNED PAJan 12, 2015abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.27.64 - 164.177.29.255704BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 22, 2016abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.30.0/24256ACTA_INFORMATIQUEINFRASTRUCTUREASSIGNED PAJun 23, 2014abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.31.0/24256BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.32.0/221,024BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.0/25128BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.128/2664BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.192/298ACTA_INFORMATIQUEINFRASTRUCTUREASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.200/298BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.208/2816BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.224/2816BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.36.240/2816BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.37.0/24256BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.38.0/23512BOUYGTEL-ISP_WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.40.0/212,048BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.48.0/204,096BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118
└ 164.177.64.0/1816,384BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 25, 2021abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20111118

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2012
Current origin since
Feb 2012 · 15 yr
Origin networks
1