Data as of Nov 12, 2026

83.217.16.0/24

4 residential-proxy exits · 30 days

JSC 'Globus-Telecom'

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
12
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

86 observations

Proxy providers listing exits

  • 711Proxy
  • GSocks
  • IPFly
  • Infatica
  • NSocks
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.217.16.0/221,024RU-GLOBUS-20040303JSC "Globus-Telecom" (ORG-GL4-RIPE) · RUALLOCATED PASep 27, 2019noc@globus-telecom.com
└ 83.217.16.0/23512RU-GLOBUS-20190909CJSC GLOBUS-TELECOM, Russia, MoscowASSIGNED PASep 9, 2019noc@globus-telecom.com
via RU-GLOBUS-20040303

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 83.217.16.0/22

83.217.16.0/22

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Sep 2019 · 7.2 yr
Origin networks
2
Last change of origin
Sep 2019
Recorded history

History

Handoffs
1