Data as of Nov 10, 2026

86.62.152.0/22

19 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
19
1.9% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

Proxy providers listing exits

  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.62.128.0/1816,384NO-GLOBALCONNECT-20050610Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAJun 10, 2005abuse@globalconnect.no
└ 86.62.152.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 21, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610

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 86.62.128.0/18

86.62.128.0/18

Routing history

Pattern
Stable
First seen
Jul 2005
Current origin since
Apr 2008 · 19 yr
Origin networks
2
Last change of origin
Apr 2008
Recorded history

History

Handoffs
1