Summary

  • Public research candidates associate an administrative autonomous-system identity with ROYA, but this package does not contain a live RIPE registry response or current routing observation.
  • The decisive next test is a time-aligned comparison of registry data, route announcements, visible AS paths, historical routing, collector visibility and any operator-maintained network record.

ROYA Communications and Internet Services Company Ltd is associated in this investigation with autonomous system AS210837. That association is a starting point, not a conclusion about the company’s present business. An autonomous system number can remain registered while its route announcements change, disappear from a particular collector’s view or move into a different operating arrangement.

The current evidence package does not establish which of those states applies. The research run had no live web or HTTP retrieval capability. It therefore verified no current prefixes, registry attributes, visible AS paths, recurring adjacent autonomous systems, routing-history interval or visibility measure. The public URLs retained in the package are evidence candidates, not evidence of the values they might return.

That limitation matters because the economic question is stronger than “does AS210837 exist?” A functioning network footprint would require a chain of observations: a current administrative record, routes actually originated or propagated by the ASN, paths visible from external collectors, and enough persistence or breadth to distinguish an operating surface from a stale or partial record. Even that chain would not automatically prove customers, contracts, ownership of address space or bargaining power.

The registry establishes identity, not service delivery

The RIPE Database aut-num object and the RDAP record are the appropriate first sources for checking the registered name, organisation references, status, maintainers, contacts and change events associated with AS210837. They can show how the number is represented administratively and whether its record has been modified. They cannot by themselves show that ROYA currently controls routers, serves customers or originates routes.

Declared import and export policy would describe an intended or recorded routing policy. It would not necessarily describe active BGP sessions. Likewise, registry country and address fields should not be treated as proof of router location or a service footprint. The distinction is operational: administrative control of a record can persist after a network changes hands, pauses announcements or uses another party to operate connectivity.

A route observation would be stronger, but still narrower than a business claim

RIPEstat’s routing-status, announced-prefixes, BGP-state, looking-glass, ASN-neighbours, routing-history and visibility services are designed to answer different technical questions. A current announced-prefixes result could identify prefixes observed with AS210837 as origin. BGP-state and looking-glass data could show particular paths and collectors. Routing history could place announcements and withdrawals in time. Visibility could indicate how broadly a route appeared among participating observation points.

None of these observations is universal reachability. A zero result may reflect withdrawal, a temporary gap, filtering or collector coverage. A nonzero result would show that a route was visible from particular vantage points at a particular time. A route originated by AS210837 would support a routing assertion, but not necessarily legal ownership of the address space or day-to-day control of the infrastructure.

The correct test is therefore comparative rather than singular. Retrieve the relevant endpoints within a closely matched UTC window, retain each response timestamp, and compare the prefix set and paths across RIPEstat and third-party views such as BGP.Tools, Hurricane Electric and BGPView. Differences are not automatically contradictions: they may reflect refresh time, caching, filtering or different collectors. Agreement would strengthen an observation of routing visibility, while still leaving the commercial mechanism open.

Adjacency can indicate dependence without proving a contract

If multiple independent collectors repeatedly show another ASN immediately before AS210837, that pattern could support an inference of recurring routing adjacency. It may be consistent with transit dependence, a peer relationship, a route server, a sibling network or another technical arrangement. It does not identify a paid-transit contract, exclusivity, customer status or the party exercising operational control.

This is where network economics begins, but does not end. A recurring upstream-like path could matter if ROYA depends on it for reachability and has no comparable alternative. To establish that consequence, the routing observation would need to be connected to service continuity, traffic dependence, contractual rights, capacity, pricing or a documented operational relationship. The present package contains none of those verified facts.

PeeringDB can add an operator-maintained record covering items such as policy, facilities, exchanges or contacts, if a record is returned. Its presence would be a useful lead; its absence would not prove that AS210837 has no active relationships. Operator-maintained directory data and route-collector observations answer different questions and must not be collapsed into one claim.

The next observable condition

The most useful follow-up is a synchronized evidence table. For one UTC retrieval window, record the RIPE administrative identity and event dates; current IPv4 and IPv6 prefixes; full visible AS paths; adjacent ASNs and their path positions; collector visibility; historical first- and last-seen information; IRR route objects; and the status of any PeeringDB record. Then repeat the routing observations over a defined interval rather than treating one empty or populated response as decisive.

Three outcomes would materially change the assessment. Persistent, cross-collector announcements would establish a stronger technical footprint, though not by themselves a customer or revenue base. A registered identity with no corroborated current routes would leave operational activity unestablished, not disproved. Divergent observations would make measurement coverage and timing the central issue, not justify a claim of shutdown, transfer or commercial failure.

For now, the bounded conclusion is clear. Public records define a testable relationship between ROYA and AS210837, but the available package does not verify current operation or economic significance. The missing step is not another interpretation of the ASN. It is current, time-stamped and independently comparable evidence connecting the identity to routes, persistence and a demonstrable dependency.

Sources and evidence boundary

The following public sources were retained as candidates for the next live retrieval. Their current contents were not retrieved in this run.

  1. RIPE Database aut-num record
  2. RDAP record
  3. RIPEstat routing status
  4. RIPEstat announced prefixes
  5. RIPEstat BGP state
  6. RIPEstat looking glass
  7. RIPEstat ASN neighbours
  8. RIPEstat routing history
  9. RIPEstat visibility
  10. PeeringDB network lookup
  11. BGP.Tools ASN summary
  12. Hurricane Electric BGP Toolkit
  13. BGPView prefixes
  14. BGPView upstreams
  15. RIPE inverse-origin search
  16. IPinfo ASN page

The linked directory entry is ROYA Communications and Internet Services Company Ltd.