LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

46.23.35.0/24

9 residential-proxy exits · 30 days

JSC Balticom

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
2
22% of its exits
Providers
43
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5.7K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • Webshare

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.34.0 - 46.23.37.2551,024LVBALTICOM-NETWORK-23-34"Balticom" JSCASSIGNED PASep 21, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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