Data as of Nov 10, 2026

178.238.26.0/24

3 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.2% of its addresses · 30 days

Providers

selling exits here

Oct 11, 2026 – Nov 9, 2026

Exits seen per day

510 observations

Proxy providers listing exits

9Proxy
BestProxy
BottingTools
BuyingProxy
Byteful
Datarama
EnigmaProxy
Evomi
FloppyData
Geonode
IPFly
InfiniteProxies
NSocks
NovaProxy
Oxylabs
Proxiware
ProxyEmpire
ProxyGeo
PuraRoute
ResiProxies
Shifter
Smartproxy

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.26.0/24	256	SeverenNet	Saint-Petersburg p2p clients	ASSIGNED PA	Feb 2, 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