Data as of Nov 13, 2026

178.57.110.0/24

3 residential-proxy exits · 30 days

Sever Telecom JSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
27
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

728 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.57.104.0/21
since Sep 2024
AS61403Residential137
68 always on
Sever Telecom JSC
178.57.96.0/20
since May 2021
AS61403Residential363
131 always on
Sever Telecom JSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.57.96.0/198,192RU-SEVERTEL-2010202Sever Telecom JSC (ORG-ZL27-RIPE) · RUALLOCATED PADec 23, 2014seleznev.rv@severtm.ru
└ 178.57.96.0/204,096SEVER-TELECOM-NET01unknownASSIGNED PAJun 21, 2016seleznev.rv@severtm.ru
via RU-SEVERTEL-2010202

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

178.57.108.0/22

Routing history

Pattern
Stable
First seen
Feb 2022
Current origin since
Mar 2026 · 8 mo
Origin networks
1