Data as of Nov 13, 2026

85.221.36.0/22

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.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
9
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

607 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.221.36.0/2401
85.221.37.0/2401
85.221.38.0/2401

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • Decodo
  • FastProxy
  • LemonBright
  • Oxylabs
  • StrikeProxy
  • Thordata
  • Webshare

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.221.0.0/1732,768NO-GLOBALCONNECT-20050208Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAFeb 8, 2005abuse@globalconnect.no
└ 85.221.36.0/221,024AS2116-DHCP-BNGunknownASSIGNED PAMay 27, 2022abuse@globalconnect.no
via NO-GLOBALCONNECT-20050208

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

85.221.0.0/17

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Sep 2016 · 10 yr
Origin networks
2
Last change of origin
Feb 2011
Recorded history

History

Handoffs
1