Data as of Nov 10, 2026

178.74.0.0/18

216 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
216
1.3% of its addresses · 30 days
Always-on exits
19
8.8% of its exits
Spread
62 of 64
/24s with at least one exit
Providers
92
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

83K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateByte
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • 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
178.74.0.0/1816,384NO-GLOBALCONNECT-20100323Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAMar 23, 2010abuse@globalconnect.no
└ 178.74.0.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.4.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.8.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.12.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.16.0/221,024HOMENET-DHCPunknownASSIGNED PAJul 15, 2011abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.20.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.24.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.28.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.32.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.36.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.40.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.44.0/221,024HOMENET-DHCPunknownASSIGNED PAJul 14, 2011abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.48.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.52.0/221,024HOMENET-DHCPunknownASSIGNED PAJul 14, 2011abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.56.0/221,024HOMENET-DHCPunknownASSIGNED PAApr 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20100323
└ 178.74.60.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 this prefix

Summary

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