Data as of Nov 12, 2026

46.23.40.0/24

10 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
40
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GhostConnect
  • GonzoProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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.40.0/23512LVBALTICOM-NETWORK-23-38"Balticom" JSCASSIGNED PANov 23, 2012abuse@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