Core Entity Brief
| Entity | Andrew Mouzoures |
|---|---|
| Public role | The admin-c role places him as a gatekeeper for the network's registry data. Any change in his contact status, or in AS210988's routing behavior, could signal operational shifts, security incidents, or asset transfers that affect internet routing stability. |
| Region | Global |
| Category | Individual registry-holder label |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | QUARTER_30_120D |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 1 public source reference |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 03, 2026 |
The organization holding AS210988 is a RIPE NCC registered network entity with Andrew Mouzoures as its administrative contact.
What It Does
- Network operations: The entity operates autonomous system AS210988, enabling it to exchange routing information and connect to the global Internet. The specific services provided—such as Internet transit, cloud hosting, or enterprise connectivity—are not determined from the available evidence.
- Revenue and service gap: No customer lists, pricing, financial reports, or product descriptions are supplied. The business model remains opaque; any claims about revenue or market position would need official corporate disclosures or verified service contracts.
Operating Snapshot
- Registry footprint: Presence in the RIPE NCC registry with an allocated autonomous system number (AS210988). The number of announced IP prefixes, peering arrangements, and routing policies is unknown.
- Contact personnel: Andrew Mouzoures (AM2111-RIPE) is the listed administrative contact. Additional roles such as tech-c or abuse-c are not identified in the provided evidence, implying either a lean operational team or incomplete registry data.
Control Surface
- ASN ownership: Control of AS210988 gives the organization the authority to originate IP prefixes and define BGP policies, directly influencing how traffic routes across the Internet. Misconfiguration can cause widespread connectivity issues.
- Registry management: Through its administrative contact, the organization can update WHOIS/RDAP records. Accurate data is essential for routing security (e.g., RPKI) and abuse handling; the contact is a single point of failure.
Watchpoints
- ASN routing activity: Monitoring BGP announcements from AS210988 can reveal the network's growth, acquisition of new prefixes, or involvement in routing incidents. Sudden changes may indicate operational instability or asset transfers.
- Registry data freshness: Stale or inaccurate contact information in the ASN record could lead to failed communications during outages or abuse incidents. Regular verification is necessary to ensure the network remains accountable.

