Summary

  • AS208179 is held by ACTIVECLOUD Pro Active Computers SRL in RIPE NCC registry data and originates the IPv4 prefix 31.14.55.0/24, first seen with that origin on 2 October 2019 and still announced on 17 October 2026.
  • The same brand-like name appears on two other directory objects whose autonomous systems are held by entirely different organisations — AS215709 by AS-YOLLA YOLLA CALLS INTERNATIONAL OU and AS215712 by printful Printful Latvia AS — so the apparent ACTIVECLOUD collision is a naming artifact, not three operators sharing one identity.

What the record actually says

The RIPE NCC registry data for autonomous system AS208179 records the holder as ACTIVECLOUD Pro Active Computers SRL, assigned within IANA 32-bit autonomous-system block 207260–208283. The same query reports the autonomous system as announced, dated 17 October 2026 (RIPEstat AS overview, AS208179).

A holder string and an announcement flag are registry facts. They are also narrower than they look. The holder field names the organisation the registry associates with the number; it does not describe what that organisation does, who controls it, or where it is.

A real prefix, a long-running origin

AS208179 is not a dormant registration. RIPEstat announced-prefix data lists a single IPv4 prefix for the autonomous system — 31.14.55.0/24 — with an announcement window running from 3 October 2026 to 17 October 2026 (RIPEstat announced prefixes, AS208179).

The prefix-side view agrees on the origin: prefix-overview for 31.14.55.0/24 lists AS208179 as the announcing autonomous system with holder ACTIVECLOUD Pro Active Computers SRL (RIPEstat prefix overview, 31.14.55.0/24). Routing-status data puts first contact earlier still: the prefix was first seen on 2 October 2019 with origin 208179, and a route object for it exists in the RIPE registry (RIPEstat routing status, 31.14.55.0/24).

Read together, those three surfaces describe an origin that has been present in the routing table for roughly seven years and is still announcing a single /24. That is a thin footprint, and it is also a specific and checkable one.

The name match that is not an operator match

BTW's directory also carries two other objects whose names contain ACTIVECLOUD: ACTIVECLOUD-BY-AS2 and BY-ACTIVECLOUD-MNT. Their autonomous systems are not held by any organisation named ACTIVECLOUD. Registry data records AS215709 as held by AS-YOLLA YOLLA CALLS INTERNATIONAL OU (RIPEstat AS overview, AS215709) and AS215712 as held by printful Printful Latvia AS (RIPEstat AS overview, AS215712).

That matters for how names are read. A name shared across database objects is not evidence of a shared operator; in this case the registry contradicts the inference outright. Anyone building a picture of "ACTIVECLOUD" from name matches alone would be assembling one organisation out of two unrelated ones and one genuine holder.

Where the record stops

The registry surface that names the holder is not the surface that describes the company. On the evidence reviewed here, the following remain unresolved:

  • The maintainer object, sponsoring organisation, registered country and registration date attached to AS208179. The RIPE NCC database query and the RDAP aut-num endpoint for the object returned no registry text in the retrievals used for this article, so those fields cannot be reported from evidence.
  • Any corporate record — registration, officers, website — connecting the holder string to a legal entity. None was retrieved.
  • Whether 31.14.55.0/24 supports any customer-facing service, and to whom the address space is assigned.
  • The RPKI validation state of the announcement.

Those are gaps in the public record, not findings of wrongdoing. The honest reading is that a real, live origin exists under a named holder, and that the accountability questions a reader would naturally ask next are not answered by the same record that confirms the origin.

The directory entry for this subject is the ACTIVECLOUD Pro Active Computers SRL profile.