Data as of Nov 18, 2026

82.193.68.0/24

3 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
34
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

8.8K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EVOPROXY
  • Evomi
  • FROXY
  • FlashProxy
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • Oxylabs
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata
  • 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.68.0/24256LVBALTICOM-NETWORK40"Balticom" JSCASSIGNED PAApr 4, 2005abuse@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