Zerops s.r.o.

Zerops s.r.o. is a Czech cloud platform operator holding AS210984, confirmed through RIPE registry and public routing data. The profile establishes the company’s identity, platform context, and ASN visibility but cannot describe active routing, commercial scale, or internal decision-making due to evidence gaps. Watchpoints include new prefix announcements, registry changes, and the emergence of named personnel. The assessment is intentionally narrow, limited to what public signals can prove.

Zerops s.r.o.

Zerops s.r.o. is a Czech cloud platform operator that holds autonomous system number AS210984, publicly visible in RIPE registry and routing data. The company offers application deployment and management services through its Zerops platform. While its ASN and website confirm an operating presence, active prefixes, customer lists, and named executives remain undocumented from current public sources.

Why It Matters

By holding AS210984 and operating a cloud platform, Zerops s.r.o. can impact service reachability for its customers through network configuration changes. Future prefix announcements, registry modifications, or new evidence about its infrastructure would directly alter the scale and significance of its role in internet routing.

What Public Sources Show

Zerops s.r.o. operates a cloud platform at zerops.io and holds the autonomous system number AS210984, placing it squarely at the intersection of application hosting and internet routing. Any change to its network configuration can directly affect the availability and performance of services running behind its infrastructure. This makes the company’s public signals material for analysts tracking infrastructure dependencies or monitoring cloud service chokepoints across the European internet landscape.

Multiple independent sources confirm the company’s core identity. The RIPE registry lists Zerops s.r.o. as the organisational holder of AS210984, and both RIPEstat and BGP.tools show routing visibility for the autonomous system. The company’s own website describes a platform for deploying, scaling, and managing applications—a typical cloud service model. The Czech public business register provides the legal anchorage for the s.r.o.

entity, though a direct confirmation link from an official government page was not captured in this review.

What the evidence does not yet show is an active prefix announcement. That means the routing footprint cannot be described beyond the bare ASN itself. Similarly, no public customer list, ownership structure, or named executives appear in the sources examined.

The profile is therefore a baseline: readers can verify the company’s identity, its cloud offering, and its ASN registration, but not its internal commercial scale or who makes its infrastructure decisions.

The current picture is one of a legally registered company with a visible but undeployed internet number resource.

The company’s publicly observable control surfaces are straightforward: its corporate and product website, its RIPE organisation and aut-num records, and the BGP routing data associated with AS210984 as reflected in public route-collectors. Future prefix announcements would be the most immediate signal of operational change, revealing the company’s active network footprint.

Likewise, changes to its registry entries—whether to contact details, description fields, or the ASN’s status—could indicate a reorganisation or transfer of control, making them a primary focus for watch cycles.

Analysts should watch for new prefix announcements originating from AS210984. Any such announcement would define the company’s active routing role and could reveal peering or transit relationships. The appearance of a PeeringDB entry would add operational detail. Registry record changes, particularly to the organisation or aut-num entities, could alter the public identity baseline.

The emergence of named individuals in public corporate filings or as RIPE contacts would help assess decision-making authority and internal structure.

The main gaps in this profile are the absence of an active prefix, the lack of a directly captured government registration confirmation, and the missing personnel data. Until those gaps are filled, the assessment is limited to ASN identity and platform context. Readers should not extrapolate a large-scale network operator from the current evidence.

Future collection efforts should target the Czech business register’s searchable interface, PeeringDB, and any official company blog or regulatory filings that might disclose network plans.

This profile is built from public, independently verifiable sources: RDAP data at rdap.org, RIPEstat telemetry, the Zerops website, the Czech business register, and BGP.tools. No private, unverifiable, or inferred claims are included. The article will be refreshed as new evidence surfaces.

Operating Surface

Zerops s.r.o. operates a cloud platform at zerops.io and appears in RIPE registry records as the organisation associated with AS210984. Its control surface includes its corporate website, RIPE database entries, and BGP routing visibility. The company can influence service availability and traffic flows for hosted applications, but the current evidence does not confirm any active prefix announcements or private contracts.

The company’s ASN is part of the observable internet routing ecosystem, and changes to its registry records or prefix announcements could affect downstream services and customers. As a cloud platform operator, it represents a dependency for hosted applications, making it a relevant entity for infrastructure mapping and risk monitoring.

Watchpoints

Zerops s.r.o. is currently a lightweight internet infrastructure actor with an ASN but no public prefix announcements. Its strategic significance lies in its potential to expand into active routing and its role as a cloud platform that could host numerous downstream customers. Until it announces prefixes or reveals its customer base, it remains a watchlist entity rather than a confirmed critical dependency.

Concrete watchpoints that would change the assessment: (1) any prefix announcement from AS210984, which would instantly elevate its routing significance; (2) changes to its RIPE registry records indicating reorganisation; (3) the addition of PeeringDB data or public interconnection agreements; (4) the identification of key personnel in public filings or registry contacts.

The critical data gaps are active prefix announcements, direct government registration confirmation, executive or staff identities, customer volume, and internal network architecture. These gaps prevent a full operating assessment. Collection should target PeeringDB, the Czech business register search, and any official company communications.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Zerops s.r.o..
• RIPE registry record - RIPEstat provides public routing and registry visibility for AS210984, supporting that the ASN is publicly observable as an internet infrastructure asset.
• Operator website - The Zerops website presents Zerops as a cloud platform for app deployment and operation, supporting the company's operating context.
• Internet registry record - The Czech public business register contains company registration records for Czech companies including s.r.o. entities, which can be used to verify Zerops s.r.o. legal existence.
• bgp.tools - BGP.tools shows public route-observation data for AS210984, supporting that the ASN has externally visible routing presence.