OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE

OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is tracked from public network records as an institution profile for BTW analyst review. The profile keeps infrastructure resources as evidence and does not promote them into BTW entities. published contact points are separated from person candidates so role mailboxes and teams cannot become people. The export is based on public sources only unless future evidence explicitly raises its validation status. Updates should follow newly published evidence.

OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE

OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is a publicly visible autonomous system number (AS211352) holder listed in RIPE NCC registry data. No website, corporate records, operational contacts, or announced prefixes have been independently verified, leaving only registry and routing‑observation tools as the current public footprint.

Why It Matters

If OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE begins announcing prefixes through AS211352, the entity could influence internet routing reachability and traffic paths for networks that accept routes originated by that ASN. Currently, the impact is potential rather than demonstrated, as no active prefixes, peering agreements, or service dependencies have been observed.

What Public Sources Show

OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is a publicly listed autonomous system number holder recorded in the RIPE NCC registry under AS211352. The entity’s entire public footprint is limited to this registration and its appearance in routing observation tools; no website, corporate filings, operational contacts, announced prefixes, or service offerings have been independently verified.

This scarcity of evidence makes the subject a latent routing actor—one that could gain operational significance if and when it begins originating internet routes, but which currently offers no observable network services.

Public sources provide only a narrow registry‑level picture. A RIPE Stat query for AS211352 confirms the association with the entity name, while the bgp.tools ASN page shows the number in routing observation ecosystems. A PeeringDB search returned no operator profile, further underlining the absence of self‑declared network operations.

Together, these data points support identity and ASN existence, but they stop well short of substantiating any business activities, infrastructure dependencies, or institutional standing.

The operating surface of OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is limited to the autonomous system number itself and its RIPE NCC registry entry. Control of AS211352 empowers the entity to originate internet routes, establish peering relationships, and influence traffic paths for any networks that accept routes announced under that ASN.

However, no active prefix set, NOC contact, or peering agreement has been observed in the public evidence, meaning that this capability remains entirely latent.

The impact mechanism is therefore one of potential rather than demonstrated consequence. If prefixes were to be announced, the entity could affect routing reachability, traffic steering, and dependency mapping for downstream networks. In the absence of such activity, OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE presents a watchpoint rather than a current operational risk.

Analysts should treat any operational claims about the entity with caution until corroborated by fresh routing, registry, or corporate disclosures.

Significant uncertainty surrounds the entity’s legal form and business purpose. The RIPE NCC registry record includes “Tom MARQUAILLE” as part of the trading name, but no independent public record links that name to a verified individual role, let alone to operational decision‑making authority. The lack of a confirmed website, physical address, or published contact points means the entity cannot be reliably located in any jurisdiction.

Without external corroboration, the profile remains anchored to the ASN record alone.

Readers should monitor several observable signals that would alter this assessment. A change in the AS211352 registry record—whether to the holder name, contact details, or status—could indicate a structural shift. The appearance of announced prefixes or the establishment of a PeeringDB profile would mark a transition from latent holder to active operator. Conversely, prolonged silence with no prefix activity would reinforce the image of a dormant registration.

In its current form, OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is a public‑source profile built on minimal but verifiable registry evidence. It serves as a baseline for future infrastructure monitoring rather than a statement about present operational power. The profile will be updated as new public facts become available, in accordance with BTW’s editorial framework that restricts commentary to what can be independently sourced.

Operating Surface

The subject holds autonomous system number AS211352, recorded in RIPE NCC’s registry and visible in routing observation tools such as bgp.tools. Beyond this ASN registration, no services, customers, operational infrastructure, peering relationships, or authoritative published contact points have been confirmed in public sources.

Control of an autonomous system implies the ability to originate internet routes, which can affect routing reachability, traffic paths, and dependency mapping for any networks that accept those routes. OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE is tracked because its ASN provides a latent point of influence, and any future prefix announcements or network activity would change its operational relevance.

Watchpoints

The subject represents a minimal-risk, latent-routing profile that is unlikely to demand immediate action but warrants periodic monitoring because ASN control can escalate quickly if the entity begins advertising prefixes or registers with operator databases.

Monitor RIPE NCC and other IRR records for changes to the AS211352 registrant, contact data, or routing policies. Track BGP monitoring platforms for any prefix announcements originating from AS211352. Watch for the establishment of a PeeringDB profile, an official website, or operational contact disclosures that would indicate a move from dormant to active infrastructure operation.

The entity lacks a verified legal registration, official website, NOC/abuse contacts, announced prefixes, customer dependencies, and any known geography. Filling any of these gaps would significantly raise or lower the profile’s operational relevance; for now the assessment must remain anchored to the ASN alone.

Sources

• Internet registry record - public-source identity and registry context for OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE.
• bgp.tools - Public BGP tooling provides a page for AS211352, supporting that the ASN is visible in public routing-observation ecosystems.
• PeeringDB network profile - PeeringDB search can be used to test whether AS211352 has a public operator record; this helps establish that a public operator profile was not verified from the evidence bundle alone.