Data as of Nov 11, 2026

46.23.46.0/23

3 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

0.59% of its addresses · 30 days

Spread

2 of 2

/24s with at least one exit

Providers

selling exits here

Oct 12, 2026 – Nov 10, 2026

Exits seen per day

81 observations

/24s with the most always-on exits

/24	Always-on exits	Proxy exits
46.23.46.0/24	0	2
46.23.47.0/24	0	1

Proxy providers listing exits

2Extract
AnyIP
Byteful
CliProxy
GSocks
Infatica
LemonBright
LemonPrime
MangoProxy
NodeProxy
NovaProxy
PROXYSCRAPE
Proxyma
RainProxy
Shifter
Thordata
VitalExclusive

Registrations in this block

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

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
46.23.32.0/20	4,096	LV-BALTICOM-20101202	JSC Balticom (ORG-JB1-RIPE) · LV	ALLOCATED PA	Dec 2, 2010	abuse@balticom.info
└ 46.23.46.0/23	512	LVBALTICOM-NETWORK-4647-R	"Balticom" JSC	ASSIGNED PA	Dec 18, 2015	abuse@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

Announcement Routing history RPKI & IRR Whois & 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

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
46.23.32.0/20	AS24651	/32	RIPE	RPKI valid

IRR

Route objects on 46.23.32.0/20

Origin	Registry	Description	Maintainer	Modified
AS24651	RIPE	LVBALTICOM-NET	LVBALTICOM-MNT	Jun 28, 2011