Data as of Nov 16, 2026

212.33.0.0/22

1 residential-proxy exit · 30 days

JSC 'Globus-Telecom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
8
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

15 observations

Proxy providers listing exits

  • GEEKPROXY_FLEX
  • GSocks
  • Infatica
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Shifter

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
212.33.0.0 - 212.33.17.2554,608RU-GLOBUS-20060301JSC "Globus-Telecom" (ORG-GL4-RIPE) · RUALLOCATED PAMay 1, 2019noc@globus-telecom.com
└ 212.33.0.0/24256GLOBUS-TELECOM-DSL1CJSC GLOBUS-TELECOM, Russia, MoscowASSIGNED PAMar 24, 2007noc@globus-telecom.com
via RU-GLOBUS-20060301
└ 212.33.1.0 - 212.33.2.255512GLOBUS-TELECOM-DSLJSC GLOBUS-TELECOM, Russia, MoscowASSIGNED PAAug 29, 2006noc@globus-telecom.com
via RU-GLOBUS-20060301
└ 212.33.3.0/24256GLOBUS-TELECOM-PTPCJSC GLOBUS-TELECOM, Russia, MoscowASSIGNED PAJul 24, 2006noc@globus-telecom.com
via RU-GLOBUS-20060301

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
Feb 2020
Current origin since
Feb 2020 · 6.7 yr
Origin networks
1