LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

85.235.200.0/22

2 residential-proxy exits · 30 days

JSC 'Severen-Telecom'

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

Residential-proxy exits

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

Exits seen per day

71 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • EZProxies
  • Evomi
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • ResiProxies
  • Shifter
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.235.192.0/19
since Nov 2008
AS35000Internet provider32
4 always on
JSC "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
85.235.192.0/198,192RU-SEVEREN-20050513JSC "Severen-Telecom" (ORG-SL18-RIPE) · RUALLOCATED PAMay 13, 2005abuse@severen.net
└ 85.235.200.0/221,024SEVEREN-B2B-MSK-NETunknownASSIGNED PAJun 27, 2007abuse@severen.net
via RU-SEVEREN-20050513

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Reactivated
First seen
May 2007
Current origin since
Oct 2023 · 3.1 yr
Origin networks
2
Last change of origin
Oct 2023
Recorded history

History

Handoffs
1