Data as of Nov 20, 2026

109.190.0.0/16

83 residential-proxy exits · 30 days

OVH SAS

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

Residential-proxy exits

Proxy exits
83
0.13% of its addresses · 30 days
Always-on exits
8
9.6% of its exits
Spread
57 of 256
/24s with at least one exit
Providers
80
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

37K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_BASIC
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GloryCloud
  • GoProxies
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSTPROXY_PRIME
  • NextProxy
  • NiuProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SCRAPELESS
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • 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
109.190.0.0/1665,536FR-OVH-20110916OVH SAS (ORG-OS3-RIPE) · FRALLOCATED PASep 16, 2011abuse@ovh.net
└ 109.190.0.0/1816,384OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PADec 20, 2012abuse@ovh.net
via FR-OVH-20110916
└ 109.190.64.0/1816,384OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 1, 2015abuse@ovh.net
via FR-OVH-20110916
└ 109.190.128.0/1816,384OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 1, 2015abuse@ovh.net
via FR-OVH-20110916
└ 109.190.192.0/198,192OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916
└ 109.190.224.0/204,096OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916
└ 109.190.240.0/212,048OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916
└ 109.190.248.0/221,024OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916
└ 109.190.252.0/23512OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916
└ 109.190.254.11/321OVH-DSLOVH Ltd (ORG-OL17-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
└ 109.190.255.0/24256OVH-DSLOVH Telecom (ORG-OT26-RIPE)ASSIGNED PASep 21, 2016abuse@ovh.net
via FR-OVH-20110916

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
Dec 2009
Current origin since
Aug 2013 · 13 yr
Origin networks
3
Last change of origin
Aug 2013
Recorded history

History

Handoffs
2