Data as of Nov 10, 2026

62.35.47.0/24

7 residential-proxy exits · 30 days

Bouygues Telecom SA

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
44
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.34.0.0/15131,072FR-BOUYGTEL-20021009Bouygues Telecom SA (ORG-BT2-RIPE) · FRALLOCATED PAOct 10, 2002abuse@bouyguestelecom.fr
└ 62.35.0.0/1816,384BOUYGTEL-ISP-WIRELINEPool for Broadband DSL customersASSIGNED PAJan 21, 2011abuse@bouyguestelecom.fr
via FR-BOUYGTEL-20021009

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 62.34.0.0/15

62.34.0.0/15

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1