Data as of Nov 16, 2026

82.198.187.0/24

15 residential-proxy exits · 30 days

JSC 'Globus-Telecom'

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
55
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LOKIPROXY
  • LudaxProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • SwiftProxy
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.198.160.0/198,192RU-GLOBUS-20031118JSC "Globus-Telecom" (ORG-GL4-RIPE) · RUALLOCATED PANov 18, 2003noc@globus-telecom.com
└ 82.198.187.0/24256SANNETRussia, MoscowASSIGNED PANov 25, 2008noc@globus-telecom.com
via RU-GLOBUS-20031118

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

82.198.160.0/19

Routing history

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