Data as of Nov 8, 2026

213.18.128.0/18

572 residential-proxy exits · 30 days

Gigaclear Limited

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

Residential-proxy exits

Proxy exits
572
3.5% of its addresses · 30 days
Always-on exits
36
6.3% of its exits
Spread
64 of 64
/24s with at least one exit
Providers
107
selling exits here
Oct 9, 2026 – Nov 7, 2026

Exits seen per day

187K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • MrScraper
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYWING_BASIC
  • PSBProxy
  • PrivateByte
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • 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
213.18.128.0/1816,384UK-GIGACLEAR-19990916Gigaclear Limited (ORG-GL85-RIPE) · GBALLOCATED PAOct 10, 2019abuse@gigaclear.com
└ 213.18.128.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.129.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.130.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.131.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.132.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.133.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.134.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.135.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.136.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.137.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.138.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.139.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.140.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.141.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.142.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.143.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.144.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.145.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.146.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.147.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.148.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.149.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.150.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.151.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.152.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.153.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.154.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.155.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.156.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.157.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.158.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.159.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.160.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.161.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.162.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.163.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.164.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.165.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.166.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.167.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.168.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.169.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.170.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.171.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.172.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.173.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.174.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.175.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.176.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.177.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.178.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.179.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.180.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.181.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.182.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.183.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.184.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.185.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.186.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.187.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.188.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.189.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.190.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916
└ 213.18.191.0/24256GIGA-CUSTunknownASSIGNED PAOct 14, 2019abuse@gigaclear.com
via UK-GIGACLEAR-19990916

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

Origin network

AS56329

GB
Name
Gigaclear Limited
Type
Internet provider
Registered
Jan 31, 2011
Domain
gigaclear.com
Website
www.gigaclear.com/
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed