Summary

  • The routing record for AS210837 shows a dated collapse in public visibility: from a self-reported July 2022 footprint of 22 IPv4 and 29 IPv6 prefixes to collector views in 2026 reporting zero announced prefixes and no global-table visibility since 11 February 2026.
  • Independent collectors disagree: IP.CC lists one IPv4 prefix (193.30.241.0/24) and CIDR Report notes a 45.151.234.0/24 more-specific in its recent window, while Hurricane Electric and CIDR Report both state the AS is not currently announcing in the global routing table.
  • The authoritative RIPE registry payloads — the RDAP autnum record and the RIPEstat announced-prefixes views — could not be directly inspected during this run's research on 26 September 2026; every figure below is attributed to a named mirror or collector.
  • ROYA Communications has published no statement in any located source; the operator's silence, and the inability to verify the primary payloads, are themselves reportable findings.

What the record says, source by source

The registration side of the record is consistent across three independent mirrors of the RIPE Database. IPIP.NET, IPTrace and Robtex each reproduce an aut-num for AS210837 named ROYA-Communications-and-Internet-Services-Company-Ltd, with organisation ORG-RI63-RIPE, a sponsoring organisation ORG-DTUL2-RIPE, status ASSIGNED, created 26 August 2021 and last modified 20 March 2023 https://iptrace.net/en/as/210837. The IPIP.NET rendering adds the organisation detail: org-name "ROYA Communications and Internet Services Company Ltd.", country IQ, organisation type OTHER, registration number M.SH. A.-02-0000029678, and an address in the flowers neighborhood, 41002, Mosul, Nineveh, Iraq https://whois.ipip.net/AS210837. These are mirror-reported values. The authoritative RIPE RDAP response for this autnum was not retrievable by this run's research tooling https://rdap.db.ripe.net/autnum/210837, so every registration field above carries transcription risk.

The historical footprint is harder to pin. PeeringDB's self-reported network record (net/30448) — last updated 27 July 2022 — lists network type Cable/DSL/ISP, a Middle East geographic scope, traffic levels of 5–10 Gbps, and 22 IPv4 and 29 IPv6 prefixes https://www.peeringdb.com/net/30448. The linked organisation record confirms the alias "Roya ISP" and the ASN 210837 https://www.peeringdb.com/org/32823. Because this is operator-supplied directory data, it describes what ROYA claimed in July 2022, not what collectors measured. The pinned historical RIPEstat view that would confirm actual announcements in that period was not retrieved https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS210837&timestamp=2022-07-01T00:00:00Z, and a further documentation check raised a methodological caution: the RIPEstat announced-prefixes endpoint uses starttime and endtime parameters, not the timestamp parameter used in the pinned URL, so that request may not have constrained the window as intended https://stat.ripe.net/docs/data-api/api-endpoints/announced-prefixes.

The current picture is where the sources diverge. Hurricane Electric's BGP page states that "AS210837 has not been visible in the global routing table since February 11, 2026", with zero prefixes announced, one prefix originated (193.30.241.0/24) and one BGP peer observed https://ipv4.bgp.he.net/AS210837. CIDR Report states the AS "is not currently used to announce prefixes in the global routing table, nor is it used as a visible transit AS", while recording one more-specific — 45.151.234.0/24, a more specific of 45.151.232.0/22 — among advertisements in its prior seven days https://www.cidr-report.org/cgi-bin/as-report?as=AS210837&view=6447. IP.CC, by contrast, lists one IPv4 prefix for the ASN, 193.30.241.0/24, described as TECHNOX-INTERNET-TEKNOLOJILERI, country Turkey, RIR RIPE https://ip.cc/topic/asn/AS210837/; Robtex lists the same /24 but associates it with OMEGATECH-AS https://whois.ipip.net/AS210837.

Why the disagreement matters

Three views report zero current announcements; one lists a single /24; one recorded a recent more-specific that may be unrelated to ROYA itself. The discrepancy could reflect stale caches, RIPEstat's minimum-peer-visibility filter (the endpoint's documented min_peers_seeing default of 10 excludes routes seen by fewer peers) https://stat.ripe.net/docs/data-api/api-endpoints/announced-prefixes, known endpoint lag — a RIPE NCC forum thread from 29 June 2026 documents a "latest available results are 26 hours old" warning on this very endpoint family https://forum.ripe.net/t/the-data-for-announced-prefixes-has-not-been-updated-for-some-time-please-check-it/1737 — or genuinely intermittent announcements. This article does not resolve the mechanism. What it can do is name each collector's exact figure and boundary date, which is more than any single view offers.

The lifecycle accountability question

Under the three-layer attribution lens this publication applies, the collapse in visibility has three candidate loci of control, and the evidence does not cleanly assign the failure to any one of them. First, the operator: a network that self-reported 51 prefixes in 2022 and now announces at most one has changed its own behaviour, and only the operator can say why. Second, the registry relationship: the aut-num remains status ASSIGNED with a sponsoring organisation, meaning the registration layer has not withdrawn the resource — a fact that makes the routing silence an operator-side event rather than a registry action, on the mirror-reported record https://iptrace.net/en/as/210837. Third, the measurement dependencies: two of the four collector views reporting zero do so through aggregation pipelines with known lag and filtering thresholds, so part of the "collapse" may be an artefact of how visibility is counted.

None of these layers can be settled without the operator. And the operator has said nothing: no statement from ROYA Communications appears in any source located during this run's research on 26 September 2026 https://btw.media/en/as210837-continuity-gap-registry-routing-and-collector-visibility.

What durable repair would look like

The remedy standard for this kind of continuity gap is bounded and testable. It would require, at minimum: restored or formally withdrawn BGP announcements reflected in repeated, independent collector observations over weeks, not hours; a dated operator statement — or a registry record change, such as a status update — explaining the transition; and reconciliation between the two disputed /24 listings and the organisations they are attributed to.

Until one of those demonstrations occurs, the honest description of AS210837 is this: a registered, ASSIGNED autonomous system, last globally visible in the routing table on 11 February 2026 by Hurricane Electric's boundary, whose present behaviour no authoritative source currently documents.

Sources