Data as of Nov 15, 2026

46.23.42.0/23

4 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
2
50% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
30
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

3.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.23.42.0/2423
46.23.43.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FROXY
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.23.32.0/204,096LV-BALTICOM-20101202JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PADec 2, 2010abuse@balticom.info
└ 46.23.42.0/23512LVBALTICOM-NETWORK-4642-R"Balticom" JSCASSIGNED PAAug 13, 2013abuse@balticom.info
via LV-BALTICOM-20101202

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 46.23.32.0/20

46.23.32.0/20

Routing history

Pattern
Stable
First seen
Jul 2011
Current origin since
Jul 2011 · 15 yr
Origin networks
1