Data as of Nov 16, 2026

31.37.112.0/24

8 residential-proxy exits · 30 days

Bouygues Telecom SA

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
4
50% of its exits
Providers
55
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

14K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • PYPROXY
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.32.0.0/13524,288FR-BOUYGTEL-20110201Bouygues Telecom SA (ORG-BT2-RIPE) · FRALLOCATED PAFeb 1, 2011abuse@bouyguestelecom.fr
└ 31.36.0.0/15131,072BOUYGTEL-ISP-WIRELINEPool for Broadband DSL customersASSIGNED PAOct 14, 2011abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20110201

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 31.32.0.0/13

31.32.0.0/13

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1