Summary

  • R-TEL's website advertises business internet, data transmission, dark fibre, data-centre services, address rental and fibre construction.
  • The same page displays 99.7% network availability and 24/7 technical support, but gives no public calculation method or service scope for the percentage.
  • RIPE associates four autonomous systems with the company's organisation object; RIPEstat showed three announced and one unannounced in this bounded observation.
  • Neither the marketing number nor the ASN count identifies the end-to-end service dependencies or the party responsible for recovery.

The most consequential number on R-TEL's website is 99.7%. It sits beside claims of more than 500 satisfied clients, more than ten years in the market and round-the-clock technical support. Precision invites confidence. Yet without a measurement boundary, 99.7% cannot tell a buyer how a critical connection is likely to behave.

The company describes a broad operating surface: internet access for businesses, data-transmission channels, dark-fibre rental, colocation and server rental, IPv4 and IPv6 address rental, and turnkey fibre construction. These services do not necessarily share the same infrastructure, failure modes or restoration owner. A site-wide percentage could refer to one network layer, one product family or an aggregate. The public page does not say.

What is missing is specific rather than abstract. The page does not publish the observation period, denominator, customer or circuit population, planned-maintenance treatment, upstream and power exclusions, monitoring point, incident threshold or service-credit rule behind the figure. That absence does not make the number false. It makes the number unsuitable for comparing services until its definition is supplied.

The registry layer provides a different map. RIPE NCC lists "R-TEL" LLC as a Ukrainian member at the Kyiv address shown by the company. The organisation object identifies ORG-LA1866-RIPE as a Ukrainian LIR.

Four RIPE aut-num objects—AS47893, AS47945, AS44801 and AS57415—are associated with that organisation. In the dated RIPEstat observations used for this article, AS47893, AS47945 and AS57415 were marked announced, while AS44801 was not.

That difference is a useful diligence trigger, not an outage diagnosis. Registered ASNs can serve different roles, remain unused, support migrations or carry only selected resources. A route collector's view cannot establish whether a customer circuit is up, whether a data-centre service is healthy or whether an unannounced ASN matters to the current product.

The two evidence layers should therefore be joined carefully. The website states a service promise. RIPE records identify administrative resources. RIPEstat gives a bounded observation of route visibility. None reveals which origin, fibre segment, upstream, facility or support team sits behind a named customer contract.

A business customer should ask R-TEL to define 99.7% for the exact service being bought. The definition should name the monitored endpoint, measurement interval, exclusions, aggregation rule and contractual remedy. It should also map who detects an incident, who can reroute or dispatch, which dependencies belong to partners and who communicates until restoration.

The value of the public claim is that it creates a testable question. Once scope and ownership are attached, an availability percentage can support procurement and post-incident review. Without them, it remains a precise-looking statement whose operational meaning changes with the denominator.

Sources

R-TEL official site; RIPE member record; RIPE organisation object; AS47893; AS47945; AS44801; AS57415; RIPEstat overviews for AS47893, AS47945, AS44801 and AS57415.