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

84.20.96.0/19

32 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
32
0.39% of its addresses · 30 days
Always-on exits
2
6.3% of its exits
Spread
13 of 32
/24s with at least one exit
Providers
53
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

5.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.20.102.0/2414
84.20.103.0/2411
84.20.100.0/2405
84.20.101.0/2404
84.20.121.0/2403
84.20.123.0/2403
84.20.99.0/2402
84.20.98.0/2402
84.20.108.0/2402
84.20.109.0/2402
84.20.120.0/2402
84.20.122.0/2402
84.20.97.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GSocks
  • GeekProxy
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RoamProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • Webshare

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
84.20.96.0/198,192NO-GLOBALCONNECT-20040902Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PASep 2, 2004abuse@globalconnect.no
└ 84.20.96.0/2664AS2116-CUSTOMERNET-8420960Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.96.120/298AS2116-CUSTOMERNET-842096120Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.97.0/24256HOMENET-DHCPunknownASSIGNED PAApr 6, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.98.0/23512HOMENET-DHCPunknownASSIGNED PAApr 6, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.100.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 6, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.104.0/221,024AS2116-HOMENET-DHCPunknownASSIGNED PANov 3, 2020abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.108.0/221,024HOMENET-DHCPunknownASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.112.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 6, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.116.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 6, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.120.0/221,024AS2116-HOMENET-DHCPunknownASSIGNED PANov 3, 2020abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902
└ 84.20.124.0/221,024AS2116-HOMENET-DHCPunknownASSIGNED PANov 3, 2020abuse@globalconnect.no
via NO-GLOBALCONNECT-20040902

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Sep 2016 · 10 yr
Origin networks
2
Last change of origin
Sep 2012
Recorded history

History

Handoffs
1