Data as of Nov 10, 2026

89.91.0.0/17

30 residential-proxy exits · 30 days

Bouygues Telecom SA

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
30
0.09% of its addresses · 30 days
Always-on exits
3
10% of its exits
Spread
23 of 128
/24s with at least one exit
Providers
43
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

6.9K observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.80.0.0/121,048,576FR-BOUYGTEL-20060223Bouygues Telecom SA (ORG-BT2-RIPE) · FRALLOCATED PAFeb 23, 2006abuse@bouyguestelecom.fr
└ 89.91.0.0/1732,768BOUYGTEL-ISP-WIRELINEPool for Enterprise customersASSIGNED PAMar 22, 2016abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20060223

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 89.80.0.0/12

89.80.0.0/12

Routing history

Pattern
Stable
First seen
Mar 2006
Current origin since
Mar 2006 · 21 yr
Origin networks
1