Data as of Nov 20, 2026

212.33.154.0/24

2 residential-proxy exits · 30 days

Globalconnect AS

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
18
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

62 observations

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.33.128.0/198,192NO-GLOBALCONNECT-980528Globalconnect AS (ORG-BNA1-RIPE) · NOALLOCATED PAApr 23, 2002abuse@globalconnect.no
└ 212.33.154.56/298NO-XFIBER-CUST-WESTNETunknownASSIGNED PAFeb 1, 2007abuse@globalconnect.no
via NO-GLOBALCONNECT-980528
└ 212.33.154.192/2664NO-XFIBER-CUST-RIGNET-1Rignet ASASSIGNED PAJul 2, 2002abuse@globalconnect.no
via NO-GLOBALCONNECT-980528

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 212.33.128.0/19

212.33.128.0/19

Routing history

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