Data as of Nov 14, 2026

176.221.16.0/22

2 residential-proxy exits · 30 days

JSC 'Severen-Telecom'

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

Residential-proxy exits

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

Exits seen per day

128 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
176.221.18.0/2401
176.221.19.0/2401

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • ByteProxies
  • Byteful
  • CROXY
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • Proxy-Seller
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.16.0/221,024SEVEREN-B2B-SPB-NETunknownASSIGNED PAJan 16, 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

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Oct 2023
Current origin since
Jan 2026 · 10 mo
Origin networks
3
Last change of origin
Jan 2026
Recorded history

History

Handoffs
2