Data as of Nov 20, 2026

193.75.48.0/21

23 residential-proxy exits · 30 days

Globalconnect AS

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
23
1.1% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
55
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

6.4K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GoProxies
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXORA
  • Proxies.fo
  • Proxio
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
193.75.0.0/1732,768NO-GLOBALCONNECT-19960513Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAAug 2, 2002abuse@globalconnect.no
└ 193.75.48.0/212,048HOMENET-DHCPunknownASSIGNED PAMay 29, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-19960513

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 193.75.0.0/17

193.75.0.0/17

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1