Data as of Nov 20, 2026

81.191.44.0/22

17 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
17
1.7% of its addresses · 30 days
Always-on exits
2
12% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
43
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

5.0K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 9Proxy
  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • Geonode
  • HideProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.191.0.0/1665,536NO-GLOBALCONNECT-20030613Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAJun 13, 2003abuse@globalconnect.no
└ 81.191.44.0/221,024HOMENET-DHCPunknownASSIGNED PAMay 18, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20030613

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 81.191.0.0/16

81.191.0.0/16

Routing history

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