The registration of an AS number grants the holder a foothold in the global routing system. Even without active announcements, the entity could become an operational network at short notice, potentially altering routing topology in Ukraine. Its dormant status also raises the possibility of resource squatting, transfer, or unauthorized activation, making it a watchpoint for infrastructure analysts.
AuteurNikita Jiang
Editorial owner accountable for this profile route.
Temps de lecture3 min
Estimated reading time at standard editorial pace.
Publié leMay 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.
RégionUkraine
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Type de contenuProfile
Structured profile used for cross-category comparison.
Domaine principalInfrastructure
Primary editorial domain framing the analysis.
SujetDigital infrastructure institution
Controlled taxonomy label used for this profile route.
HorizonQuarter (30-120d)
Most likely window for material strategy effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confiance0.70
Multi-source inference with primary-source anchors.
Dossier de preuves
Sources primaires utilisées pour la classification et l'évaluation d'impact.
FDN3 FOP Dmytro Nedilskyi is a Ukrainian sole proprietorship holding dormant AS211736. Public registry records confirm the assignment, but no BGP prefixes are announced. The entity's operational intent is unknown, and no individual contacts are identified. The primary risk is dormant activation, which could introduce new routing paths or hijacks. Watchpoints: registry record changes, first prefix announcement, new PeeringDB or website evidence. Evidence boundary: only RIPE NCC registry data and announced-prefix absence are source-backed.
Core Entity Brief
Core Entity Brief
Entity
FDN3 FOP Dmytro Nedilskyi
Public role
The registration of an AS number grants the holder a foothold in the global routing system. Even without active announcements, the entity could become an operational network at short notice, potentially altering routing topology in Ukraine. Its dormant status also raises the possibility of resource squatting, transfer, or unauthorized activation, making it a watchpoint for infrastructure analysts.
Region
Ukraine
Category
Digital infrastructure institution
Primary domain
Infrastructure
Signal focus
Institution Type
Time horizon
Quarter (30-120d)
Impact
Medium
Confidence
0.70
Evidence coverage
3 public source references
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 02, 2026
FDN3 FOP Dmytro Nedilskyi is a Ukrainian sole proprietorship holding dormant autonomous system AS211736; its public footprint is limited to RIPE NCC registry records.
What It Does
Visible operating role: The entity holds AS211736 but does not announce any IP prefixes or operate visible internet services, making the autonomous system dormant.
Revenue and customer gap: No public evidence shows a revenue model, customer base, or contracts; the sole proprietorship's business intent remains unknown.
Operating Snapshot
Identity baseline: FDN3 FOP Dmytro Nedilskyi is listed as the holder of AS211736 in the RIPE NCC registry, with a name pattern consistent with a Ukrainian sole proprietorship (FOP).
Routing context: Zero BGP prefixes are currently announced by AS211736, so the AS is not participating in global routing.
Control Surface
Numbering records: Control is exercised through RIPE NCC database objects for AS211736, including maintainer objects, contact details, and route objects. This administrative access could allow the holder to originate IP prefixes and establish BGP peerings if activated.
Evidence changes: New announcements, withdrawals, or reassigned prefixes would alter the entity's operational significance. Changes to RDAP or WHOIS records could signal a transfer or intention to activate.
Watchpoints
Record freshness: Outdated or altered RIPE NCC records are the primary source of uncertainty; monitoring for changes in org-name, maintainer, or contact fields is essential.
Footprint change: Any new ASN acquisition, prefix announcement, website, or PeeringDB entry would significantly raise the entity's infrastructure relevance and trigger a reassessment.
ROA posture: The RPKI/ROA status is unconfirmed. If the AS becomes active, verifying ROA coverage will be critical to evaluate routing security; the absence of confirmed data is a watchpoint.
Domain of operation
The registration of an AS number grants the holder a foothold in the global routing system. Even without active announcements, the entity could become an operational network at short notice, potentially altering routing topology in Ukraine. Its dormant status also raises the possibility of resource squatting, transfer, or unauthorized activation, making it a watchpoint for infrastructure analysts.
Public role: FDN3 FOP Dmytro Nedilskyi is framed by the registration of an as number grants the holder a foothold in the global routing system. even without active announcements, the entity could become an operational network at short notice, potentially altering routing topology in ukraine. its dormant status also raises the possibility of resource squatting, transfer, or unauthorized activation, making it a watchpoint for infrastructure analysts. and public infrastructure context. Evidence basis: Internet registry record; Registry RDAP / WHOIS record
Operating surface: Digital infrastructure institution and Ukraine provide the public context for this institution profile. Evidence basis: Internet registry record; Registry RDAP / WHOIS record
Timeline
FDN3 FOP Dmytro Nedilskyi public profile updated
Public coverage records FDN3 FOP Dmytro Nedilskyi as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: The registration of an AS number grants the holder a foothold in the global routing system. Even without active announcements, the entity could become an operational network at short notice, potentially altering routing topology in Ukraine. Its dormant status also raises the possibility of resource squatting, transfer, or unauthorized activation, making it a watchpoint for infrastructure analysts.
Object role: FDN3 FOP Dmytro Nedilskyi controls the registration of AS211736 through RIPE NCC maintainer objects, giving it the administrative capability to originate IP prefixes, establish BGP peerings, and participate in global routing. Currently, no activity is observed, so its role is confined to registry-level resource holding with no publicly visible operating surface.
Impact note: If AS211736 becomes active, it could inject routes into BGP, influence traffic paths, and create new connectivity dependencies that require monitoring. In its current dormant state, the impact is limited to the registry footprint itself, but any change in records, contacts, or routing posture would shift the assessment and could affect routing security in the RIPE NCC service region.
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 FDN3 FOP Dmytro Nedilskyi 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 FDN3 FOP Dmytro Nedilskyi included?
FDN3 FOP Dmytro Nedilskyi 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.
