LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

193.71.136.0/22

14 residential-proxy exits · 30 days

Globalconnect AS

Announcement
193.71.0.0/16
RPKI valid
Announced by
AS2116
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

3.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
193.71.139.0/2416
193.71.138.0/2415
193.71.136.0/2402
193.71.137.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
193.71.0.0/1665,536NO-GLOBALCONNECT-19930901Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAAug 2, 2002abuse@globalconnect.no
└ 193.71.136.0/221,024HOMENET-DHCPunknownASSIGNED PADec 2, 2021abuse@globalconnect.no
via NO-GLOBALCONNECT-19930901

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 193.71.0.0/16

193.71.0.0/16

Routing history

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