Summary

  • Public records identify a set of RIPE NCC and independent routing-observation sources that can be used to test AS210837, but the current research receipt does not verify their live field values.
  • The defensible conclusion is therefore conditional: route origin, repeated cross-observatory visibility, declared policy and operator records would be needed before inferring operational control, upstream dependence or customer exposure.

The evidence stops one step before the business claim

The central question around ROYA Communications and Internet Services Company Ltd is not whether the company name appears beside an autonomous system number. It is whether that identity corresponds to a network operation with observable control, identifiable dependencies and economic consequences.

The current record does not answer that question conclusively. It provides immutable source snapshots and source-specific research candidates for AS210837, including RIPE NCC endpoints for the aut-num record, AS overview, announced prefixes, ASN neighbours, routing history and route-object search. It also identifies independent views from BGP.Tools, Hurricane Electric, Cloudflare Radar, PeeringDB and BGPView. The research receipt records the existence of those sources and the questions they can answer, but explicitly says that the live responses were not retrieved. Exact current prefixes, neighbour sets, route-history changes and operator records therefore remain unverified. RIPEstat launchpad RIPE WHOIS API RIPE announced-prefix API RIPE ASN-neighbours API RIPE routing-history API

That limitation is not a technical footnote. It changes the article’s conclusion. A registered ASN can be an administrative identity, a retained resource, an intermittently used network instrument or part of a live access business. Those possibilities have different implications for continuity, bargaining power and cash flow. Treating them as interchangeable would turn a research lead into an unsupported company claim.

The strongest finding available now is methodological and causal: AS210837 can be investigated through a chain of evidence, but the chain is incomplete. The chain begins with the administrative record, moves through declared routing policy and route objects, then tests whether prefixes are actually visible, whether visibility persists, which adjacent ASNs recur and whether any operator or commercial record links the network to customers and contracts.

Administrative identity is the starting point, not proof of operation

The RIPE Database aut-num object is the appropriate first check for the relationship between AS210837 and the named company. A live object could verify the registered holder, status, creation and modification metadata, maintainers and declared import or export policy. The current snapshot, however, says that the live response was not retrieved and that the exact attributes and modification dates remain unverified. RIPE aut-num object

That distinction matters because administrative records describe what has been registered or asserted. They do not necessarily describe what packets are being carried today. An import or export attribute can name a routing-policy relationship without proving that the relationship is operational. A route object can remain in an Internet Routing Registry after a route has been withdrawn. Conversely, a route may be visible without a matching object in the particular registry being consulted.

The RIPE route and route6 search is therefore useful as a comparison layer, not as a substitute for routing observation. Its value would be in showing which address prefixes have a declared AS210837 origin, who maintains those objects and when they were modified. The current research receipt says those search results were not retrieved and warns that a route object must not be treated as proof that ROYA owns the underlying address allocation. RIPE route-object search

This produces the first state difference the investigation must preserve. “Registered to” and “originating now” are separate propositions. The former concerns administrative identity. The latter concerns observed control of a routing surface at a defined time and from defined measurement points.

Route origin would establish visibility, not ownership or customers

The RIPEstat announced-prefix endpoint is the next test. A timestamped response could show the IPv4 and IPv6 prefixes observed by RIPE RIS with AS210837 as origin. First-seen and last-seen values could help distinguish longstanding announcements from additions, withdrawals or intermittent visibility during 2025 and 2026. The current evidence package contains the endpoint and its intended use, but not the live prefixes or counts. RIPE announced-prefix API

Even a positive result would have a limited meaning. It would show that a collector observed an announcement. It would not, on its own, establish legal ownership of the address space, customer dependency, revenue exposure or the commercial direction of an interconnection. A network can originate a customer prefix, announce a delegated block, provide temporary reachability or appear differently across collectors without revealing the contract behind the route.

