Data as of Nov 17, 2026

86.62.128.0/18

54 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
54
0.33% of its addresses · 30 days
Always-on exits
2
3.7% of its exits
Spread
18 of 64
/24s with at least one exit
Providers
59
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

14K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CoreProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXORA
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

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
86.62.128.0/1816,384NO-GLOBALCONNECT-20050610Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAJun 10, 2005abuse@globalconnect.no
└ 86.62.128.0/221,024HOMENET-DHCPunknownASSIGNED PAMar 7, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.132.0/221,024HOMENET-DHCPunknownASSIGNED PAMar 7, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.136.0/221,024HOMENET-DHCPunknownASSIGNED PAMar 7, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.140.0/221,024HOMENET-DHCPunknownASSIGNED PAMar 7, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.144.0/24256AS2116-CUSTOMERNET-86621440Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.145.0/24256AS2116-CUSTOMERNET-86621450Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.146.0/2664AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.146.64/2664AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.146.128/2664AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.146.192/2664AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.0/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.32/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.64/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.96/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.128/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.160/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.192/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.147.224/2732AS2116-CUSTOMER-DHCPCustomer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.148.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 21, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.152.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 21, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.156.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 21, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.160.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 22, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.164.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 22, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.168.248/298AS2116-CUST-ABACUS-IT-ASunknownASSIGNED PAMar 7, 2023abuse@globalconnect.no
via NO-GLOBALCONNECT-20050610
└ 86.62.171.96/298AS2116-CUST-A-MBLER-ASunknownASSIGNED PAMar 7, 2023abuse@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 this prefix

Summary

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