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

86.62.156.0/22

17 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
17
1.7% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
37
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

752 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.62.157.0/2406
86.62.158.0/2406
86.62.159.0/2404
86.62.156.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

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.156.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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