That is why route origin has to be compared with route objects and historical visibility. A prefix present in both an active observation and a current registry assertion would be a stronger operational signal than either item alone, but it would still not prove that the route is part of a durable customer service. A prefix visible in BGP but absent from the consulted route database could reflect another registry, a stale registry boundary or a missing object. A route object without current visibility could represent intended policy, a withdrawn route or an inactive service.

The difference between these cases is commercially important. If ROYA demonstrably originates a stable set of prefixes, the company may have operational control over a routing surface. If that surface is intermittent or externally originated, the continuity risk may sit elsewhere. If the ASN has no current observed prefixes, the public evidence would support an administrative-presence conclusion rather than an active-operator conclusion. None of these outcomes can be selected from the current receipt because the live values are not present.

Neighbours are clues about dependency, not contracts

The ASN-neighbours endpoint can identify ASNs observed immediately before or after AS210837 in BGP paths. Repeated adjacency across measurement points may generate candidates for transit providers, peers or downstream relationships. Separate IPv4 and IPv6 observations may also reveal different connectivity patterns. But the source itself warns that adjacency does not establish the commercial relationship type. RIPE ASN-neighbours API

This is where a technical observation is most easily over-read. An adjacent ASN could be an upstream, a downstream, a settlement-free peer, a route-server participant or an artefact of limited visibility. The direction of a BGP path is not the same thing as the direction of payment. A provider may carry a route without being the contracting party for the end customer. A peer may exchange traffic without selling transit. A route server may make a participant appear adjacent without representing a bilateral commercial dependency.

Independent observatories can make the inference more robust, but not transform it into a contract. BGP.Tools can provide a comparison point for originated prefixes and inferred connectivity. Hurricane Electric can offer another view of prefixes and adjacent ASNs. Cloudflare Radar may add independent routing or time-series context. BGPView can serve as supplementary evidence. Each source has different collectors, refresh schedules and inference methods; the research receipts identify their pages as candidate sources but do not verify their current contents. BGP.Tools Hurricane Electric BGP Toolkit Cloudflare Radar BGPView

Agreement would strengthen an operational-footprint finding. If several independently timestamped systems showed the same prefixes and recurring adjacent networks, the probability of a real and observable routing surface would rise. Disagreement would not prove shutdown, transfer or fraud. It would first raise a measurement and timing question: which collectors saw what, when and from where?

The economic mechanism is conditional. If AS210837 relies on one or a small number of externally visible upstream paths, a change in those paths could affect reachability, redundancy and negotiating leverage. But the size of that exposure depends on facts not in the current record: whether the adjacent networks are paid transit providers, whether alternative paths exist, whether ROYA controls access facilities or last-mile assets, whether customers are attached to the observed prefixes and whether contracts impose continuity obligations.

Routing history is the test for change

The commission asks what changed, not merely what exists. The RIPEstat routing-history endpoint is therefore more valuable than a static ASN profile. A timestamped series beginning in January 2025 could show new prefix appearances, withdrawals, visibility gaps or changes in collecting peers. A stable prefix set and uninterrupted visibility could support a continuity finding, subject to collector coverage. The current source snapshot says that no historical payload was retrieved, so no 2025–2026 change can be asserted. RIPE routing history

Without a before-and-after observation, the causal story remains hypothetical. There is no verified state difference showing that ROYA added an upstream, lost one, expanded its address footprint, changed origin, moved from IPv4 to IPv6, or experienced a routing interruption. There is also no verified evidence that a network event changed prices, customer service, bargaining power or cash flow.

That does not make the investigation empty. It clarifies the next observable condition. A genuine change would need a timestamped comparison: the prefix set before and after the event; the identity and recurrence of adjacent ASNs; route-object modification dates; corroboration from another observatory; and, ideally, an operator or regulatory record explaining the change. Without those elements, a current profile risks confusing persistence of a registry record with persistence of a service.

PeeringDB can add operator context, but it is self-reported

