Mattias Lindstrom is a registry contact for AS210409 with no independent public verification of his current role or employer. The profile relies solely on RIPE database records and RIPEstat, establishing a narrow administrative association without proven ownership or operational control. The main uncertainties are stale data, lack of routing activity, and absence of corroborating web sources. Watchpoints include registry record changes, new prefix announcements, and external confirmation such as a LinkedIn profile. The profile must be read as a monitoring baseline, not as a claim of current authority.

Mattias Lindstrom

Mattias Lindstrom appears in the RIPE registry as an administrative contact for autonomous system AS210409 (Skylite-AS). The listing provides a named point of contact for network coordination, but no independent public evidence verifies his employer, title, or operational role. The profile is a registry-holding baseline, not a claim of current authority.

Why It Matters

Network operators and abuse teams may direct inquiries to Lindstrom based on the RIPE listing. If the data is inaccurate, those communications can delay routing repairs, abuse mitigation, or legal inquiries. The observable impact remains low while AS210409 has no public routing activity, but it would rise if the network becomes operational.

What Public Sources Show

Mattias Lindstrom appears in the RIPE registry as an administrative contact for autonomous system AS210409, which carries the name Skylite‑AS. The listing is a registry pointer, not proof of employment or operational control, and no independent public source confirms his current role or employer.

A named contact in an ASN record influences how outside operators route coordination, abuse complaints, and legal inquiries. If the registry entry is stale or inaccurate, those communications reach the wrong destination, potentially delaying incident response or creating confusion about network responsibility.

The RDAP record for AS210409 shows Lindstrom’s RIPE handle MALI12‑RIPE with the role “admin.” RIPEstat confirms the ASN exists in the RIPE‑coordinated space but shows no announced prefixes. The same registry entry lists additional contacts—Leif Haggstrom, Thomas Nilsson, and Lukas Strom—spreading responsibility across at least three other named individuals.

The sole public operating surface is the RIPE database entry. Through it, Lindstrom can receive emails and inquiries directed at the ASN. No corporate website, PeeringDB record, or official organizational document corroborates his affiliation or identifies the legal entity behind Skylite‑AS.

If the registry data remains current, network operators, abuse teams, and law enforcement may treat Lindstrom as the first point of escalation. Because AS210409 has no observed BGP activity, that potential impact stays theoretical until the network becomes operational. The practical consequence depends entirely on the ongoing accuracy of a single database record.

No independent web source confirms Lindstrom’s employer, title, or career history. The person behind the handle could have left the entity that registered the ASN years ago. Without external verification—a LinkedIn profile, a corporate staff page, or a company registration—every field beyond the registry handle is unconfirmed.

Three observable changes would reshape the assessment: a modification of the RIPE object that removes or alters Lindstrom’s role; any prefix announcement from AS210409; and discovery of a professional profile or public document linking the handle to a real organization. Until one occurs, the profile remains a narrow registry‑contact monitoring baseline rather than a claim of current authority.

Operating Surface

He is listed solely as an admin contact on the AS210409 RDAP record under handle MALI12-RIPE. This positions him as a potential point of contact for matters related to the autonomous system, yet it does not prove management, ownership, or technical control of the network. The role is a registry function, not a verified employment relationship.

A named person in an ASN registry record can influence how outside operators, investigators, or counterparties route coordination, abuse escalation, and infrastructure attribution. Public registry evidence identifies Lindstrom in connection with AS210409; tracking that data helps maintain accurate dependency mapping and avoids misdirected communications if the record becomes stale.

Watchpoints

Lindstrom’s registry entry creates a potential attribution point for AS210409, but the absence of routing activity and any corroborating source suggests the record may be stale or the entity inactive. Treat as a weak signal until externally confirmed.

Observe RDAP and RIPEstat for changes to the contact record; monitor BGP for any prefix announcements from AS210409; search for a LinkedIn profile or corporate affiliation that ties the handle to a real organization.

No company website, employment record, or personal biography exists outside the RIPE database. The legal entity behind Skylite-AS is unknown. No routing history confirms the network is operational.

Sources

• Registry RDAP / WHOIS record - Public-source identity and registry context for Mattias Lindstrom; shows handle MALI12-RIPE and admin role.
• RIPE registry record - RIPEstat provides a public overview page for AS210409, corroborating that the ASN exists in RIPE-coordinated number resource context.