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.

El registro de AS210894 es compacto pero inusualmente legible. RIPEstat identifica al titular como DSKOV / JSC DSC e informa que el AS se anunció el 27 de mayo de 2026. Su vista de estado de enrutamiento muestra una única ruta IPv4 visible, 95.66.198.0/23, vista por 326 de 326 pares RIS, sin espacio IPv6 anunciado visible. Ver también: La UE reescribe las reglas de soberanía de la infraestructura de IA.

El papel público de Dementiev es más reducido que un cargo laboral. Los registros RIPE sitúan el identificador de persona AD17360-RIPE en el expediente de AS210894 y en el rastro organizativo de JSC DSC. Esto respalda una lectura de responsabilidad de registro: es un contacto público designado vinculado al registro de recursos de red, pero la evidencia pública no prueba la propiedad corporativa, la autoridad ejecutiva ni el control práctico del enrutamiento. Ver también: La FCC respalda a los constructores de fibra con límites de permisos.

Las dependencias de red también están acotadas. IP2Location e IPinfo describen AS210894 como una red rusa de JSC DSC con 512 direcciones IPv4 y sin asignación IPv6 en sus resúmenes; ambos identifican a MTS PJSC y a la Sociedad de Responsabilidad Limitada Vladinfo como visibilidad de proveedor ascendente o par. Por lo tanto, un cambio de mantenedor, un nuevo prefijo, un cambio de proveedor ascendente o la sustitución del identificador de persona designado serían más relevantes que los cambios ordinarios en la descripción de la empresa. Ver también: Ofcom expone la brecha de cobertura móvil en los trenes del Reino Unido.

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