PeeringDB is relevant because it can connect routing observations to operator-supplied information about policy, facilities and exchange participation. The current research receipt identifies the AS210837 API query as a candidate source but says that no matching network record was confirmed. PeeringDB network query

A verified, dated PeeringDB record would be useful context. It could identify how the operator describes its network, where it says it interconnects and whether its declared policy is consistent with observed routing. It would still be self-reported and potentially incomplete or stale. A missing record would not prove that no network exists; many small operators have limited directory visibility. A populated record would not prove that every stated facility, policy or relationship is currently active.

The same rule applies to company records. A legal name, web presence or registry entry may establish that an organization exists or claims an activity. It does not prove route origination, customer numbers, transit terms or cash flow. Those claims require company filings, transaction records, regulator decisions, operator statements or other primary evidence that links the network resource to an economic obligation.

The commercial conclusion is deliberately bounded

The current evidence package does not establish customer dependency, pricing power, upstream contract terms, revenue exposure or a cash-flow consequence for ROYA. That is the correct conclusion, not a temporary rhetorical inconvenience.

The potential mechanism is nevertheless clear. If ROYA controls a demonstrably active routing surface, and if that surface carries customers or essential connectivity, upstream concentration could affect continuity and bargaining power. A provider change, route withdrawal or address-resource problem could then become an operational event with commercial consequences. But each link requires evidence: active routes; identifiable control; a relationship between the routes and customers; a dependency on particular upstreams or facilities; and an observable effect on service, price, cost or cash flow.

The reverse failure path must remain equally visible. AS210837 may be a retained or intermittently used ASN whose public records outlive a former operating arrangement. Apparent adjacency may be a measurement artefact or a non-commercial relationship. A registered prefix may not be active. An active route may belong to a customer or another organization’s address space. A small or sparse network may be operational but poorly represented by global observatories. None of these possibilities can be eliminated by the current source receipt.

The result is a bounded state assessment:

  1. Administrative identity: investigable through RIPE records, but exact current attributes are not verified here.
  2. Observed routing: testable through announced-prefix and routing-history measurements, but current values are unavailable in this run.
  3. Interconnection: potentially inferable through repeated, cross-observatory adjacency, but neighbour data does not identify contract direction or payment.
  4. Commercial dependency: not established. No source receipt links AS210837 to customers, prices, upstream terms, revenue or cash flow.

That assessment is narrower than calling ROYA an active regional ISP and more useful than repeating that its ASN exists.

What would change the assessment

The next evidence should be collected as a dated comparison rather than a single lookup. First, retrieve the current RIPE aut-num object and route-object search with modification dates, maintainers and declared policy. Second, retrieve announced prefixes and routing history for a defined interval. Third, compare those results with BGP.Tools, Hurricane Electric, Cloudflare Radar and BGPView, recording timestamp and measurement scope. Fourth, check whether PeeringDB or company records describe facilities, policy or service relationships.

Fifth, seek primary commercial or regulatory records linking network control to customers, contracts, pricing or continuity obligations.

The falsifying evidence would be just as important. A verified absence of current route visibility across independent collectors would weaken an active-operator thesis. A stable prefix set with no material change would weaken a claim of recent strategic transformation. Conflicting route-origin and registry data would weaken any ownership inference. Evidence of multiple alternative upstreams would weaken a concentration-risk thesis. Evidence that the relevant prefixes belong to customers or another legal entity would weaken the claim that ROYA controls the full commercial surface.

The next condition for a stronger conclusion is therefore observable and specific: a timestamped, cross-source record showing which prefixes AS210837 originated, for how long, through which recurring paths and under whose operational or contractual control. Until that record exists, the responsible market conclusion is not that ROYA has no operation. It is that public evidence has not yet demonstrated one at the level required to infer dependency or bargaining power.

Sources and evidence boundary

This article uses the current FACT_PACKAGE and its runtime-issued source set. The source receipts identify the endpoints and their intended evidentiary roles; where live values were unavailable, the article states that limitation rather than converting a candidate claim into a fact.