Data as of Nov 19, 2026

88.202.192.0/20

19 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
19
0.46% of its addresses · 30 days
Spread
8 of 16
/24s with at least one exit
Providers
55
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4.0K observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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
88.202.192.0/204,096UK-GIGACLEAR-20051122Gigaclear Limited (ORG-GL85-RIPE) · GBALLOCATED PAFeb 10, 2014abuse@gigaclear.com
└ 88.202.192.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.193.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.194.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.195.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.196.0/221,024GOD01-H-V111Gigaclear Limited (ORG-GL85-RIPE) · GBASSIGNED PASep 17, 2014abuse@gigaclear.com
└ 88.202.200.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.201.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.202.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.203.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.204.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.205.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.206.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122
└ 88.202.207.0/24256GigaclearGigaclearASSIGNED PAJan 6, 2016abuse@gigaclear.com
via UK-GIGACLEAR-20051122

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
Jul 2014
Current origin since
Jul 2014 · 12 yr
Origin networks
1