RMDC RMDC B.V.

RMDC RMDC B.V. is a dormant holding entity for AS211728 in the RIPE NCC registry, with no active routing, no public services, and no identifiable individuals. The evidence boundary is narrow: two official RIR sources confirm the organization name and the absence of prefix announcements. Business purpose, legal status, and human operators remain unknown. Monitoring is warranted only if registry details change or the ASN begins announcing prefixes; otherwise the entity has zero infrastructure relevance.

RMDC RMDC B.V.

RMDC RMDC B.V. is a registry-visible holder of dormant AS211728, with no active routing, peering, or service footprint. The entity’s role is confined to the RIPE NCC database; it announces no IP prefixes and has no identified website, PeeringDB presence, or IRR entities. Its current impact is zero, but future routing activity could change that, making it a baseline watchpoint for dormant RIR resources.

Why It Matters

Currently, the entity has no observable impact on internet routing. Its impact is contingent on future activation. Until then, it serves as a reference point for analysts scanning registry changes that could presage shifts in network topology. If it never activates, it remains a placeholder of no operational consequence.

What Public Sources Show

RMDC RMDC B.V. is an organisation registered in the RIPE NCC database as the holder of autonomous system number AS211728. Its name suggests a Dutch private limited company, though no corporate registration has been independently verified. At present, the ASN is dormant: it announces no IP prefixes in the public BGP table, giving the entity no observable impact on internet routing.

The evidence base consists of two official RIR sources. The RIPE NCC AS overview for AS211728 lists RMDC RMDC B.V. as the holder and confirms the absence of active prefix announcements. An RDAP query for the same ASN shows the organisation name but provides no additional contact or routing details. No public website, PeeringDB entry, AS-SET, or aut-num IRR entity has been identified in the available public sources.

The entity’s operating surface is limited to the RIPE NCC registry entry. There are no associated IP prefixes, contact persons, or external service links present in that record. If the ASN were to begin announcing prefixes in the future, it could influence internet traffic paths for those prefixes, but such activity has not been observed.

Several watchpoints would change the assessment. Any future BGP announcements, withdrawals, or reassigned prefixes attached to AS211728 would signal operational activity. Changes to the registry record—such as new contacts, associated prefixes, or status changes—would alter the public baseline. Discovery of a public website, PeeringDB listing, or IRR entity would expand the profile.

Significant gaps remain. The entity’s full corporate identity, business purpose, and human operators are unknown. No published contact points or named individuals have been surfaced in the available registry evidence. The legal status implied by the ‘B.V.’ suffix has not been confirmed through a Dutch Chamber of Commerce record.

Readers should treat this profile as a snapshot based on a narrow evidence window; it is not a definitive statement about what the entity has or has not created.

Operating Surface

The entity holds autonomous system number AS211728 in the RIPE NCC registry but does not announce any prefixes in the public BGP table. Its public role is limited to the registry record, with no confirmed operational network services, no known human operators, and no verified corporate presence beyond the registration.

It matters as a potential future routing policy node: if AS211728 becomes active and announces prefixes, it could influence internet traffic paths. Tracking it provides a reference point for tracking dormant resources in the RIR ecosystem that may later materialize as operational infrastructure, and changes would signal shifts in network topology or ownership.

Watchpoints

RMDC RMDC B.V. represents the class of dormant RIR resources that could shift from registry placeholder to operational actor with a single BGP announcement. Its strategic relevance lies not in current activity but in the potential for abrupt change that would alter the observable topology. Analysts should treat it as a leading indicator for policy or ownership shifts in the RIPE region.

Immediate watchpoints are BGP prefix announcements by AS211728, changes to the RDAP or WHOIS record including new contacts or associated prefixes, and the appearance of a public website, PeeringDB entry, or IRR aut-num entity. Any of these would change the assessment from dormant to operational, requiring a profile rewrite.

Key gaps include the absence of a confirmed corporate registration, no identified human operators, and no insight into the entity's business model or funding. The 'B.V.' suffix remains unverified against the Dutch Chamber of Commerce. Without these, the entity's intent and control structure are opaque.

Sources

• Internet registry record - public-source identity and registry context for RMDC RMDC B.V..
• Registry RDAP / WHOIS record - evidence-led registry, routing, or network context for RMDC RMDC B.V..