BTW.Media
Strategic Internet IntelligenceJun 06, 2026
Sign InRegister
Back to Companies Desk›Dmitry E Kiselyov
Technology market and infrastructure profile visual with growth structure.
Reference visual: company and capital context snapshot.

Company Briefing / Digital infrastructure institution

By a.tang@btw.media MARKET EDITOR

Dmitry E Kiselyov

Dmitry E Kiselyov is tracked because the handle DEK-RIPE could influence registry matters for AS210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring.

Authora.tang@btw.media

Editorial owner accountable for this profile route.

Reading Time3 min

Estimated reading time at standard editorial pace.

PublishedMay 26, 2026

Date this profile last entered editorial circulation.

Last updateJun 02, 2026

Date this profile last entered editorial circulation.

CategoryDigital infrastructure institution

Controlled classification used for cross-profile comparison.

RegionEurope/RIPE region

Primary geography where current signals are most visible.

Signal FocusInstitution Type

Principal area tracked in this intelligence profile.

Content TypeProfile

Structured profile used for cross-category comparison.

Primary DomainInfrastructure

Primary editorial domain framing the analysis.

TopicDigital infrastructure contact

Controlled taxonomy label used for this profile route.

Time HorizonQuarter (30-120d)

Most likely window for material strategy effects.

ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confidence0.95

Anchored to multiple primary-source references and direct disclosures.

Evidence Pack

Primary-source references used for classification and impact scoring.

Context

Dmitry E Kiselyov is the RIPE registry contact handle DEK-RIPE for silent AS210928. No employer, location, or operational activity ties to the name. The control surface is limited to registry communications and contact updates; there is no evidence of authority over BGP routing or network infrastructure. The profile is low-confidence and will remain so until routing activation, identity confirmation, or registry record changes appear. Watchpoints monitor registry state, ASN activity, and any real-world identity link.

Core Entity Brief

Core Entity Brief

EntityDmitry E Kiselyov
Public roleDmitry E Kiselyov is tracked because the handle DEK-RIPE could influence registry matters for AS210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring.
RegionEurope/RIPE region
CategoryDigital infrastructure institution
Primary domainInfrastructure
Signal focusInstitution Type
Time horizonQuarter (30-120d)
ImpactMedium
Confidence0.95
Evidence coverage3 public source references
Related coverageProfile anchor article
WebsitePublic evidence pending
Last updateJun 02, 2026

Dmitry E Kiselyov appears in external numbering or routing evidence for AS210928; the public assessment is bounded by that source-backed context.

What It Does

  • Visible operating role: The subject acts as the designated admin and tech contact for AS210928 in the RIPE Database, handling registry-related communications without verified commercial, operational, or routing activity.
  • Revenue and customer gap: No supplied evidence establishes a revenue model, customer base, or contract position; those claims need official, financial, or service-source support before publication.

Operating Snapshot

  • Identity baseline: Dmitry E Kiselyov is listed as the administrative and technical contact for autonomous system AS210928 in the RIPE Database, identified by the RIPE handle DEK-RIPE. Public evidence does not confirm that this name represents an institution, a company, or an individual with verified operational authority beyond the registry listing.
  • Routing context: No active prefix sample is present in the current evidence set, so the public assessment is limited to ASN identity until routing evidence changes.

Control Surface

  • Numbering records: Control is limited to the registry-contact entry for AS210928. The subject can receive and potentially update contact details through the RIPE Database interface. There is no evidence of authority over network infrastructure, routing policies, or prefix announcements.
  • Evidence changes: New announcements, withdrawals, or reassigned prefixes attached to AS210928 can change how much operational significance readers should assign to Dmitry E Kiselyov.

Watchpoints

  • Record freshness: Stale, conflicting, or changed public records are the main uncertainty when translating source evidence into an operating profile.
  • Footprint change: New ASN, prefix, official website, PeeringDB, or registry evidence would raise or lower Dmitry E Kiselyov's infrastructure relevance.

Domain of operation

Dmitry E Kiselyov is tracked because the handle DEK-RIPE could influence registry matters for AS210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring.

  • Public role: Dmitry E Kiselyov is framed by dmitry e kiselyov is tracked because the handle dek-ripe could influence registry matters for as210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; bgp.he.net
  • Operating surface: Digital infrastructure contact and Europe/RIPE region provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; bgp.he.net

Timeline

  1. Dmitry E Kiselyov public profile updated

    Public coverage records Dmitry E Kiselyov as a subject for role, operating context, and evidence review.

Signal Map

Signal Map

  • Why tracked: Dmitry E Kiselyov is tracked because the handle DEK-RIPE could influence registry matters for AS210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring.
  • Object role: The subject is listed in RIPE public records as admin/tech contact for AS210928, granting the holder the ability to receive registry correspondence and potentially update contact details, but without demonstrated control over network operations or BGP announcements.
  • Impact note: Currently, the subject has minimal routing impact due to no active BGP prefixes; however, if the registry record is authentic, the contact could facilitate resource transfers or updates, and activation of AS210928 would increase the infrastructure dependency risk.
  • Control surface: public operating records, official service pages, source-backed relationship updates
  • Key dependencies: official company sources, public registries, operator-published records

Public View

The public read of Dmitry E Kiselyov 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 Dmitry E Kiselyov included?

Dmitry E Kiselyov has public evidence that makes the institution 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.

Actions

Back to Companies DeskBack to Front Page