Data as of Nov 11, 2026

37.191.136.0/22

17 residential-proxy exits · 30 days

Globalconnect AS

Announcement
RPKI valid
Announced by
Type
Internet provider
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
40
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.0K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.191.128.0/1732,768NO-GLOBALCONNECT-20120321Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PADec 30, 2020abuse@globalconnect.no
└ 37.191.136.0/221,024HOMENET-DHCPunknownASSIGNED PAFeb 11, 2025abuse@globalconnect.no
via NO-GLOBALCONNECT-20120321

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

37.191.128.0/17

Routing history

Pattern
Rotating
First seen
May 2012
Current origin since
Mar 2022 · 4.6 yr
Origin networks
2
Last change of origin
Mar 2022
Recorded history

History

Handoffs
1