A local workload needs more than a patriotic hosting answer
Imagine the infrastructure team at a mid-sized Omani bank, a freight platform serving Duqm and Sohar, or a systems integrator reselling cloud capacity to ministries. The default answer is familiar: put production in Dubai, keep disaster recovery somewhere else, and treat local hosting as a compliance footnote. That answer is cheap to explain and often easy to procure, because the UAE and Saudi markets have the best-known cloud regions, the deepest partner ecosystems and the strongest perception of scale. But it is not the only answer once the workload contains regulated personal data, operational dependency on Omani public entities, or latency-sensitive field systems linked to ports, wells and industrial customers.
Duqm Data Centre SAOC matters because it is one of the names that turns that abstract question into a purchasable Omani alternative. The company appears in the RIPE NCC member directory for Oman as Duqm Data Centre SAOC, with the public member page listing the Special Economic Zone - Duqm address, a data2cloud contact domain and Oman as the area serviced: https://www.ripe.net/membership/member-support/list-of-members/om/d2c/. Its own public site says data2cloud was founded in 2015, has its head office in Oman, serves local cloud-market needs and extends service to regional and global customers: https://data2cloud.om/. Oman also lists Duqm Data Centre (D2C) in the Ministry of Transport, Communications and Information Technology register of approved hosting service providers and data centers, with accredited SaaS and IaaS scope and a Muscat address: https://mtcit.gov.om/register-of-approved-hosting-service-providers-and-data-centers.
That does not make D2C a hyperscale rival to Dubai or Riyadh. It makes it a narrow but strategically interesting local-cloud operator whose public record combines three kinds of evidence: government-facing accreditation, internet-number resources, and commercial claims about colocation, virtual machines, backup, email and locally hosted object storage. The thesis is therefore not that D2C has already converted Duqm into a Gulf cloud hub. It is that the company exposes the economics of trying to do so: customers want Omani control and data locality, but they also test price, uptime, interconnection, security certification, power resilience, supplier depth and the risk of being locked into a smaller platform.
The company's strongest buyer story starts with sovereign workloads. Oman has made cloud and hosting governance a formal policy domain. MTCIT's cloud and hosting standard presents a framework for government agencies to adopt cloud services with attention to security, data sovereignty and accredited providers: https://mtcit.gov.om/library-3/guidelines-documentation-7/standards-64/cloud-and-hosting-services-standard-263. MTCIT's service page for cloud hosting and data center services says providers need the relevant telecommunications license and then an approval letter to deliver services to government entities: https://mtcit.gov.om/services-5/services-13/services-92/cloud-hosting-and-data-center-services-405. That creates a domestic market in which local accreditation is not just marketing language; it can become a procurement prerequisite.
But the same facts also limit the case. Public evidence points to a company with a visible but small autonomous-system footprint, not a vast internet platform. RIPEstat showed AS209576 announcing two IPv4 prefixes, 91.132.66.0/24 and 91.132.67.0/24, during the most recent observation window available at the time of research: https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS209576. RIPEstat's overview identifies the holder as data2cloud Duqm Data Centre SAOC and shows the AS as announced: https://stat.ripe.net/data/as-overview/data.json?resource=AS209576. That is useful evidence of operational presence in the routing system, but it is not proof of large utilisation, multiple independent upstreams, broad peering, or a deep wholesale cloud platform.
The judgment on D2C therefore turns on whether Omani locality is valuable enough to pay for a smaller supplier. For a bank that must explain where customer data sits, a local IaaS platform with government approval and a domestic support team may be easier to defend than an offshore default. For a logistics platform serving free-zone tenants, local hosting may reduce contractual friction and create a credible story about Oman-based resilience. For a cloud reseller, D2C can be a domestic component inside a broader multi-cloud offer. The hard part is that each of those buyers will still benchmark against Dubai's cloud maturity, Saudi Arabia's national-scale investment and Equinix/Omantel's connectivity position inside Oman.
The numbers make that benchmark sharper. Oman's data-center market is small but no longer theoretical: a ResearchAndMarkets summary put it at USD 181 million in 2023 and projected USD 326 million by 2029, a 10.3 percent CAGR: https://www.businesswire.com/news/home/20240729169602/en/Oman-Data-Center-Market-Investment-Analysis-Report-2024-2029-Featuring-Key-DC-Investors---Cloud-Acropolis-Datamount-Equinix-Ooredoo-and-Oman-Data-Park---ResearchAndMarkets.com. Arizton's later Oman forecast put investment at USD 288 million in 2025 and around USD 492 million by 2031, a 9.34 percent CAGR: https://www.arizton.com/market-reports/oman-data-center-market. Those are market-research figures, not audited D2C revenue, but they set the scale of the opportunity. D2C is trying to win in a market that can grow meaningfully for Oman while still being tiny beside Dubai, Abu Dhabi and Saudi Arabia.
The company is a real Omani cloud operator, but the name carries two geographies
The first analytical trap is the company name. "Duqm Data Centre SAOC" sounds like a single facility story in Duqm. The public trail is more complicated. RIPE's member page associates the member with the Special Economic Zone - Duqm address. The official data2cloud website says the business provides managed hosting solutions through Tier3+ data centers "hosted in Muscat, Oman." The MTCIT approved-provider register gives D2C's address as Panorama Mall, 4th Floor, Block 5, Bowshar, Muscat. The EPI certification record for a D2C computer room refers to Smail Industrial Estate, Al Dakhiliyah governorate, and shows an ANSI/TIA-942-B Design Rated 3 certificate that expired in March 2019: https://www.epi-certification.com/sites/map/Oman.
Those are not necessarily contradictions. Technology companies often carry a legal name, an operating brand, a registered address, one or more data halls and a sales/support office. But the difference matters for how to read the investment story. The name gives D2C a Duqm-linked policy identity. The website and accreditation register ground the customer offer in Oman, with Muscat playing a practical commercial role. The older design certification at Smail points to facility history rather than current whole-platform assurance. A serious buyer should therefore separate legal identity, sales office, certified rooms, routed network and actual workload location.
The official site is nevertheless specific enough to show a commercial catalogue. It advertises colocation in full-rack and half-rack form, starting from OMR 500; virtual machines under an infrastructure-as-a-service label, starting from OMR 16; backup as a service starting from Baisa 0.090 per GB; email services starting from OMR 1.500; and Cloud Drive as locally hosted object storage starting from OMR 90. The same page lists colocation, backup, infrastructure service, disaster-recovery service, email collaboration, cloud drive, security services and other managed-service lines: https://data2cloud.om/.
Those prices are not a full tariff. They do not reveal bandwidth commits, virtual CPU sizing, storage tier, support class, contract term, redundancy level, power allocation or whether the OMR 500 colocation figure is monthly and under what rack assumptions. But their existence is important. They show that D2C is not only an entry in a registry; it is selling recognizable cloud and hosting products to ordinary enterprise buyers. It is also presenting the offer in a way that targets customers who want to avoid running their own dedicated server rooms, not only customers buying raw rack space.
The site adds several claims that define the trust proposition: Tier 3+ certified data centers, MTCIT cloud-service-provider accreditation, ISO/IEC 27001:2022, 27017:2015 and 27018:2019 certification, Cloud Security Alliance Cloud Controls Matrix compliance, a 99.95 percent uptime guarantee, 24 by 7 monitoring, enterprise-grade security and same-day delivery. Because the assignment here is a public research article, the prudent reading is to treat those as company claims unless independently verified in current certificate databases. Still, they help explain how D2C wants to compete. It is not pitching only national pride. It is pitching a packaged trust layer: local hosting, certifications, managed support and faster provisioning.
Customer references on the official site point in the same direction. FRiENDi mobile is quoted as using data2cloud support for customer-service operations. iNNOVATEQ is quoted as saying D2C infrastructure hosts its Nibras platform, which monitors thousands of wells and requires high computing power. Those references are not audited revenue evidence, but they are useful market signals because they show the kind of workload D2C wants associated with its platform: telecom customer support and industrial monitoring rather than hobby hosting. They also fit Oman's broader demand pattern, where public-sector systems, oil-and-gas operations, logistics, healthcare and finance can value local support even when global clouds look cheaper on raw compute.
Ownership history adds another layer. Ooredoo Oman financial filings say that during 2015 the company acquired or subscribed for a 51 percent shareholding in Duqm Data Centre SAOC, that the company was registered in Oman, and that commercial operations started during 2019 after additional share subscriptions raised the shareholding to 71 percent as of 31 December 2019. Recent Ooredoo Oman financial statements still discuss D2C as the subsidiary with that historical investment path: https://www.ooredoo.om/wp-content/uploads/annualreport/Ooredoo_FS_English_2025.pdf. Ooredoo Group's 2024 annual report also lists Duqm Data Centre SAOC in the group table with Oman and a 39.0 percent interest at group level: https://www.ooredoo.com/wp-content/uploads/2025/03/Ooredoo_Annual-Report_2024_English.pdf.
That is commercially meaningful because D2C's visible upstream and peer environment also points toward Ooredoo Oman. RIPEstat's neighbor data for AS209576 showed one unique neighbor, AS50010: https://stat.ripe.net/data/asn-neighbours/data.json?resource=AS209576. Third-party BGP views identify AS50010 as Omani Qatari Telecommunication Company SAOC, the Ooredoo Oman network. BGP.Tools describes AS209576 as a small BGP network and shows a single visible upstream/peer pattern around that same carrier relationship: https://bgp.tools/as/209576. The implication is not that D2C lacks autonomy as a company. It is that its cloud-locality offer is carrier-adjacent and likely benefits from Ooredoo's infrastructure, sales relationships and regulated-telecom credibility.
That carrier link has a hard-asset side. Ooredoo Group announced in 2024 that Ooredoo Oman would land the 45,000 km 2Africa cable system in Barka and Salalah, connecting more than 3 billion people across 33 countries on three continents when complete: https://www.ooredoo.com/en/media/news_view/ooredoo-to-land-worlds-largest-subsea-cable-system-2africa-comes-to-oman/. Submarine Networks also records Barka and Salalah as Oman landing points for 2Africa and notes Ooredoo's Tier 3 data-center activity in the country: https://www.submarinenetworks.com/en/stations/asia/oman. D2C is not publicly shown as a cable-landing-station operator, and the article should not imply that. But the Ooredoo adjacency matters more when Ooredoo is investing in Oman's international cable geography, not only local access lines.
The network footprint is credible, small and revealing
For data centers, routing records are not everything. Many cloud platforms lease transit, hide behind carrier networks, use provider-assigned space, or serve domestic customers without a large public BGP presence. Still, D2C's RIPE and BGP trail is one of the few measurable ways to see the company's internet operating boundary.
RIPE RDAP lists AS209576 with the name data2cloud, active status, registration on 15 January 2019, and Duqm Data Centre SAOC as an organization entity: https://rdap.db.ripe.net/autnum/209576. RIPE route records show 91.132.66.0/24 originated by AS209576, created on 13 April 2020: https://rest.db.ripe.net/ripe/route/91.132.66.0/24AS209576. A second RIPE route record shows 91.132.67.0/24 originated by AS209576, created on 9 December 2020: https://rest.db.ripe.net/ripe/route/91.132.67.0/24AS209576. In the RIPEstat announced-prefixes view, both were visible in the two-week window ending 3 July 2026.
Those two /24s tell a specific story. They are enough public IPv4 space to support a small cloud platform, customer NAT pools, hosted services, mail systems, management endpoints and some dedicated customer assignments. They are not enough, by themselves, to suggest a large public cloud or a content-heavy hosting network. IPinfo lists AS209576 as hosting-type, shows 512 IPv4 addresses, two RPKI-valid /24s and 23 hosted domains: https://ipinfo.io/AS209576. IP2Location similarly associates AS209576 with Duqm Data Centre SAOC, Oman, the data2cloud.om domain and 91.132.66.0/24 plus 91.132.67.0/24: https://www.ip2location.com/as209576.
There are also inconsistencies across third-party address datasets. NetworksDB says it found 2,048 addresses in five networks operated by the organization and lists a larger 91.132.64.0/22 view: https://networksdb.io/ip-addresses-of/duqm-data-centre-saoc. Some public ASN summaries list 2a09:1540::/32 as associated with AS209576, while the RIPEstat announced-prefixes query used for this article showed only the two IPv4 /24s in the observation window. The fair reading is that D2C may have registry or database associations beyond currently visible routed IPv4, but the live routing signal visible through RIPEstat is modest.
That modesty can be an advantage in one buyer segment and a liability in another. For regulated local workloads, a small address footprint can mean a cleaner attack surface, less noisy abuse exposure and a supplier that is not crowded with anonymous high-risk customers. Scamalytics classifies Duqm Data Centre SAOC as potentially low fraud risk, reports low levels of web traffic from the ISP across its network, and says none of the IP addresses it observes are running high-risk services: https://scamalytics.com/ip/isp/duqm-data-centre-saoc. That is a weak market signal rather than a security audit, but it is directionally useful: D2C is not showing the public profile of a heavily abused bulk-hosting network.
For buyers needing scale, the same small footprint raises questions. Can D2C supply enough public IPv4 for large customer environments without heavy address reuse? Does it have enough transit diversity to survive a carrier incident? How much private connectivity can it offer to banks, government bodies, SaaS platforms and industrial sites? How mature is its DDoS mitigation, route filtering and RPKI practice? The public record shows valid route objects and some RPKI-valid third-party summaries, which is positive. It does not show dense peering, multiple independent upstreams, or a rich cloud exchange ecosystem.
The visible dependence on AS50010 is therefore central. Ooredoo's network can be a strength because a local carrier can supply access, enterprise accounts, mobile/fixed customer relationships and operational support in Oman. It can also be a concentration risk if buyers expect carrier-neutrality. A cloud platform that depends on a single upstream path will have a different resilience profile from one sitting in a carrier-neutral internet exchange with many available providers. D2C's public buyer argument is strongest where the customer values Omani support and accreditation more than global peering optionality.
The network evidence also helps interpret product claims. The official site says D2C offers virtual machines, backup, cloud drive and email collaboration. Those services do not need a huge autonomous system if the customer base is domestic and enterprise-oriented. A few hundred IPv4 addresses can support many private-cloud customers when the public exposure is controlled. Colocation, by contrast, can require richer carrier options if customers want their own network architecture. The article's baseline conclusion is that D2C is credible as a local managed cloud and hosting provider, but public routing data does not yet prove that it is a large interconnection venue.
The real commercial wedge is government and regulated enterprise demand
D2C's best economics are likely not driven by generic compute arbitrage. A buyer choosing between an OMR-priced Omani virtual machine and a global hyperscaler instance will almost always find a cheaper raw compute path elsewhere if it ignores compliance, support, data location and procurement rules. The local provider wins only when the buyer values a bundle: Omani data location, ministry approval, local account management, Arabic and English support, fast physical escalation, and an operating story that can be explained to boards and regulators.
That is why MTCIT's register matters more than a typical vendor directory. The register names approved hosting service providers and data centers, and for D2C it indicates accredited SaaS and IaaS scope while leaving PaaS unchecked: https://mtcit.gov.om/register-of-approved-hosting-service-providers-and-data-centers. That creates a clear positioning boundary. D2C can compete for software-as-a-service and infrastructure-as-a-service needs in Oman's government-linked market, but the public register does not show the same PaaS approval. The distinction matters for application-development teams. A ministry buying virtual servers, backup or hosted software has a stronger visible path than a team seeking an approved local platform stack.
The procurement signal is not hidden. MTCIT's data-center-establishment investment page describes data centers as a Digital Industry opportunity and explicitly frames Oman as attractive because of geography, connectivity infrastructure, regulation, political stability, digital transformation and energy-efficiency initiatives: https://mtcit.gov.om/investment-2/investment-4/investment-opportunities-57/data-centers-establishment-399. That page is not a D2C endorsement. It is more important as demand architecture: the same ministry that approves providers is also advertising the sector to investors, which means local hosting is part of industrial policy rather than a side market.
The national policy backdrop is favorable. MTCIT describes the National Digital Economy Program as a framework aligned with Oman Vision 2040 and says the general target is to increase the digital economy's contribution to GDP from 2 percent to 10 percent by 2040: https://mtcit.gov.om/programs/ndep. The program's listed initiatives include promoting data center and cloud services, attracting foreign digital investment, developing cybersecurity and adopting fourth-industrial-revolution technologies. That is a demand signal for D2C because local cloud platforms become part of the infrastructure base behind digital-government programs, national AI projects, e-services and data-driven public administration.
Oman's Personal Data Protection Law adds a second demand driver. MTCIT's page says the law was issued under Royal Decree No. 6/2022 and aims to protect personal data through controls for processing, including consent before processing: https://mtcit.gov.om/library-3/legislations-policies-8/laws-75/personal-data-protection-law-1034. The official decree text also addresses cross-border transfer controls and processor obligations: https://prod.mtcit.gov.om/ITAPortal//Data/English/DocLibrary/2024115132533256/PROMULGATING%20THE%20PERSONAL%20DATA%20PROTECTION%20LAW.pdf. Data-protection law does not automatically force every workload into Oman, but it makes data location, contractual control and auditability part of procurement conversation. That is exactly where a domestic provider can move from "nice to have" to "risk-reducing."
The government-service page for cloud hosting and data centers is even more operational. It describes a service that enables licensed cloud-computing and data-center providers to offer storage, preservation and processing platforms, operate data centers, and deliver cloud hosting services and technical support to government entities. It also says providers must obtain a Class IV license from the Telecommunications Regulatory Authority before MTCIT issues the approval letter: https://mtcit.gov.om/services-5/services-13/services-92/cloud-hosting-and-data-center-services-405. D2C's presence on the register therefore places it inside a controlled approval environment. That approval does not prove every control is strong, but it is a gate that offshore generic hosting does not pass by default.
For public-sector buyers, that gate changes the comparison with Dubai or Riyadh. A ministry can buy global cloud where policy permits, but it still needs to explain data classification, cross-border transfer, support jurisdiction, incident response and local recoverability. A local approved IaaS provider can become the landing zone for systems that are too sensitive, too operationally local or too procurement-bound to live only in an offshore region. This is the sovereign-workload signal behind D2C: not a guarantee of revenue, but a public policy channel that makes domestic IaaS more than commodity hosting.
For regulated enterprises, the same logic applies through procurement norms rather than statute. Banks, insurers, health-care organizations, telecom support vendors and energy-service platforms often need local incident response, clear data-processing roles, backup recoverability and evidence of security controls. The official site claims ISO/IEC 27001:2022, 27017:2015 and 27018:2019 certification. ISO 27017 is cloud-specific guidance for information-security controls applicable to cloud services, as ISO describes here: https://www.iso.org/standard/43757.html. ISO 27018 is particularly relevant to personally identifiable information in public-cloud environments. If D2C can show current certificates and scope statements to buyers, those claims help it compete for regulated workloads where procurement teams need recognizable frameworks.
This is not a market without competition. Oman Data Park, Datamount, Cloud Acropolis, Omantel and others appear in Oman's approved-provider register. Equinix operates in Oman through Muscat and Salalah facilities, and says the Muscat data center provides a direct on-ramp to AWS at Oman's primary subsea cable gateway: https://www.equinix.com/data-centers/europe-colocation/oman-colocation/muscat-data-centers. AWS itself announced a Direct Connect location within Equinix MC1 in Muscat in 2023: https://aws.amazon.com/about-aws/whats-new/2023/03/aws-direct-connect-muscat-oman/. For many enterprise architects, that makes a hybrid design attractive: keep sensitive or latency-sensitive domestic workloads on approved Omani infrastructure, connect to global clouds through Oman-based interconnection, and use Dubai or Riyadh only where global cloud-native services matter more than local control.
D2C's commercial challenge is to own a defensible part of that architecture. It does not need to beat AWS on product breadth. It needs to be trusted for local virtual machines, backup, disaster recovery, email/collaboration, local object storage, sovereign-data hosting and managed support. The buyer's question is not "Can D2C replace every global cloud service?" It is "Which workloads become less risky, easier to procure or easier to recover when they sit with an Omani approved provider?"
Duqm gives the strategic story; Muscat and carrier routes carry the near-term workload
The assignment lens asks whether Duqm can become credible cloud locality outside Dubai and Riyadh. D2C's name makes that question unavoidable, but the public facts suggest the answer is layered. Duqm is the strategic frame. Muscat is the current cloud and customer center. Carrier routes through Oman are the connectivity spine. The operating case for D2C depends on all three.
The Special Economic Zone at Duqm is one of Oman's clearest long-range bets. OPAZ calls it the largest special economic zone in the Middle East and North Africa, established in 2011, covering 2,000 square kilometers, overlooking the Arabian Sea and Indian Ocean, close to global shipping lanes, and open to industry, tourism, trade, logistics and real estate development: https://opaz.gov.om/en/zones/special-economic-zone-at-duqm. The same page lists incentives such as 100 percent foreign ownership, no currency restrictions, no minimum capital requirement, tax exemptions and long usufruct terms. Those incentives are designed for physical investment, but they also create a plausible data-center narrative: land, power planning, port logistics and a policy zone that can host large infrastructure.
The investment base is now large enough to give that narrative weight. OPAZ said investments in Duqm stood at RO 3.6 billion around the first Duqm Economic Forum in 2023 and had risen to RO 6.3 billion after the second forum in October 2024: https://opaz.gov.om/en/media-center/news/2025/economic-free-zones-in-oman-cement-their-status-as-premier-investment-destinations. Oman's foreign ministry separately reported that the Special Economic Zone at Duqm hosted investments exceeding OMR 6 billion, while broader OPAZ-supervised zones and industrial cities were attracting multi-billion-rial capital: https://www.fm.gov.om/en/17485/. In 2026, OPAZ said total committed investment across economic zones, free zones and industrial cities had reached OMR 22.4 billion: https://opaz.gov.om/en/media-center/news/2026/total-committed-investment-in-economic-free-and-industrial-zones-reached-omr-22-4-billion. A Duqm data-center thesis is therefore not built on a vacant-port fantasy; it is attached to a zone where public and private capital has already moved at industrial scale.
Port of Duqm describes itself as part of the SEZD project and a strategic port of the future: https://portofduqm.om/what-we-offer/. IAPH's member profile says the port functions as port authority, terminal operator and landlord, and is part of the SEZAD project established to diversify Oman's economy: https://www.iaphworldports.org/memberports/port-of-duqm-company-saoc/. A data-center operator linked to this geography can sell more than racks. It can sell proximity to industrial tenants, port logistics, energy projects, customs-light import of equipment and a non-Hormuz location that is strategically legible to customers worried about regional chokepoints.
Carnegie's 2026 assessment of Duqm is useful because it is neither boosterism nor dismissal. It describes Duqm as a policy-driven effort to manage risk, with a location outside the Strait of Hormuz and Bab al-Mandab, and argues it is more likely a supplementary node in global trade networks than a guaranteed transformative hub: https://carnegieendowment.org/sada/2026/03/duqm-at-the-crossroads-omans-strategic-port-and-its-role-in-vision-2040. That is the right framing for cloud infrastructure too. Duqm does not have to overtake Dubai to matter. It has to be good enough for certain workloads that want Oman, port-city logic, energy proximity or geographical diversity inside the Gulf.
Power is the main physical constraint behind that ambition. Data centers convert power reliability and cooling into digital capacity. Marafiq's Duqm Integrated Power and Water Plant provides a relevant infrastructure signal, though not a D2C-specific supply contract. Marafiq says the plant has potential capacity of 326 MW of electricity and 36,000 cubic meters of water per day, with seawater intake and outtake infrastructure, and was developed under the Central Utilities Services Agreement with SEZAD: https://marafiq.om/integrated-power-and-water-project-launched-in-oman. For a future Duqm data-center cluster, that kind of utilities backbone is essential. It does not remove the need for dedicated substation design, backup generation, fuel supply, thermal management and water strategy, but it makes the zone's industrial infrastructure more credible than a remote site with no utility base.
The electricity math is sobering. A 1 MW IT load running continuously uses 8,760 MWh a year before cooling and facility overhead. If the all-in business electricity reference point is OMR 0.060 per kWh, as GlobalPetrolPrices reported for Oman in December 2025 using regulator and utility sources, that IT load alone implies about OMR 525,600 a year in energy before PUE uplift: https://www.globalpetrolprices.com/Oman/electricity_prices/. If a facility runs at 1.5 PUE, the same 1 MW of IT capacity becomes about 13,140 MWh of site consumption, or roughly OMR 788,400 at that reference price. A lower non-residential flat tariff of 25 Baisa per kWh, reported in Oman tariff coverage of the new non-residential rules, would still put a 1 MW IT load at about OMR 219,000 a year before PUE: https://www.omanobserver.om/article/1164082/oman/community/new-cost-reflective-electricity-tariff-system-announced. This is why power price, PUE, utilisation and contracted load matter more than glossy cloud language.
Oman's north-south grid and renewables plans also affect the long-term economics. Public power-planning material has identified a Duqm power system, future wind and solar capacity, and interconnection of Oman's main systems as strategic energy moves. For data-center customers, the most important question is not whether the energy is green on a slide. It is whether power price, redundancy, grid stability and heat management can support predictable service-level agreements. Cooling in Oman's climate is a real cost base, and any data-center operator must translate design promises into measurable PUE, water use, maintenance cycles and spare-parts availability.
Connectivity has a similar two-track story. Oman is improving as a subsea and interconnection market. Equinix says it has two data centers in Oman, Muscat and Salalah, with Muscat at the heart of the Asia-Africa-Europe digital ecosystem and Salalah positioned for subsea access: https://www.equinix.com/data-centers/europe-colocation/oman-colocation. Submarine Networks describes the Oman Emirates Gateway as a 275 km cable connecting the UAE and Oman and linking Equinix MC1 in Barka, Equinix SN1 in Salalah and datamena DX1 in Dubai: https://www.submarinenetworks.com/en/systems/intra-asia/oeg. SUBCO describes the Oman Australia Cable as a 9,800 km Muscat-Perth system with about 97 milliseconds round-trip delay and a route avoiding shallow, congested and earthquake-prone waters: https://sub.co/oac/.
Equinix's own MC1 technical specification makes the Muscat alternative especially concrete: MC1 is 60 km west of Muscat, 2 km from the AAE-1 cable landing station, and offers 720 cabinets across 12 data halls with expansion capability for three further phases: https://www.equinix.com.br/content/dam/eqxcorp/en_us/documents/resources/ibx-tech-specs/ibx_mc1_en.pdf. Equinix and Omantel also opened SN1 in Salalah as Oman's second carrier-neutral data center, with Equinix describing Salalah as a route crossroads between Asia, Europe, Africa and Australia: https://newsroom.equinix.com/2024-11-7-Equinix-and-Omantel-Officially-Open-Salalah-SN1%2C-the-Second-Carrier-Neutral-Data-Center-in-Oman. For a D2C customer, these facts create both opportunity and pressure. Oman has real cable geography, but the best-documented carrier-neutral hubs are not D2C facilities.
D2C does not automatically capture that connectivity simply by being Omani. The strongest interconnection claims in public sources belong to Equinix/Omantel facilities, not to D2C. But D2C can benefit from the national connectivity layer if it can offer domestic workloads a reasonable route to carriers, global cloud on-ramps, and recovery locations inside Oman. The commercial story becomes stronger if D2C can show private interconnects to banks, ministries, Ooredoo enterprise networks, Equinix MC1/SN1, or other approved providers. The public record currently shows a small AS and Ooredoo adjacency, not a broad exchange.
That is why the Duqm brand should be read as option value. Today, D2C's public product language and MTCIT address point heavily to Muscat enterprise cloud. Tomorrow, a Duqm-linked data-center strategy could matter if free-zone industrial tenants, port systems, oil-and-gas platforms, logistics operators and government digital projects need local compute that is not just in the capital. The price of turning that option into reality is utilisation. Data centers are expensive when empty. A port-zone facility needs anchor tenants, power contracts, connectivity diversity and an operating team deep enough to convince buyers that local proximity does not mean operational compromise.
Pricing shows a managed-services business, not a commodity hyperscaler
D2C's visible prices are valuable because many local data-center operators avoid publishing anything that resembles a starting point. The official homepage's "starting from" figures make the company readable as a managed-services business. Colocation starts at OMR 500. Virtual machines start at OMR 16. Backup starts at Baisa 0.090 per GB. Email services start at OMR 1.500. Cloud Drive starts at OMR 90. These figures invite comparison, but they should not be over-interpreted without the detailed configuration behind each offer.
The commercial logic likely differs by product line. Colocation revenue is tied to rack space, power draw, cross-connects, remote hands, bandwidth and contract term. In a small market, a full rack can be sticky if the buyer has equipment, compliance needs and local staff constraints. But colocation also exposes the operator to capital intensity: raised floor or slab design, UPS, cooling, generator sets, fire suppression, security, spares, audits and skilled technicians. A low starting price can attract customers, but margin depends on power utilisation and support intensity.
Virtual machines and backup shift the economics toward platform utilisation. If D2C can maintain shared compute, storage and network capacity at high utilisation, it can sell smaller increments to many customers. That is appealing in Oman because many organizations need a local server, backup target or business-continuity environment, but not an entire rack. The challenge is that global clouds have trained buyers to expect elastic capacity, rich APIs, self-service dashboards, snapshots, managed databases, object lifecycle rules, observability, identity integrations and security tooling. D2C's public site uses the language of IaaS and object storage, but it does not show the full control-plane depth that a cloud-native buyer might expect.
Backup as a service may be one of the strongest local products. Backup is less glamorous than compute, but it maps tightly to sovereign and operational risk. A bank, ministry or industrial platform may prefer to keep recoverable data inside Oman even if production systems use a mix of local and offshore infrastructure. Backup also fits a managed-service relationship: customers often need retention design, restore testing, encryption, air-gap logic and ransomware recovery planning more than they need raw storage. D2C's site frames backup as reducing the risk of data loss, access interruption and investment in backup infrastructure and personnel. That is exactly the pain point for mid-market enterprises.
Email and collaboration services occupy a different lane. Global SaaS is dominant here, but local email hosting can still matter for organizations that want in-country mail stores, Arabic-language support, bundled domain administration or a simple alternative to global subscriptions. Cloud Drive as locally hosted object storage is strategically more interesting. Object storage can serve government archives, media assets, backup repositories, application storage and compliance-sensitive documents. But it requires trust in durability, replication, access control and migration path. Customers will ask what happens if they outgrow the service or need to repatriate data quickly.
The cost base behind all this is unforgiving. Omani cloud locality requires local staff, procurement of servers and storage, imported hardware lead times, power contracts, cooling, security audits, software licensing, vendor support and spare-parts management. If the company uses vendor platforms from Dell, Sangfor, VMware, Veeam, Microsoft, Fortinet, Cisco or similar suppliers, currency, licensing and support costs can move independently of local demand. The official site shows technology partners but does not disclose architecture. Network records include a netname Sangfor_Cloud in the 91.132.66.0/24 RIPE-derived summaries, for example through Ipregistry's page: https://ipregistry.co/AS209576/91.132.66.0/24. That hints at vendor-backed cloud infrastructure but should be treated as a registry label, not a full platform disclosure.
Utilisation is the hidden multiplier behind that cost base. A 100-rack room at low occupancy still needs security, monitoring, cooling, maintenance, insurance, software renewals and technical staff. A 4 MW site at half utilisation can look expensive even if its long-term location is right. Competitor disclosures show the range of scale customers can compare against: Datamount says it operates Tier III-class facilities in Muscat Governorate and Ad Dakhiliyah, including Jabal Al Akhdar and Al Bandar: https://www.datamount.om/datacenters. Earlier coverage of Datamount's Jebel Akhdar launch described around 9,000 square meters and about 1,000 racks: https://gecnewswire.com/datamount-launches-omans-largest-data-center-in-jebel-akhdar/. Data Center Dynamics reported Oman Data Park's planned Firq site as a 4.4 MW data center with a 350 kW on-site solar array: https://www.datacenterdynamics.com/en/news/oman-data-park-taps-local-developer-for-14mw-onsite-solar-project-at-data-center/. D2C does not publish comparable rack, square-meter or MW figures, so a buyer cannot yet benchmark its utilisation risk against named local rivals.
Supplier dependence is therefore part of the investment case. A small cloud provider can move fast, customize and support local buyers closely. It can also be exposed to vendor roadmaps, renewal pricing, hardware scarcity and the technical debt of maintaining older virtualization stacks. The way to reduce that risk is to publish clearer product specifications, service levels, backup durability, security scope, interoperability and customer exit terms. D2C's public site gives a buyer enough to inquire. It does not yet give enough to underwrite a mission-critical migration without due diligence.
The revenue upside comes from bundling. A customer who buys IaaS may also need backup, security services, monitoring, disaster recovery and managed support. A government entity that needs approved local hosting may prefer a single accountable vendor over stitching together offshore cloud, local telecom and separate security consultants. A reseller can package D2C capacity into sector-specific offers. These bundles can produce better margins than raw compute. But bundles also increase delivery risk: the provider must be excellent at account management and operations, not only facility management.
The competitive field is bigger than Oman's approved-provider list
D2C competes locally with approved Omani providers, regionally with Dubai and Riyadh defaults, and architecturally with hybrid designs that combine global clouds with Omani connectivity. That makes its competitive set wider than the list of companies in one register.
Inside Oman, the approved register names Oman Data Park, Datamount, D2C, Cloud Acropolis, Omantel and other providers with varying SaaS, PaaS and IaaS scopes. That already creates buyer choice. Oman Data Park has long marketed itself as a major local managed-services and cloud provider. Datamount has developed a differentiated data-center story around Omani terrain and energy. Cloud Acropolis appears in the register with PaaS and IaaS accreditation. Omantel has the national-carrier position and partnerships with Equinix. D2C's advantage is likely its Ooredoo connection, local cloud catalogue and D2C brand history; its disadvantage is that competitors can claim broader scale, stronger interconnection, or clearer facility narratives.
The named competitors have their own public numbers. Oman Data Park says it has served more than 500 local and international institutions and stores data in Level 3 data centers at Al Wattayah, Rusayl and Duqm: https://product.omandatapark.com/p/data-storage/. Datamount markets a multi-location footprint that includes Jabal Al Akhdar and Al Bandar. Equinix says its Oman footprint totals about 34,000 square feet, or 3,200 square meters, across Muscat and Salalah, with direct access to the only hyperscale cloud on-ramp available in the country: https://www.equinix.com/data-centers/europe-colocation/oman-colocation. Those figures do not prove those rivals are better for every workload, but they force D2C to compete against specific capacity and interconnection claims rather than an abstract local market.
The local market is also not isolated from hyperscalers. Oman Observer reported in 2022 that Oman would host an AWS Local Zone, with local storage and lower-latency processing pitched as benefits for local customers: https://www.omanobserver.om/article/1129753/business/economy/oman-to-host-amazons-first-aws-local-zone-in-mena-region. AWS later announced Direct Connect in Muscat: https://aws.amazon.com/about-aws/whats-new/2023/03/aws-direct-connect-muscat-oman/. AWS's own Middle East partner guidance says it has a Local Zone in Oman, Outposts availability across Oman and neighboring countries, and Middle East regions in Bahrain and the UAE, with a Saudi Arabia region planned and a USD 5.3 billion investment commitment: https://aws.amazon.com/blogs/publicsector/how-aws-can-help-partners-grow-in-the-middle-east/. Even where Oman does not have a full public cloud region, hyperscaler access through local partners changes buyer expectations. A CIO can ask why a workload should sit on a local provider's IaaS rather than an AWS-connected environment with broader tooling.
Dubai and Abu Dhabi remain the Gulf's mature default for many regional workloads. AWS says its UAE region has three Availability Zones: https://aws.amazon.com/blogs/aws/now-open-aws-region-in-the-united-arab-emirates-uae/. Microsoft lists UAE North in Dubai, UAE Central in Abu Dhabi, and Qatar Central in Doha in its Azure region list: https://learn.microsoft.com/en-us/azure/reliability/regions-list. Oracle lists live cloud regions in UAE East (Dubai), UAE Central (Abu Dhabi), Saudi Arabia West (Jeddah) and Saudi Arabia Central (Riyadh): https://www.oracle.com/sa/cloud/public-cloud-regions/. Saudi Arabia is accelerating too: Amazon said its Saudi region would consist of three Availability Zones at launch: https://press.aboutamazon.com/2024/3/aws-to-launch-an-infrastructure-region-in-the-kingdom-of-saudi-arabia, and Microsoft confirmed customers would be able to run workloads from its Saudi Arabia East data-center region from Q4 2026: https://news.microsoft.com/source/emea/2026/02/microsoft-confirms-saudi-arabia-datacenter-region-available-for-customers-to-run-cloud-workloads-from-q4-2026/. Market research summaries put the GCC data-center market on a steep growth path: Arizton says the GCC market was valued at USD 3.48 billion in 2024 and is expected to reach USD 9.49 billion by 2030, growing at about 18 percent CAGR: https://www.arizton.com/market-reports/gcc-data-center-market-investment-analysis-report. Businesswire's Middle East colocation market summary cites large expected investment from 2025 to 2030, with Saudi Arabia representing a major share: https://www.businesswire.com/news/home/20260122070624/en/Middle-East-Data-Center-Colocation-Outlook-Forecast-Report-2025-A-%247.7-Billion-Market-by-2030---AI-Adoption-Sustainability-Mandates-and-Smart-City-Expansion-Drive-Infrastructure-Investments---ResearchAndMarkets.com.
Those figures are market-level and vendor-sponsored, so they should be used as context rather than precise forecasts. But the direction is obvious: Gulf buyers will have more data-center choice, not less. That creates pressure on local Omani providers to define why their locality matters. D2C cannot win on the same axis as Khazna, Gulf Data Hub, Equinix, stc, Center3 or the largest Saudi/UAE projects. It can win by being the Omani component in a risk-conscious architecture.
The most practical competitive thesis is "local first for the right workloads, regional cloud for the rest." In that model, D2C hosts workloads that need Omani approval, close support, local backup or data-residency comfort. Dubai, Abu Dhabi or Riyadh host applications that need global managed services, massive scale or AI accelerators. Equinix/Omantel facilities provide interconnection and cloud on-ramps. Ooredoo provides access and enterprise connectivity. The buyer does not make a religious choice between local and global; it creates a workload placement policy.
For D2C, this means partnership may matter as much as rivalry. If Ooredoo Oman remains a controlling or strategic shareholder, D2C can ride telecom enterprise sales and connectivity bundles. If D2C builds practical interconnects to Equinix MC1/SN1, it can become more valuable as a local node in hybrid cloud. If it proves strong backup and disaster recovery, it can serve customers who keep primary workloads elsewhere. If it publishes stronger compliance evidence, it can be shortlisted for regulated data even when it is not the cheapest platform.
Non-official market chatter suggests buyers do notice local-provider cost and maturity gaps. A Reddit thread asking Oman IT professionals about cloud-service providers lists Oman Data Park, Ooredoo, Cloud Acropolis, Awasr, Data2Cloud, Datamount, Equinix and others, and one participant says local options are likely expensive compared with established global providers: https://www.reddit.com/r/Oman/comments/1b6fkn2/oman_it_pros_what_cloud_service_providers_do_you/. DataCenterMap lists D2C as a cloud and colocation provider in Muscat and says its exact data-center location is not public: https://www.datacentermap.com/oman/muscat/d2c/. Those are weak sources individually, but together they capture the real market question: D2C is visible in local buyer conversation and provider directories, while pricing and facility transparency remain friction points.
The competitive question therefore becomes evidence. A buyer can accept higher cost if the local provider proves resilience, auditability, support quality and recovery. The same buyer will reject a local provider if the only argument is patriotism or vague sovereignty language. D2C's current public evidence is enough to support a differentiated Omani hosting thesis, but the next level would require published facility locations, current certifications, uptime history, interconnection partners, platform specifications and customer case studies that quantify outcomes rather than merely naming services.
Risk is operational before it is geopolitical
Because Duqm sits inside a strategic geography, it is tempting to make geopolitical risk the center of the story. There is a case for that. Oman has a distinctive regional posture, Duqm is outside the Strait of Hormuz, and port-zone infrastructure can be sold as diversity from more crowded Gulf hubs. But for D2C customers, the more immediate risks are operational: power, cooling, network diversity, support depth, supplier concentration, certification scope and utilisation.
Power and cooling dominate data-center economics. Oman's climate makes cooling a material operating cost, and cooling failures are not abstract. A provider must manage chillers or direct-expansion systems, airflow, dust, humidity, thermal monitoring, maintenance windows and spare parts. If D2C's facilities are in Muscat, Smail or other Omani sites rather than a large new Duqm campus, each site has its own utility and cooling profile. The official site's Tier 3+ and uptime claims need facility-specific evidence to be investment-grade.
This is where the Duqm energy story and the Muscat connectivity story can pull in different directions. Duqm has the industrial-land and utility narrative, including Marafiq's 326 MW power and water plant. Muscat/Barka has the better-documented cable and cloud-on-ramp narrative, including Equinix MC1 near AAE-1 and AWS Direct Connect. Salalah has the emerging north-south diversity narrative, with SN1 and Ooredoo's 2Africa landing plan. D2C has to show which of those geographies it actually uses for production, backup and customer colocation. Without that mapping, the buyer cannot know whether it is paying for Duqm resilience, Muscat interconnection, carrier-backed managed service, or some blend of the three.
Network diversity is the second risk. RIPEstat's neighbor view showing one unique neighbor is not necessarily the full commercial network architecture, but it does make the public footprint look concentrated. If a buyer needs high availability to multiple carriers, it should ask for diagrams, carrier lists, cross-connect options, DDoS providers and failover tests. If the buyer mainly needs local backup and managed hosting, the threshold may be lower. The key is matching workload criticality to observed network depth.
Supplier concentration cuts both ways. Ooredoo ownership and upstream adjacency can make D2C stronger because a major telecom shareholder can supply capital discipline, connectivity, enterprise sales and operational processes. It can also make D2C less carrier-neutral in perception. Some customers will welcome that because they already buy from Ooredoo. Others will want independence or multi-carrier redundancy. D2C's public route to credibility is to present the carrier relationship as a strength while still proving that customer resilience is not dependent on a single network path.
Regulatory risk is more nuanced. Approval to serve government entities is a positive signal, but regulation can also change. Oman issued specific data-center and cloud-computing regulations through the Telecommunications Regulatory Authority in 2024, reported in legal summaries as requiring permits for entities providing cloud or data-center services in Oman: https://www.mondaq.com/data-protection/1540350/navigating-the-new-telecommunications-regulatory-authority-tra-regulations-on-cloud-computing-and-data-centres-in-oman-legal-implications-and-subscriber-challenges. The public MTCIT service page aligns with the idea that providers need license and approval steps. If rules tighten around data classification, audits, local ownership, incident reporting or service levels, approved providers may benefit, but they will also face higher compliance cost.
Geopolitical risk still matters, mainly through customer perception and cable routes. Oman can be positioned as a neutral and diverse location, yet all Gulf infrastructure remains exposed to regional tension, cable incidents, import dependency, and the economics of energy transition. The Oman Emirates Gateway and Oman Australia Cable improve route diversity, but D2C's public evidence does not show direct control over those cables. It benefits from Oman's national connectivity environment rather than owning the whole path.
Utilisation risk is the most underappreciated part of the business model. Data centers are fixed-cost machines. Empty racks and underused servers destroy margins. A small provider can be profitable if it sells sticky managed services with good support margins, but a large facility strategy needs anchor tenants. If D2C or any Duqm-linked data-center operator builds ahead of demand, it must carry power commitments, depreciation, maintenance and staff before revenue fills the halls. The Gulf is full of ambitious data-center announcements; utilisation separates infrastructure from real platforms.
The public record does not disclose D2C revenue, EBITDA, capacity utilisation, rack count, megawatts, churn, customer concentration or backlog. Ooredoo filings establish ownership history and commercial-operation timing, but they do not provide a standalone operating picture deep enough to value D2C independently. That absence is itself a risk. Buyers and investors should not assume that approved-provider status equals scale or profitability.
The utilisation gap is not a minor disclosure issue; it changes the economics of every public price. A virtual machine starting at OMR 16 is attractive only if the platform underneath has enough paid occupancy to absorb fixed power, licensing and support costs. Colocation from OMR 500 can be profitable if racks are dense, power is priced correctly and support is disciplined; it can be loss-making if power draw, cooling, spares and remote hands are underpriced. Local object storage from OMR 90 can be sticky if it becomes a backup or archive target, but customers will scrutinize durability and exit path. Without capacity and utilisation data, the article's judgment must stop short of saying D2C has proven data-center economics. It has proven market presence and policy relevance.
The risk-adjusted view is therefore conditional. D2C looks suitable for Omani workloads that value local hosting, managed service and regulatory alignment. It looks less proven for workloads requiring hyperscale services, deep peering, globally distributed resilience or massive compute. That does not make it weak. It makes it a specialized local platform whose best use cases are narrower than its strategic name suggests.
The facts that would change the judgment
Several facts would materially strengthen the D2C thesis. The first is current, facility-specific certification. The older TIA/EPI record is useful history, but it expired in 2019 and relates to a named computer room: https://tiaonline.org/942-datacenter/duqm-data-centre-saoc-d2c-computer-room-level-2-smail-industrial-estate-al-dakhiliyah-governorate/. If D2C publishes current Tier III or TIA-942 certificates, ISO certificate scopes, audit bodies, facility locations and renewal dates, the trust case improves immediately. Generic certification claims help marketing; current certificate scope closes procurement gaps.
The second is capacity disclosure. Rack count, white-space area, power capacity, redundancy design, PUE range, backup fuel autonomy, water strategy and site locations would let customers separate a small hosted platform from a serious multi-site data-center operator. The official site says D2C offers three data centers in Oman. If those sites are named and their roles explained - production, disaster recovery, edge, customer colocation - D2C's resilience story becomes much clearer.
The third is interconnection depth. Additional visible upstreams, carrier lists, private cloud on-ramps, internet-exchange participation, DDoS partners and route-security details would change the network assessment. RIPE and RIPEstat currently show a credible but small routed footprint. A stronger interconnection story would let D2C compete for higher-criticality workloads and not only local managed hosting.
The fourth is customer evidence. Public case studies with sector, workload type, availability outcome, migration scope and compliance problem solved would be more persuasive than broad claims. The existing FRiENDi mobile and iNNOVATEQ references are useful, but more detail would show whether D2C is hosting core production, backup, support applications, monitoring platforms or peripheral systems.
The fifth is proof of Duqm-specific deployment. If the company demonstrates active data-center capacity inside the Duqm special economic zone, with power, cooling and connectivity details, the strategic narrative becomes more than nameplate value. Duqm's free-zone incentives, port logistics and energy infrastructure could then be tied to a measurable facility. Without that proof, D2C should be treated as an Omani cloud provider with a Duqm-linked legal and strategic identity, not necessarily as the operator of a large Duqm campus.
The sixth is pricing transparency. Starting prices attract leads, but enterprise customers need total cost. Bandwidth pricing, backup retention, restore fees, support levels, cross-connects, public IP charges, snapshots, security add-ons and exit costs all affect the real comparison with Dubai, Riyadh or global cloud. Transparent pricing would help D2C make the case that local does not mean opaque.
The seventh is sovereign-workload evidence. D2C's register position shows eligibility, not wins. Named public-sector deployments, framework agreements, approved service catalogues, disaster-recovery references or anonymized ministry workloads would materially raise confidence. The most persuasive case would show not only that the company may host government data, but that customers choose it for specific regulated workloads because the Oman-based control surface solves a procurement or risk problem better than Dubai, Riyadh or a self-managed server room.
On the negative side, several facts would weaken the thesis. Expired or narrow certification scope would make the trust story less robust. Continued single-neighbor visibility would limit claims of network resilience for critical production. Low utilisation or heavy dependence on one or two customers would raise financial risk. Unclear data residency terms would blunt the sovereign-cloud advantage. Weak backup restore performance would damage one of the most plausible product wedges. Any sign that government accreditation had lapsed would materially affect the buyer case.
The current judgment sits between enthusiasm and skepticism. D2C is not an empty shell; it has a public site, MTCIT approval, RIPE membership, AS209576, routed prefixes, visible Ooredoo linkage and commercial cloud products. It is also not yet publicly proven as a large, highly interconnected, multi-site Omani cloud platform with deep capacity. The investment question is whether Oman produces enough regulated, government-linked and industrial demand to let D2C grow profitably without trying to mimic hyperscale clouds.
Bottom line
Duqm Data Centre SAOC is best understood as a local-cloud option whose importance exceeds its visible routing size. The company gives Oman a domestic provider story: local cloud products, approved-provider status, Ooredoo-linked ownership history, and internet-number evidence that shows real operation rather than a paper brand. It also exposes the cost of making Omani cloud locality credible. Locality must be backed by power, cooling, network diversity, current certificates, support depth, customer proof and clear pricing.
The strongest case is for workloads where Omani data location, government approval and managed support are more important than hyperscale breadth. Backup, disaster recovery, local virtual machines, regulated SaaS hosting, government-adjacent workloads and industrial monitoring are plausible fits. The weakest case is for customers expecting a Dubai-style cloud ecosystem, dense carrier-neutral peering, broad managed services, or massive AI compute.
D2C's strategic opportunity is to stop being judged as a small substitute for Dubai and start being judged as a necessary Omani component in hybrid Gulf infrastructure. That requires hard evidence, not slogans. If the company can show current facility certification, richer interconnection, clear multi-site capacity and strong customer outcomes, the Duqm-linked thesis becomes more persuasive. If the public record remains mostly registry entries, starting prices and broad certification claims, D2C will remain credible but bounded: useful for local cloud locality, not yet proof that Duqm has become the Gulf's next cloud node.