Person Profile / Case File

Aleksey Dementiev

A named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.

Aleksey Dementiev

Sources

Public references used for this article.

  • RIPEstat AS210894 overviewRIPEstat identifies AS210894 as DSKOV / JSC DSC and reports it as announced on 27 May 2026. (source risk: low)
  • RIPEstat AS210894 routing statusRIPEstat routing-status data shows one visible IPv4 route, 95.66.198.0/23, no visible IPv6 space and two observed neighbours on 27 May 2026. (source risk: low)
  • RIPE Database query for AD17360-RIPEThe RIPE person record identifies Aleksey Dementiev as a public registry contact handle in the AS210894 evidence chain. (source risk: low)
  • RIPE Database query for ORG-JD116-RIPEThe RIPE organisation record links ORG-JD116-RIPE to JSC DSC. (source risk: low)
  • IP2Location AS210894 summaryIP2Location identifies AS210894 as JSC DSC in Russia, with 95.66.198.0/23, 512 IPv4 addresses, no IPv6 and MTS/Vladinfo upstream visibility. (source risk: low)
  • IPinfo AS210894 summaryIPinfo identifies AS210894 as JSC DSC, with 512 IPv4 addresses, no IPv6, and MTS/Vladinfo upstream or peer visibility. (source risk: low)
CategoryPerson

A named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.

RegionRussia

The person handle gives a compact Russian routing footprint a public accountability point without proving corporate control.

Signal FocusAS210894 registry accountability

The person handle gives a compact Russian routing footprint a public accountability point without proving corporate control.

Content TypePROFILE

A named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.

Primary DomainInfrastructure

AS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.

TopicAS210894 registry accountability

Aleksey 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.

ImpactMedium

AS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.

Confidence?Confidence Grade
0.90–1.00AHigh — direct sources
0.75–0.89A/BStrong
0.55–0.74B/CMedium
0.35–0.54C/DWeak–medium
0.10–0.34DWeak signal
0.00–0.09DInternal monitoring
High confidence (88%)

Several public sources

Aleksey 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.

L'enregistrement AS210894 est compact mais inhabituellement lisible. RIPEstat identifie le détenteur comme DSKOV / JSC DSC et signale que l'AS a été annoncé le 27 mai 2026. Sa vue d'état de routage montre une seule route IPv4 visible, 95.66.198.0/23, vue par 326 des 326 pairs RIS, sans espace IPv6 annoncé visible. Voir aussi: L'UE réécrit les règles de souveraineté de l'infrastructure IA.

Le rôle public de Dementiev est plus étroit qu'un titre de poste. Les enregistrements RIPE placent le handle de personne AD17360-RIPE dans le fichier AS210894 et la piste d'organisation JSC DSC. Cela étaye une lecture de responsabilité de registre: il est un contact public nommé lié à l'enregistrement de ressource réseau, mais les preuves publiques ne prouvent pas la propriété de l'entreprise, l'autorité exécutive ou le contrôle pratique du routage. Voir aussi: La FCC soutient les constructeurs de fibre avec des limites de permis.

Les dépendances réseau sont également limitées. IP2Location et IPinfo décrivent AS210894 comme un réseau russe JSC DSC avec 512 adresses IPv4 et aucune allocation IPv6 dans leurs résumés; tous deux identifient MTS PJSC et Limited Liability Company Vladinfo comme visibilité en amont ou de pair. Un changement de mainteneur, un nouveau préfixe, un changement en amont ou le remplacement du handle de personne nommée importeraient donc plus que des changements ordinaires de description d'entreprise. Voir aussi: Ofcom révèle les lacunes de couverture mobile sur les trains britanniques.

Area of expertise

Aleksey 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.

  • Role evidence: Aleksey Dementiev is framed by a named public ripe contact in the jsc dsc / as210894 registry-accountability trail. and public infrastructure context. Evidence basis: RIPEstat AS210894 overview; RIPEstat AS210894 routing status
  • Operating context: AS210894 registry accountability and Russia provide the public context for this person profile. Evidence basis: RIPEstat AS210894 overview; RIPEstat AS210894 routing status

Timeline

  1. Aleksey Dementiev public profile updated

    Public coverage records Aleksey Dementiev as a subject for role, operating context, and evidence review.

Role and Scope

  • Profile: Aleksey Dementiev
  • Current Role: A named public RIPE contact in the JSC DSC / AS210894 registry-accountability trail.
  • Analytical Category: Person
  • Why tracked: The person handle gives a compact Russian routing footprint a public accountability point without proving corporate control.

Signal Map

  • AS210894 is small, but maintainer, upstream or contact changes would directly alter the public accountability surface around the announced IPv4 /23.
  • Decision horizon: Longer term
  • Operational relevance: Medium
  • Relevant activities: AD17360-RIPE, JSC DSC, AS210894, 95.66.198.0/23

Member Briefing

Deeper Profile Context

Login is required to unlock the full profile briefing and source notes.

Only for Strategy Circle

Strategic Circle Access

Open to all readers. Unlock profile briefings after joining and logging in.

Join Strategic Circle

Only for Leadership Alliance

Leadership Alliance Access

For owners and management of IP-holding companies. Login required to unlock.

Join Leadership Alliance

Public Sources and Linked Organizations

OrganizationLinkRelated organizationConfidenceWhy it mattersSourceCaveat
Aleksey Dementievregistry contact forJSC DSCGoodAleksey Dementiev AS210894 registry contact observedThe RIPE person record identifies Aleksey Dementiev as a public registry contact handle in the AS210894 evidence chain.Low risk, public source

Public View

The public read of Aleksey Dementiev is limited to visible role, operating context, and relationship evidence.

Watchpoints

  • New public role, affiliation, product, policy, or market disclosures.
  • Verified relationship changes involving named organizations or people.

Caveats

  • Private or unverified claims are excluded from this public view.

FAQ

Why is Aleksey Dementiev included?

Aleksey Dementiev has public evidence that makes the person relevant to BTW's coverage of digital infrastructure, governance, or markets.

What is public about this profile?

The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.

What should readers watch next?

Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.

← BackAll People