Data as of Nov 12, 2026

178.238.28.0/23

8 residential-proxy exits · 30 days

JSC 'Severen-Telecom'

Announcement

178.238.16.0/20

RPKI valid

Announced by

AS24739

Type

Internet provider

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

1.6% of its addresses · 30 days

Always-on exits

38% of its exits

Spread

2 of 2

/24s with at least one exit

Providers

selling exits here

Oct 13, 2026 – Nov 11, 2026

Exits seen per day

8.7K observations

/24s with the most always-on exits

/24	Always-on exits	Proxy exits
178.238.28.0/24	2	4
178.238.29.0/24	1	4

Proxy providers listing exits

2Captcha
Ake.net
BartProxies
BirdProxies
BottingTools
BuyingProxy
ByteProxies
Byteful
CliProxy
Datarama
Decodo
EnigmaProxy
Evomi
FlashProxy
GSocks
Geonix
Geonode
GonzoProxy
IPPeak
Infatica
InfiniteProxies
MangoProxy
NodeProxy
NovaProxy
Oxylabs
Proxiware
Proxy-Seller
ProxyEmpire
ProxyGeo
ProxyHat
Proxyma
RainProxy
Shifter
VantageProxies
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
178.238.16.0/20	4,096	RU-SEVEREN-20100701	JSC "Severen-Telecom" (ORG-SL18-RIPE) · RU	ALLOCATED PA	Jul 1, 2010	abuse@severen.net
└ 178.238.28.0/23	512	SeverenNet	p2p clients	ASSIGNED PA	Feb 24, 2011	abuse@severen.net via RU-SEVEREN-20100701

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

178.238.16.0/20

Routing history

Pattern: Stable
First seen: Jul 2010
Current origin since: Jul 2010 · 16 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
178.238.16.0/20	AS24739	/20	RIPE	RPKI valid

IRR

Route objects on 178.238.16.0/20

Origin	Registry	Description	Maintainer	Modified
AS24739	RIPE	SEVEREN	SEVEREN-MNT	Jul 2, 2010