Data as of Nov 10, 2026

178.74.28.0/22

14 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
14
1.4% of its addresses · 30 days
Always-on exits
3
21% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
43
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

24K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.74.0.0/1816,384NO-GLOBALCONNECT-20100323Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAMar 23, 2010abuse@globalconnect.no
└ 178.74.28.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323

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

178.74.0.0/18

Routing history

Pattern
Stable
First seen
Apr 2010
Current origin since
Feb 2014 · 13 yr
Origin networks
2
Last change of origin
Feb 2014
Recorded history

History

Handoffs
1