Data as of Nov 22, 2026

217.118.32.0/19

12 residential-proxy exits · 30 days

Globalconnect AS

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
12
0.15% of its addresses · 30 days
Always-on exits
1
8.3% of its exits
Spread
9 of 32
/24s with at least one exit
Providers
26
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CoreProxy
  • DataImpulse
  • Decodo
  • FastProxy
  • FloppyData
  • Geonode
  • IPRoyal
  • KocerRoxy
  • LemonBright
  • Novada
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RainProxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.118.32.0/198,192NO-GLOBALCONNECT-20010212Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAJun 11, 2002abuse@globalconnect.no
└ 217.118.32.0/2732AS2116-CUSTOMERNET-217118320Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.33.0/24256AS2116-MGMT-LOOPBACKBlocks used for management loopbacksASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.34.168/298AS2116-MGMT-LOOPBACKBlocks used for management loopbacksASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.37.0/24256AS2116-CUSTOMERNET-217118370Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.38.40/298AS2116-CUSTOMERNET-2171183840Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.38.96/2732AS2116-CUSTOMERNET-2171183896Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.38.224/298AS2116-LINKNETSCustomer /31 or /30 linknetsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.38.248/298AS2116-CUSTOMERNET-21711838248Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.39.0/24256AS2116-CUSTOMERNET-217118390Customer netsASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.40.0/221,024AS2116-CUSTOMER-STATIC-LOOPBACKCustomer static /32 loopbacksASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212
└ 217.118.44.0/221,024AS2116-CUSTOMER-STATIC-LOOPBACKCustomer static /32 loopbacksASSIGNED PAMay 20, 2012abuse@globalconnect.no
via NO-GLOBALCONNECT-20010212

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 this prefix

Summary

Routing history

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