Data as of Nov 11, 2026

185.52.44.0/22

15 residential-proxy exits · 30 days

Hexatel SAS

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
2
13% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
46
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.52.44.0/2428
185.52.46.0/2404
185.52.47.0/2403

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • FastProxy
  • FlashProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MarsProxies
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RainProxy
  • ResiProxies
  • Shifter
  • Thordata
  • ThunderProxy
  • VProxy
  • VitalExclusive
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE

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
185.52.44.0/221,024FR-HEXATEL-FR-20140328Hexatel SAS (ORG-HS78-RIPE) · FRALLOCATED PAMar 28, 2014ripe@groupetc.com
└ 185.52.44.0/24256HEXATEL-INFRAunknownASSIGNED PAOct 20, 2026ripe@groupetc.com
via FR-HEXATEL-FR-20140328
└ 185.52.45.0/24256HEXATEL-CUSTOMERSunknownASSIGNED PAOct 20, 2026ripe@groupetc.com
via FR-HEXATEL-FR-20140328
└ 185.52.46.0/24256HEXATEL-CUSTOMERSunknownASSIGNED PAOct 20, 2026ripe@groupetc.com
via FR-HEXATEL-FR-20140328
└ 185.52.47.0/24256HEXATEL-CUSTOMERSunknownASSIGNED PAOct 20, 2026ripe@groupetc.com
via FR-HEXATEL-FR-20140328

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
Mar 2019
Current origin since
Mar 2019 · 7.7 yr
Origin networks
1