Data as of Nov 15, 2026

176.221.30.0/23

1 residential-proxy exit · 30 days

JSC 'Severen-Telecom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

80 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.221.28.0/22
since May 2026
AS24739Business7JSC "Severen-Telecom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.221.16.0/204,096RU-SEVEREN-20111125JSC "Severen-Telecom" (ORG-SL18-RIPE) · RUALLOCATED PADec 24, 2025abuse@severen.net
└ 176.221.28.0/221,024SEVEREN-B2B-SPB-NETunknownASSIGNED PAMay 18, 2026abuse@severen.net
via RU-SEVEREN-20111125

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Rotating
First seen
Oct 2023
Current origin since
Apr 2026 · 7 mo
Origin networks
5
Last change of origin
Apr 2026
Recorded history

History

Handoffs
4