MOONYHOST-NET Gabriel Engvall

Gabriel Engvall is a person name attached to AS202817 and the MOONYHOST-NET tag in public routing registries. The evidence base includes a CIDR report, bgp.tools tag, and IPGeolocation listing, but no primary operator site, biography, or corporate record confirms his role. A stale bgp.tools page shows the ASN previously belonged to FIBRACAT Telecom, raising the possibility of reassignment. The profile must operate within these thin registry facts; any operational dependency should wait for a direct confirmation source. Key watchpoints: the appearance of a Moonyhost website, registry record updates, new prefix announcements.

MOONYHOST-NET Gabriel Engvall

Gabriel Engvall is a person name linked to AS202817 and the MOONYHOST-NET label in public routing registries. The evidence is thin and contradicted by an older FIBRACAT Telecom registration, leaving his actual operating authority unverified.

Why It Matters

If Gabriel Engvall does control AS202817, changes to its upstream connections or announced prefixes could affect peer trust for a small network. The conflicting FIBRACAT record suggests the ASN may have been reassigned, diluting any current operator signal.

What Public Sources Show

Gabriel Engvall is a person name tied to autonomous system 202817 and the MOONYHOST-NET label. Public routing registries show the ASN active with a single route, but no primary proof confirms Engvall actually runs a network or company. For analysts mapping Sweden's internet infrastructure, this thin identity is a puzzle that requires monitoring rather than immediate trust.

The CIDR Report of 29 May 2026 lists AS202817 as 'MOONYHOST-NET - Gabriel Engvall, SE' with one route.

BGP.tools tags the ASN as a personal or hobby system, while IPGeolocation's Sweden ASN list shows it with zero prefixes. However, a bgp.tools AS page last updated in October 2025 displays a contradictory record: the same ASN belonged to FIBRACAT Telecom in Spain, with no prefixes and not in the global routing table. No operator website, PeeringDB entry, or company registration independently links Engvall to Moonyhost operations.

Public searches found no biography, LinkedIn profile, or employment record confirming his role.

The only verifiable facts are the ASN registration and third-party routing snapshots, which exist without corroborating corporate context. Engvall's observable control surface is limited to the AS202817 registration: the AS name in the registry, its appearance in routing reports, and a few directory labels.

There are no announced prefixes in the current evidence set, meaning the ASN's operational footprint is effectively invisible except for the one route entry in the CIDR Report.

Without a direct relationship to upstream providers or customers, the network's function remains a guess. A future primary source—an operator website, a PeeringDB profile, or a social media post from Engvall—would either confirm or refute his network role. Changes to the AS202817 WHOIS record or RIPE database entry, particularly a shift back to FIBRACAT or another holder, would clarify ownership.

The appearance of new prefixes or BGP announcements would signal an active network, raising its relevance for traffic and trust maps.

Because the evidence is registry-thin and conflicting, readers should treat 'MOONYHOST-NET Gabriel Engvall' as a contact label rather than a confirmed operator. Any decision relying on this person's authority—such as peering or security assessment—must wait for more than a name in a routing report.

Operating Surface

Gabriel Engvall appears as the registrant contact for AS202817 under the MOONYHOST-NET label according to CIDR and bgp.tools sources. No independent website, employer, or role title confirms him as a network operator or business representative.

Analysts monitoring the Swedish internet segment need to understand whether AS202817 and the MOONYHOST-NET label represent a live personal network or historical debris. Changes in registry data or routing could signal a new operational presence or reallocation.

Watchpoints

The MOONYHOST-NET Gabriel Engvall entity is a low-confidence registry signal, not an actionable operational contact. The conflicting FIBRACAT record raises the possibility of ASN reassignment, meaning that any current routing association may be transient or misattributed. Until a primary confirmation surface appears, the strategic priority is to avoid over-reliance on this label for network dependency mapping or trust decisions.

1. A new primary website or self-published page for Moonyhost or Engvall that confirms network operations. 2) RIPE database updates for AS202817 that change the holder name or contact details. 3) BGP announcements or PeeringDB entries for AS202817 that show active routing. 4) Any public association between Engvall and a known organisation (employment, conference talk, or social media profile).

Key gaps include: no primary organisational URL, no biographical or career data for Gabriel Engvall, no financial or commercial records for Moonyhost, and no technical footprint beyond the ASN registration. The source set relies entirely on third-party routing directories, which can lag or carry stale entries.

Sources

• Internet registry record - public-source identity and registry context for MOONYHOST-NET Gabriel Engvall.
• cidr-report.org - CIDR Report generated on May 29, 2026 lists AS202817 as MOONYHOST-NET - Gabriel Engvall, SE and shows it as a one-route entry in current routing-table reporting.
• bgp.tools - bgp.tools Personal ASN tag page includes AS202817 Gabriel Engvall and defines the tag as a personal or very small-group ASN used for hobby, education, or infrastructure-niche purposes.
• ipgeolocation.io - IPGeolocation's Sweden ASN country list includes AS202817 Gabriel Engvall, SE with zero IPv4 and zero IPv6 routes in its displayed table.
• bgp.tools - bgp.tools AS202817 page last updated on October 4, 2025 shows conflicting older context: FIBRACAT Telecom, S.L.U., ALTECOM-AS, Spain, zero prefixes, and not currently in the global routing table.
• RIPE registry record - RIPE Database documentation explains that AUT-NUM entities contain ASN registration details and routing policy, supporting use of ASN records as evidence rather than as the person entity itself.