LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

213.18.166.0/24

10 residential-proxy exits · 30 days

Gigaclear Limited

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
1
10% of its exits
Providers
50
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.6K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

The registry's network records over this block, widest first, each 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.166.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 213.18.128.0/18

213.18.128.0/18

Routing history

Pattern
Stable
First seen
Sep 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
2
Last change of origin
Oct 2019
Recorded history

History

Handoffs
1