CategoryRegional ISPA named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.
RegionRussiaThe person handle gives a compact Russian routing footprint a public accountability point without proving corporate control.
Signal FocusAs210894 Registry AccountabilityA named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.
Content TypeSignal BriefingAS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.
Primary DomainMarketAS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.
TopicAs210894 Registry AccountabilityAleksey Dementiev is not useful here as a biography; he is useful as a named public registry contact in the AS210894 file. RIPE-facing records connect the contact handle AD17360-RIPE to the autonomous system operated for JSC DSC, while RIPEstat reports AS210894 as announced on 27 May 2026 with one visible IPv4 route, 95.66.198.0/23. IP2Location and IPinfo add the same basic network shape: Russia, 512 IPv4 addresses, no IPv6, and upstream exposure through MTS and Vladinfo. The intelligence value is accountability in a small routing footprint where person, organisation, route and upstream changes are easier to monitor than corporate disclosure.
ImpactMediumAS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.
ConfidenceiHigh confidence (88%)Several public sources
The AS210894 record is compact but unusually legible. RIPEstat identifies the holder as DSKOV / JSC DSC and reports the AS as announced on 27 May 2026. Its routing-status view shows a single visible IPv4 route, 95.66.198.0/23, seen by 326 of 326 RIS peers, with no visible IPv6 announced space.
Dementiev's public role is narrower than a job title. RIPE records place the AD17360-RIPE person handle in the AS210894 file and the JSC DSC organisation trail. That supports a registry-accountability reading: he is a named public contact connected to the network-resource record, but the public evidence does not prove corporate ownership, executive authority or hands-on routing control.
The network dependencies are also bounded. IP2Location and IPinfo describe AS210894 as a Russian JSC DSC network with 512 IPv4 addresses and no IPv6 allocation in their summaries; both identify MTS PJSC and Limited Liability Company Vladinfo as upstream or peer visibility. A maintainer change, new prefix, upstream shift or replacement of the named person handle would therefore matter more than ordinary company-description changes.