Thomas Sloth

Thomas Sloth is the administrative and technical contact for AS210322 per RIPE registry records, with affiliation to FIBIA P/S. The evidence is limited to three public registry sources; no employer verification, current title, or routing visibility exists. The profile serves as a contact baseline and uncertainty marker for operational dependency mapping.

Thomas Sloth

Thomas Sloth is identified in RIPE NCC public registry records as the administrative and technical contact for AS210322, an autonomous system registered to the Danish company FIBIA P/S. The profile outlines the narrow registry contact surface, the operational dependency signal it provides, and the significant gaps in verifying his actual employment, authority, and current role.

Why It Matters

The impact of public signals about Thomas Sloth is operational and reputational: changes to his registry contact listing could indicate a shift in technical stewardship or administrative control of AS210322. Conversely, the absence of employer verification means the contact record may be stale or purely administrative, limiting the reliability of the signal.

What Public Sources Show

Thomas Sloth is the registered administrative and technical contact for autonomous system AS210322 in the RIPE NCC public registry. The autonomous system belongs to the Danish company FIBIA P/S, but the profile is built entirely from registry records and does not independently verify Thomas Sloth’s employment, job title, or decision-making authority. This profile explains the narrow registry contact surface that the evidence supports and the operational dependency signal it provides.

The public evidence rests on three sources. An RDAP query for AS210322 shows Thomas Sloth listed with admin and tech contact roles. A RIPEstat overview confirms that the autonomous system is registered to FIBIA P/S, placing the contact in an organisation context. A RIPE Database lookup for the entity handle TS40490-RIPE returns a public record that connects the named person to that registry entry.

No corporate biography, employer page, or independent professional profile for Thomas Sloth was found among the supplied sources.

In the context of internet number resource management, a registry contact is more than a passive entry. Network operators, researchers, and counterparties use these records to identify responsible parties for routing coordination, abuse escalation, and technical stewardship. When the same named contact persists in registry data, it can serve as a continuity signal for the operational team behind a network.

A change, removal, or long-term staleness can similarly raise questions about the current administrative reality.

The operating surface for Thomas Sloth is therefore limited to the authority granted by the registry record itself—the ability to be publicly referenced as a technical or administrative point of contact for AS210322. There is no public evidence that he holds a formal executive role, owns the autonomous system, or controls the organisation’s infrastructure beyond what a standard registry contact normally implies.

Without an active prefix sample or routing table entry, the observable footprint attached to this contact remains entirely within the registry domain.

The main uncertainty is whether the record reflects a current, active relationship or a historical entry that has not been updated. Registry records can be stale, inherited from previous staff, or used for purely administrative compliance without signifying day-to-day operational involvement.

No independently verified employer documentation or professional biography is available in the provided evidence, so readers should treat the contact listing as a signal rather than a confirmed statement of current responsibility.

Key watchpoints that would change this assessment include: any alteration to the RDAP or RIPE database records for AS210322—particularly if Thomas Sloth is removed or replaced as a contact; the emergence of active prefix announcements under AS210322, which would provide routing-based evidence of the autonomous system’s operations; and independent employer verification through a corporate website, professional network profile, or official document that confirms Thomas Sloth’s role at FIBIA P/S.

Until such evidence appears, the profile remains a registry-only reference point.

Operating Surface

Thomas Sloth appears in public RDAP and RIPE database pages as a named contact for internet number resource registration. The current evidence assigns him admin and tech contact roles for AS210322, but does not independently confirm a formal job title, employer relationship, or broader network-operations responsibility beyond what the registry entry states.

A named administrative and technical contact in a public registry can influence how network operators, researchers, and counterparties identify the responsible party for routing, abuse escalation, and infrastructure coordination. Monitoring the continuity of Thomas Sloth's registry listing helps map operational responsibility and dependencies around AS210322 and its associated resources.

Watchpoints

Thomas Sloth represents a single-point registry contact reference for AS210322, a small Danish autonomous system. The contact signal is useful for operational dependency mapping, but its reliability is undermined by the absence of employer verification or routing evidence. Analysts should treat the contact listing as a baseline and watch for changes that could indicate operational handovers or administrative updates.

The key public signals to track are: alterations to the AS210322 contact records in RIPE NCC databases; the appearance of prefixes announced by AS210322, which would provide routing-based evidence of active operations; and any independent employer documentation (e.g., corporate website, professional profile) confirming Thomas Sloth’s current role at FIBIA P/S or another network operator.

The evidence lacks an employer biography, corporate profile, or professional network listing for Thomas Sloth. No public source establishes a formal job title or current employment status. Additionally, no active prefix announcements are present, so the profile cannot confirm that AS210322 is currently routing traffic. These gaps prevent a confident assessment of Thomas Sloth’s operational authority or the timeliness of the registry record.

Sources

• Registry RDAP / WHOIS record - Public RDAP record lists Thomas Sloth as admin and tech contact for AS210322.
• RIPE registry record - RIPEstat identifies AS210322 as belonging to FIBIA P/S, providing organisation context for the registry contact record.
• RIPE registry record - RIPE Database search result confirms the entity handle TS40490-RIPE for Thomas Sloth.