Data as of Nov 21, 2026

82.193.79.0/24

15 residential-proxy exits · 30 days

JSC Balticom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Always-on exits
3
20% of its exits
Providers
45
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

6.7K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FROXY
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPOasis
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSTPROXY_LITE
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.193.64.0/198,192LV-BALTICOM-20031006JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PAOct 6, 2003abuse@balticom.info
└ 82.193.79.0/24256LVBALTICOM"Balticom" JSCASSIGNED PADec 30, 2016abuse@balticom.info
via LV-BALTICOM-20031006

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.193.64.0/19

82.193.64.0/19

Routing history

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