Data as of Nov 10, 2026

83.99.239.0/24

1 residential-proxy exit · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
20
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

9.0K observations

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • Geonode
  • GoProxies
  • IPRoyal
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxy-Cheap
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • Webshare

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.99.128.0/1732,768LV-BALTICOM-20040138JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PAJan 28, 2004abuse@balticom.info
└ 83.99.236.0/221,024LVBALTICOM-NETWORK33"Balticom" JSCASSIGNED PAOct 3, 2008abuse@balticom.info
via LV-BALTICOM-20040138

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.99.128.0/17

83.99.128.0/17

Routing history

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