Data as of Nov 14, 2026

83.99.198.0/23

7 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Always-on exits
2
29% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
31
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.99.198.0/2415
83.99.199.0/2412

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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.198.0/23512LVBALTICOM-NETWORK18"Balticom" JSCASSIGNED PAJul 17, 2006abuse@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