Data as of Nov 17, 2026

194.207.0.0/19

15 residential-proxy exits · 30 days

GCI Network Solutions Limited · space held by KCOM Group Limited

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

Residential-proxy exits

Proxy exits
15
0.18% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Spread
6 of 32
/24s with at least one exit
Providers
63
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

9.7K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
194.207.0.0/1665,536UK-KINGSTON-960404KCOM Group Limited (ORG-TCL3-RIPE) · GBALLOCATED PAJun 13, 2017abuse@kcom.com
└ 194.207.0.0/298KCOMNasstarASSIGNED PAFeb 1, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.0.8/298KCOMKcomASSIGNED PAFeb 1, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.0.16/304KCOMKcomASSIGNED PAFeb 7, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.0.20/304KCOMKcomASSIGNED PAFeb 7, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.1.0/24256KCOM-KCOMKcom National SCP -AS206509ASSIGNED PAAug 30, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.2.0/24256KCOM-KCOMKcom National SCP -AS206509ASSIGNED PAAug 30, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.3.0/24256KCOM-KCOMKcom National SCP -AS206509ASSIGNED PAAug 30, 2018abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.11.0/24256SGS-KCOMSGSASSIGNED PAJul 4, 2019abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.12.0/24256SGS-KCOMSGSASSIGNED PAJul 4, 2019abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.13.0/298SGS-KCOMSGSASSIGNED PAJul 4, 2019abuse@kcom.com
via UK-KINGSTON-960404
└ 194.207.13.12/304HIGHWAYSENGLAND-KCOMHighways EnglandASSIGNED PAJan 30, 2020abuse@kcom.com
└ 194.207.26.0/24256Ineedbroadband_LtdunknownASSIGNED PAMay 21, 2021abuse@ineedbroadband.co.uk

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
Rotating
First seen
Mar 2018
Current origin since
Nov 2023 · 3.0 yr
Origin networks
2
Last change of origin
Nov 2023
Recorded history

History

Handoffs
1