Data as of Nov 21, 2026

213.52.24.0/21

3 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
22
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

8.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.52.30.0/2411
213.52.24.0/2401
213.52.28.0/2401

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • Byteful
  • CliProxy
  • EVOPROXY
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_TURBO
  • GSocks
  • IPPeak
  • Infatica
  • LOKIPROXY
  • NodeProxy
  • NovProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • SOTAPROXY
  • Shifter
  • ThunderProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.52.0.0/1732,768NO-GLOBALCONNECT-20080123Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAJan 23, 2008abuse@globalconnect.no
└ 213.52.24.0/212,048AS2116-CUST-HNETT-BREDBAND-ASunknownASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20080123

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

213.52.0.0/17

Routing history

Pattern
Stable
First seen
Feb 2008
Current origin since
Feb 2011 · 16 yr
Origin networks
2
Last change of origin
Feb 2011
Recorded history

History

Handoffs
1