Edwin Wong is a person listed in RIPE registry data as admin/tech contact for AS210282, operated by Larus Cloud Service Limited. The profile is built entirely from public registry sources, with no independent employer verification, career history, or active prefix evidence. The contact pathway represents a potential control surface for routing coordination. Watchpoints include changes to the RIPE record, prefix announcements, and employer verification.

Edwin Wong

Edwin Wong is publicly listed in RIPE records as an administrative and technical contact for AS210282, an autonomous system originated by Larus Cloud Service Limited. The profile explains the narrow registry-visible operating surface, potential impact on routing coordination, and evidence gaps that limit the assessment.

Why It Matters

If accurate, the registered contact can speed incident response and maintain integrity of routing information for AS210282. If the record is stale or the contact unresponsive, routing incidents may go unresolved, eroding trust among peers and transit providers and complicating threat investigation.

What Public Sources Show

Edwin Wong is listed in public RIPE registry data as the administrative and technical contact for autonomous system AS210282, which is operated by Larus Cloud Service Limited. That registry position creates a potential operating surface over routing resources, but the evidence does not verify employment or exclusive authority.

The RIPE handle EW1323-RIPE ties Wong to the ASN in admin and tech roles. Both RDAP queries and the RIPE web interface confirm the person object, and BGP.tools confirms AS210282 is an active ASN. No independent employer verification, biography, or job title appears in the current public sources.

As a listed contact, Wong can initiate changes to the RIPE entry for AS210282—modifying contact details, submitting routing information, or updating resource records. Peers, transit providers, and threat investigators rely on that data for operational decisions, making the contact pathway a meaningful control point.

The impact sits at the registry layer: accurate contacts improve incident response; stale or incorrect contacts degrade trust. If Wong acts or fails to act on a routing incident or abuse report, the operational footprint of AS210282 could shift. The current evidence bundle contains no active prefixes for the ASN, so the assessment is limited to identity and contactability.

Several gaps bound this profile. There is no independent source linking Wong to a specific employer beyond the registry linkage to Larus Cloud Service Limited. No career history, social profile, or official biography is available. It is not known whether the handle reflects exclusive control or is a role account shared among staff.

Watchpoints include any change to the RIPE database entry for EW1323-RIPE—reassignment or removal would alter the baseline. Appearance of the same handle on additional ASNs would indicate a larger operating footprint. If a corporate website or professional profile confirms employment, the authority assessment should be revised upward.

The main uncertainty is that registry data can be outdated. The person named may no longer hold the role, yet the record persists. Until a first-party employer statement or independent verification surfaces, the profile must stay bounded by the original registry evidence.

Operating Surface

Edwin Wong appears in public RIPE/RDAP registration data as the admin and tech contact for AS210282 under handle EW1323-RIPE. The role covers managing registry updates, responding to network abuse or operational queries, and serving as the public point of contact for that autonomous system, without proven corporate authority.

Edwin Wong matters to BTW readers because a named contact on a public ASN record can affect how outside operators, peers, abuse desks, and investigators identify responsible parties for routing coordination, troubleshooting, and registry updates. The contact pathway is a point of operational dependency.

Watchpoints

Edwin Wong's registry role makes him a potential operational dependency for AS210282. Readers monitoring Larus Cloud Service Limited's network should treat Wong as a contact point whose responsiveness or authority can impact routing integrity. Without employer verification, the profile remains a registry-scoped signal rather than a confirmed insider.

Changes to the EW1323-RIPE handle in RIPE, new prefixes announced by AS210282, or Wong's appearance in other ASN registries would alter the assessment. Any independent employer confirmation would require revising authority and affiliation claims.

Missing employer verification, job title, career timeline, active prefix data for AS210282, and historical registry changes. Also no social or professional profiles for the person.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Edwin Wong.
• RIPE registry record - RIPE Database query page is the public registry surface for the handle EW1323-RIPE referenced in the AS210282 RDAP contact data.
• bgp.tools - A public BGP reference page exists for AS210282, providing external routing-context confirmation that the ASN is an active public network identifier worth operational follow-up.