Every Cloud Region in Saudi Arabia, and Which Ones Actually Exist

Five providers, six regions — and neither Amazon Web Services nor Microsoft is among them. As of 31 July 2026, every generally available Saudi Arabia cloud region belongs to Google Cloud (Dammam, me-central2), Oracle (Jeddah, me-jeddah-1; Riyadh, me-riyadh-1), Huawei Cloud (Riyadh), Alibaba Cloud operated by the SCCC joint venture (Riyadh, me-central-1), or Tencent Cloud (Riyadh). AWS and Microsoft Azure have each announced a Saudi region. Neither has launched one.

That gap between announcement and availability is the whole point of this page. AWS committed more than $5.3bn to a Saudi region on 4 March 2024 and targeted 2026 [S15]. Microsoft confirmed in February 2026 that its Saudi Arabia East region would carry customer workloads from Q4 2026 [S4]. Both commitments are real. Neither is a region you can deploy into today, and a large volume of secondary coverage — vendor blogs, market reports, even compliance guidance — states otherwise.

Every claim in the table below is checked against the provider’s own published region list rather than its press release. Where the two disagree, the region list wins.

Last verified: 31 July 2026

What a cloud region is, precisely. A region is a named, purchasable set of isolated data centers exposed as a single API endpoint with its own service catalogue and its own residency boundary. It is not the same thing as a data center: a provider can own racks in the Kingdom, as several do, without offering a region. This page covers regions only. For the physical build-out see the Saudi data center market; for the sector overview, the Saudi Arabia data centers guide.

Which Cloud Providers Are Live in Saudi Arabia?

Five. The table is the answer to the question this page exists to settle.

Sources for each row are the providers’ own region documentation: AWS [S1][S2], Azure [S3], Google [S5], Oracle [S7][S8][S9], Alibaba [S10], Tencent [S11], Huawei [S16].

And the money and the catalogue, which is where the marketing and the engineering diverge:

Does AWS Have a Region in Saudi Arabia?

No. This is the single most misreported fact in Saudi cloud coverage, and AWS settles it on its own page.

As of 31 July 2026 the AWS global infrastructure page reads: “The AWS Cloud spans 123 Availability Zones within 39 Geographic Regions, with announced plans for 7 more Availability Zones and 2 more AWS Regions in the Kingdom of Saudi Arabia, and Chile” [S1]. The Kingdom is listed among the announced, not the built. Independently, the Available AWS Regions table in AWS documentation lists three Middle East entries — me-south-1 (Bahrain), me-central-1 (UAE) and il-central-1 (Israel, Tel Aviv) — and no Saudi Arabia row [S2]. A me-central-2 region code circulates widely in third-party write-ups; it appears in no AWS-published table.

The figure conflict, resolved. Several secondary sources state that the AWS Saudi region reached general availability in January 2026 with three Availability Zones around Riyadh. That claim propagates through reseller blogs, data-center project trackers and at least one cloud-compliance guide that names “AWS Riyadh” as a region satisfying Saudi residency requirements. Against it stand three AWS-controlled surfaces that agree with each other: the global infrastructure headline count, the regions-and-AZ landing page, and the documentation region table. If the region had launched, the count would read 40 Regions and one announced. It reads 39 and two. The AWS-published position is that the region does not yet exist, and it is the position an architect should build against.

What AWS does have in the Kingdom is real but limited: a CloudFront edge location in Jeddah, launched 24 January 2025 and priced within the Middle East region tier [S15], and AWS Outposts, shippable to Saudi customer premises since April 2024. Neither gives you a region endpoint, a regional service catalogue, or in-region managed databases. Separately, AWS and HUMAIN announced an “AI Zone” on 13 May 2025 backed by more than $5bn [S19], and expanded that into HUMAIN ONE, an enterprise AI operating system built on AWS, in May 2026. Both sit alongside the region programme rather than substituting for it.

Is Google Cloud Available in Saudi Arabia?

Yes — with a commercial gate that most comparisons omit entirely.

The Dammam region me-central2 opened on 15 November 2023 with three zones (me-central2-a, -b, -c). It is the oldest Western hyperscaler region in the Kingdom and, on machine-type breadth, the widest. But Google’s own access documentation is explicit: “Access to Google Cloud services from the (me-central2) Dammam region is available only to KSA-based customers that have signed up to purchase cloud services through CNTXT” [S5]. Customers paying by credit card must switch to invoiced billing; non-Saudi entities must contact CNTXT directly.

The Aramco structure, precisely stated. In December 2020, Saudi Aramco Development Company and Google Cloud signed a strategic alliance under which Google Cloud would establish and operate the region while a separate company supplied cloud solutions to enterprise customers. That company is CNTXT, an Aramco joint venture with the Norwegian industrial-software firm Cognite, launched 19 June 2022. Google owns and runs the infrastructure. CNTXT owns the customer relationship. It is a channel arrangement, not a co-owned region — a distinction that matters for procurement, support escalation and contracting, and one that no competing comparison page draws.

The sovereignty layer is genuinely differentiated. Since 20 August 2024, Sovereign Controls by CNTXT has been generally available via Assured Workloads, offering external key management with key access justifications: the encryption keys sit outside Google infrastructure, CNTXT operates the external key manager with the Saudi Information Technology Company (SITE) and Fortanix, and the customer can deny a key-access request, including one arising from an extraterritorial legal demand. Abdullah Jarwan, CEO of CNTXT, and a parallel package sold directly by Google as Sovereign Controls for KSA give buyers two routes [S6].

Where the catalogue stops. Dammam offers 274 of 519 Compute Engine machine types; us-central1 offers 516 [S18]. The absent families are the ones AI teams need: no A2, A3 or A4. Vertex AI’s core platform went live in Dammam in May 2024, but the accelerator classes that make frontier training viable are not in the region. If your workload is a Kubernetes estate, a data warehouse or a regulated line-of-business application, Dammam is a serious option. If it is a training run, it is not.

Does Microsoft Azure Have a Saudi Arabia Region?

Not yet, and the primary sources agree with each other for once.

Microsoft’s Azure regions list — the reliability documentation, last updated 28 July 2026 — shows four Middle East regions: Israel Central, Qatar Central, UAE Central and UAE North. There is no Saudi Arabia entry, and none flagged as coming soon [S3]. In February 2026 Microsoft confirmed the position directly: “From Q4 2026, Saudi Arabia’s public and private sector organizations can run cloud workloads locally, accessing secure, low latency cloud and AI services to advance Vision 2030 priorities” [S4]. The region is named Saudi Arabia East, sits on one site in the Eastern Province, and will launch with three availability zones. Brad Smith, Vice Chair and President of Microsoft, and Turki Badhris, President of Microsoft Arabia, appeared alongside H.E. Eng. Abdullah bin Amer Al-Swaha, Minister of Communications and Information Technology, at the confirmation.

Microsoft had said construction on three sites was complete in December 2024, with availability expected in 2026. The February 2026 statement narrowed that to the final quarter. A build finished in late 2024 that will not carry customer workloads until late 2026 is a two-year gap between concrete and endpoint — and the reason is the same one that governs every other announced region in the Kingdom. See why grid power, not chips, is the binding constraint.

Oracle Runs Two Saudi Regions. The Third Never Arrived.

Oracle has been the most aggressive hyperscaler on region count in the Kingdom and is the only one with two live regions, but the count deserves scrutiny.

Jeddah (me-jeddah-1, region key JED) went live on 1 February 2020, making it the first hyperscaler region in Saudi Arabia by nearly four years [S8]. Riyadh (me-riyadh-1, region key RUH) followed on 31 July 2024 per Oracle’s own release note, announced publicly on 6 August 2024 as part of a $1.5bn Saudi commitment [S9]. Richard Smith, Executive Vice President and General Manager, EMEA Cloud Infrastructure at Oracle, framed it at launch: “The Oracle Cloud Riyadh Region will help accelerate adoption of cloud and AI technologies to boost innovation across all sectors of the Saudi economy” [S9]. H.E. Eng. Haytham Alohali, Vice Minister at the Ministry of Communications and Information Technology, spoke for the government side.

The third region, in NEOM, was announced in October 2021 and reconfirmed in the February 2023 investment release. It does not appear in Oracle’s commercial region list at 31 July 2026 [S7]. That is four years and nine months from announcement to non-existence — the longest announced-to-absent gap in the Saudi market and a useful calibration for how to read any hyperscaler region announcement here.

The resilience caveat nobody prices. Both Saudi Oracle regions have one availability domain. Oracle’s documentation states that it launches regions in new geographies with a single availability domain to move quickly, and provides three fault domains inside it — separate racks, power distribution and top-of-rack switching. Oracle argues, with Gartner support, that three fault domains give protection comparable to three availability zones. The honest counter is Oracle’s own: a single-AD deployment offers no protection if the whole availability domain fails, and Oracle’s recommended disaster-recovery pattern for such regions is replication to a remote region [S7]. For a Saudi customer under residency constraints, the only in-Kingdom remote Oracle region is the other one — Jeddah and Riyadh, about 850km apart — which is a workable DR pair but a materially different architecture from a three-AZ region.

Oracle also supplies the Kingdom’s most substantial sovereign offering through a third party: stc deploys Oracle Alloy, announced 23 April 2024 and extended by a partnership worth more than SAR2bn ($533m) on 14 May 2025, giving stc a dedicated cloud running more than 100 Oracle Cloud Infrastructure services from center3 facilities. Alloy is not a public region — you cannot select it from Oracle’s region picker — but it is a real, purchasable, in-Kingdom Oracle estate under Saudi operational control.

The Chinese Providers, and the Procurement Exposure They Carry

Three of the six live Saudi regions are Chinese, and they are the reason the Kingdom looks better on region count than on usable Western capacity.

Huawei Cloud Riyadh launched in September 2023 with three availability zones, hosted inside a center3 facility, and holds a Class C licence from the Communications, Space and Technology Commission (CST). Huawei announced $400m of Saudi cloud investment over five years at LEAP 2025 and joined the government’s National Framework Agreement in December 2024 [S16].

Alibaba Cloud Riyadh is the oldest of the three. SCCC — the Saudi Cloud Computing Company, a joint venture of Alibaba Cloud, stc Group, eWTP Arabia Capital, the Saudi Company for Artificial Intelligence and SITE — launched services on 5 June 2022 with two Riyadh data centers and a stated ambition of 16 across the Kingdom [S20]. It now offers roughly 90 localised Alibaba products. The structural detail that matters: Alibaba Cloud’s own Elastic Compute Service documentation lists Riyadh as me-central-1 and flags it as a partner region, distinct from the regions Alibaba operates itself [S10]. Support paths, service parity and contractual counterparty all follow from that flag.

Tencent Cloud entered on 10 February 2025 at LEAP with its first Middle East region, me-saudi-arabia, carrying two Riyadh availability zones and a commitment of more than $150m [S11][S17].

The exposure, stated precisely. This is a procurement and defence-contracting risk, not a general export-control ban, and the distinction is worth getting right. On 8 June 2026 the US Department of Defense added Alibaba, Baidu and Tencent to its 1260H list of Chinese military companies. The designation imposes no immediate sanctions; it bars the Department of Defense from awarding direct contracts to designated firms from 30 June 2026, with indirect procurement restrictions following in 2027. Alibaba sued in the Northern District of California on 23 June 2026, arguing the listing has “no basis in fact or law” [S21][S22]. Huawei’s position is different and older: it sits on the Commerce Department’s Entity List, which is an export-control instrument.

For a customer running restricted workloads, the practical consequences are concrete. If you hold or intend to bid for US defence work, hosting on an Alibaba or Tencent region — including one operated by a Saudi joint venture — is a compliance question your contracting officer will ask about, and the answer changes again in 2027. If your workload involves US-origin controlled technology, the Huawei relationship raises a separate and harder set of questions. None of this makes these regions unusable; most Saudi enterprise workloads are untouched. It does mean the region choice is a legal decision as much as a technical one, and it is not reversible cheaply. The US export-control regime on AI accelerators is the adjacent constraint on the compute itself.

The Sovereign Layer: HUMAIN, stc, SCCC and Center3

Saudi Arabia’s domestic providers are frequently listed alongside the hyperscalers as though they were interchangeable. They are not, and the differences are the most decision-relevant thing on this page.

HUMAIN is not a cloud you can buy. The PIF-owned company broke ground on twin 100MW campuses in Riyadh and Dammam in August 2025 and committed to going live in Q2 2026. That quarter closed on 30 June. No announcement, filing or credible report confirms either site is operational — the full evidence trail is in our dated status tracker for HUMAIN’s Riyadh and Dammam sites. Even on the company’s own roadmap, its compute is sovereign capacity under PIF control rather than a public region with a price list and an API endpoint. For the corporate picture see the HUMAIN company profile and its infrastructure programme.

stc operates the deepest local stack. Through SCCC it resells Alibaba Cloud; through Oracle Alloy it runs a dedicated OCI estate; through stc.AI it launched a sovereign AI platform hosting open-weight models; and through center3 it owns the physical layer under much of the rest. Center3 runs 25 carrier-neutral data centers, 16 subsea cable systems and three internet exchanges, targets 1GW by 2030 with roughly 200MW online by 2026, and hosts Huawei’s Saudi region and stc’s Alloy deployment [S23]. Huawei’s Saudi “region” and stc’s “sovereign cloud” are, physically, often the same buildings.

Mobily is a colocation and connectivity player rather than a region operator: $905m (SAR3.4bn) committed to data centers and subsea cables, roughly 39MW of planned capacity, and landings including SEA-ME-WE 6 at Yanbu [S24]. SITE appears as a shareholder in SCCC and as a partner in Google’s external key management, not as a region operator in its own right.

The pattern is consistent: the Saudi sovereign layer supplies buildings, cables, key custody and channel, while the region endpoints themselves belong to foreign vendors. That is a deliberate structure, and it means “sovereign cloud” in the Kingdom generally denotes operational and key control rather than domestic software.

Which Major Cloud Providers Have No Saudi Region?

Confirmed absences as of 31 July 2026, which is often exactly what a searcher needs:

• Amazon Web Services — announced 4 March 2024, not launched [S1][S2].
• Microsoft Azure — announced, targeted Q4 2026, not launched [S3][S4].
• IBM Cloud — no Saudi multizone region. IBM has a Riyadh regional headquarters, a $200m+ software lab commitment and an announced IBM–AWS innovation hub in Riyadh, but no IBM Cloud region.
• Salesforce — Hyperforce is live in the UAE; no confirmed Saudi Hyperforce region.
• SAP — SAP’s Saudi public cloud environment is real, and SAP made the Kingdom the first country to host the full SAP Business Network for the public sector with local residency in October 2025 — but it runs on Google Cloud, not on SAP-owned Saudi infrastructure [S25]. It is a residency arrangement, not an SAP region.
• Oracle NEOM — announced October 2021, still absent from Oracle’s commercial region list.

A useful test when reading any Saudi cloud claim: ask whether the provider’s own region documentation contains a row. If it does not, what exists is a data center, a colocation footprint, a reseller arrangement or a press release — all of which can be valuable, and none of which is a region.

Do You Have to Store Data in Saudi Arabia?

It depends on the class of data and the identity of the customer, not on a single localisation statute — and the widely repeated claim of a blanket personal-data residency rule does not survive contact with the current text.

The Personal Data Protection Law permits transfer outside the Kingdom on conditions, through SDAIA standard contractual clauses, binding common rules or an accreditation certificate. Our companion analysis of how Saudi Arabia regulates AI and what actually binds a deployment works through the PDPL transfer mechanism, the penalty tiers and the unpublished adequacy list in full; this page does not repeat it. The framework overview sits at Saudi data protection and privacy, with classification and control detail at Saudi data privacy and cyber compliance.

Where residency does bite, it bites through three channels:

Government data. The obligation here is hard. Morgan Lewis, writing on 27 March 2026, puts it flatly: “For government agency data, localisation is exclusive: all data must remain within Saudi Arabia, subject only to narrow law-based exceptions” [S13]. Which datasets fall inside that rule is determined by National Data Management Office classification — four levels, running from top secret to public — which drives storage location, encryption, retention and whether the data may leave the Kingdom at all. Classification is a precondition for cloud onboarding, not a downstream compliance step. See NDMO data governance policies and the SDAIA institutional profile.

Financial-sector data. Offshore hosting of financial-institution data requires prior approval from the Saudi Central Bank. In practice, Morgan Lewis observes, many providers default to full in-Kingdom hosting to avoid the approval process [S13]. That is a procurement preference produced by a legal friction, not a prohibition — and the distinction matters when you are pricing an architecture.

Cybersecurity controls. The National Cybersecurity Authority’s Cloud Cybersecurity Controls, currently CCC-2:2024, set minimum requirements for both cloud service providers and cloud service tenants, and the NCA states the document was updated on 31 July 2025 specifically “to reflect changes related to data localization requirements” [S12]. Alongside CST’s Cloud Computing Regulatory Framework, under which providers must be registered and classified, this is the operative layer for public entities and critical infrastructure. The Saudi cybersecurity stack covers the wider control set.

The honest summary: if you are a private company processing ordinary commercial data, no Saudi law requires you to use a Saudi cloud region. If you sell to government, operate critical infrastructure, or are regulated by SAMA, you will end up in one — whether by rule or by tender condition.

The Copyright Position That Makes In-Kingdom Training Different

One paragraph, because it is a genuine differentiator and it is easy to overstate.

From 12 August 2026, Article 26(4) of Saudi Arabia’s new Copyright Law, promulgated by Royal Decree M/169, permits copying a work to develop artificial-intelligence products and algorithms “without the author’s permission and without compensation,” subject only to lawful publication, lawful acquisition of the original copy, and proportionality — with no rights-holder opt-out, no attribution duty and no commercial carve-out on the face of the text. That is a materially different legal proposition from training in an EU region, where the text-and-data-mining exception collapses the moment a publisher inserts a machine-readable reservation, or a UK one, where the position remains contested. For a model developer, in-Kingdom compute is not merely closer to Arabic data; it sits under a statute that expressly licenses training on it. Our full analysis of Article 26 of the 2026 Copyright Law covers the effective-date arithmetic, the Berne three-step problem and the position for publishers. Two cautions belong with the claim: a copyright exception is not a lawful basis for processing personal data, so the PDPL applies independently to any corpus containing personal information; and Article 26(4) protects ingestion, saying nothing about whether outputs infringe. The wider framework sits at Saudi intellectual property.

Power Decides Which Announced Regions Actually Arrive

A region that exists on a map but cannot get a grid connection is a different asset from one that can, and this is the mechanism behind every date on the table above.

Saudi Arabia operated 467MW of data center load in Q1 2026 against a 6.6GW target for 2034 — a fourteen-fold gap that has to be closed by transmission and generation, not by procurement of servers. The clearest single piece of evidence is that HUMAIN’s flagship 6GW Al-Saad campus went to tender in May 2026 for a 380/132/33kV network, 500MVA and 200MVA substations and a 2,000MVA bulk supply point: the first procurement on the Kingdom’s flagship AI project was electrical infrastructure, not compute. Our pillar analysis, Saudi Arabia’s AI power constraint is the grid, not the chips, sets out the energisation queues, gas-turbine procurement and cooling-water constraints in detail, and the site-by-site count of what is energised today shows how much of that 467MW belongs to the cloud regions above.

Read the region table through that lens and the pattern resolves. Microsoft finished building three Saudi sites in December 2024 and will not carry customer workloads until Q4 2026. Oracle announced NEOM in October 2021 and has not launched it. AWS announced in March 2024 for 2026 and had not launched by the end of July 2026. Three different vendors, three different corporate cultures, one shared dependency. The Kingdom’s own promotional ranking makes the point unintentionally: the methodology that placed Saudi Arabia second globally for data-center market attractiveness weights power availability and land enablement at 58% of the score.

Latency, Cables and What Routing Through the UAE Costs

The standard advice for a Saudi workload with no in-Kingdom region is to run in me-central-1 (AWS UAE) or UAE North (Azure) and accept the round trip. The measured cost of that advice is larger than the map suggests.

The physics floor. Light in fibre travels at roughly 200,000km per second, so 100km of route contributes about 1ms of round-trip time. Riyadh to Manama is about 410km in a straight line; real fibre routes run 1.3 to 1.5 times great-circle, giving a floor near 6ms. Riyadh to Dubai is about 870km, floor near 12ms.

The measured reality. WonderNetwork probes on 31 July 2026 recorded Riyadh to Manama at 21.16ms, Riyadh to Doha at 55.12ms and Riyadh to Dubai at 101.79ms [S26]. The Dubai figure is roughly eight times the physical floor, and — the detail worth stopping on — it is slower than Riyadh to London (78.18ms) and Riyadh to Frankfurt (80.84ms). That is a routing artefact, not a distance problem: Gulf traffic frequently transits European or Asian interconnection points rather than taking the direct regional path. These are public-internet measurements between probe hosts, not cloud-backbone measurements, and a hyperscaler’s private network will do materially better. But the direction of the error is consistent, and it means “just use the UAE region” is an assumption to test on your own path rather than a safe default.

The cable position is strong and improving. Center3 lands the 2Africa system at Jeddah and Yanbu, with landing stations also at Duba, Haql and Al Khobar; 2Africa spans roughly 45,000km across 46 landing stations in 33 countries, and its Pearls extension reaches Saudi Arabia, Kuwait, Bahrain, Qatar, Iraq, Oman, the UAE, Pakistan and India [S27]. stc’s Saudi Vision cable runs 1,160km up the Red Sea linking Jeddah, Yanbu, Duba and Haql. Mobily lands SEA-ME-WE 6 at a new Yanbu station [S24]. Huawei claims 25ms within Saudi Arabia and around 100ms across the wider region from its Riyadh footprint [S16]. The Kingdom’s connectivity is not the constraint. Its region endpoints are. Broader connectivity context sits with 5G and telecoms and the cloud computing market overview.

Which Saudi Cloud Region Should You Choose?

The honest verdict, by workload.

Mainstream enterprise application needing in-Kingdom residency. Google Dammam or Oracle Riyadh. Those are the only Western-vendor regions that exist. Google gives you three zones and a broader managed-service catalogue but you buy through CNTXT, which changes your contracting counterparty and your support escalation path. Oracle sells directly and its licensing economics are hard to beat for Oracle-estate workloads, but you are accepting a single availability domain and a cross-region DR design.

Government or SAMA-regulated workload. stc’s Oracle Alloy deployment or SCCC, subject to the procurement question below. These are the offerings built for classification-driven residency, with Saudi operational control and local key custody. Google’s Sovereign Controls with CNTXT-operated external key management is the strongest option among the hyperscalers on that axis.

AI training or frontier inference. Nothing in the Kingdom serves this today at commercial scale. Google Dammam has no A2, A3 or A4 machine families. HUMAIN’s capacity is not a purchasable public cloud and its first sites remain unconfirmed as operational. The realistic 2026 answer is a UAE region or an offshore region with a residency review, revisited when Azure Saudi Arabia East and the AWS region land.

Any workload with US defence exposure. Avoid Alibaba, SCCC and Tencent on procurement grounds, and treat the Huawei region as a separate and harder analysis. The 1260H direct-contract bar took effect 30 June 2026 and indirect procurement restrictions follow in 2027.

Anything with a hard 2026 deadline. Design for the regions that exist. Two of the four largest committed Saudi regions — AWS and Azure — are still announcements, and the sector’s own record on announcement-to-availability is not encouraging: Oracle NEOM is 4.7 years and counting.

Why This Matters for Vision 2030

Vision 2030’s digital-economy targets rest on the Kingdom becoming the region’s default cloud destination, and the region table is the cleanest available scoreboard. On raw count Saudi Arabia leads the Gulf: six live regions against the UAE’s four Azure and AWS entries. On usable Western hyperscaler capacity the picture inverts — the UAE has AWS, Azure and Google regions today; Saudi Arabia has Google and Oracle, one of them channel-gated and the other single-AD.

That gap is closing on a known schedule, and it is closing for a physical reason rather than a policy one. Both missing regions are built. Both are waiting on the same grid. The national AI strategy and the wider data center pipeline are downstream of whether energisation arrives on time — which makes the Q4 2026 Azure date the single most testable prediction in Saudi digital infrastructure.

Risks, Contradictions and Open Questions

The AWS region code is unconfirmed. me-central-2 circulates widely and appears in no AWS-published table. AWS has not announced a code, an AZ naming scheme or a launch date beyond “2026.” Anyone building Terraform against me-central-2 today is building against a guess.

A large body of secondary coverage is wrong about AWS, and some of it is compliance guidance. At least one cloud-compliance write-up names “AWS Riyadh” as a region satisfying Saudi residency requirements. That is not a harmless error; it is an architecture decision made on a region that does not exist.

Huawei’s region code could not be pinned to a primary table. Huawei Cloud’s international documentation refers to the region as ME-Riyadh and its own regions-list page returned a 404 to automated retrieval. Zone count and hosting arrangement rest on Huawei’s launch materials and Data Center Dynamics’ reporting.

Oracle’s single-AD position is contested, not settled. Oracle argues three fault domains match three availability zones and cites Gartner. That is a defensible engineering position and it is also the position of the vendor with one availability domain. Customers with a hard multi-AZ requirement in their own controls will not be able to satisfy it in-Kingdom on OCI.

Investment figures are announcements, not audited spend. The $5.3bn, $1.5bn, $2.1bn, $400m and $150m commitments here are what the companies and the ministry said. None is a disclosed capital-expenditure figure, and none has a published drawdown schedule.

Latency figures are indicative. The WonderNetwork measurements are single-probe public-internet samples taken on one day. They establish a direction, not a service level. Oracle publishes measured inter-region round-trip times inside its console but not on the public web, so the Riyadh-to-Dubai backbone figure could not be verified from a provider primary.

SCCC’s expansion plan is unreconciled. Sixteen data centers were announced at launch in June 2022. Two Riyadh sites are documented. Where the other fourteen stand is not publicly stated.

What to Watch Next

• Q4 2026. Microsoft’s stated availability window for Saudi Arabia East. If it slips, the grid explanation moves from likely to confirmed.
• 12 August 2026. Article 26 of the Copyright Law enters force. Implementing regulations were still unwritten at publication.
• Any AWS regions-table change. The AWS documentation region table and the “39 Geographic Regions” headline count are the two surfaces that will move first. A Saudi row appearing there is the launch; a press release is not.
• 2027. The 1260H indirect-procurement restrictions bite, expanding the compliance question for anyone in a US defence supply chain hosting on Alibaba, SCCC or Tencent.
• Oracle NEOM. Its appearance on Oracle’s commercial region list would be the first evidence that the giga-project’s digital layer is being built rather than announced.
• Google GPU families in Dammam. An A3 or A4 machine family appearing in me-central2 would be the first sign that frontier training is commercially available in-Kingdom on a Western hyperscaler.

Change Log

• 31 July 2026 — First publication. All region statuses verified against provider documentation on this date.

Related Vision 2030 Context

• Saudi data center market — the physical capacity build behind the regions
• Saudi Arabia data centers guide — the sector overview and operator map
• Cloud computing in Saudi Arabia — market structure and enterprise adoption
• Saudi Arabia’s AI power constraint — why announced regions arrive late
• HUMAIN data center status tracker — dated verification of the Riyadh and Dammam sites
• How Saudi Arabia regulates AI — PDPL, SDAIA and what actually binds a deployment
• Article 26 of the 2026 Copyright Law — the AI training exception
• NDMO data governance policies — the classification layer that drives residency
• HUMAIN company profile — the PIF-owned sovereign AI operator
• Saudi AI strategy — the policy programme the build-out sits inside

Sources

• [S1] Amazon Web Services, Global Cloud Infrastructure, provider infrastructure page, accessed 31 July 2026. https://aws.amazon.com/about-aws/global-infrastructure/
• [S2] Amazon Web Services, AWS Regions — Available AWS Regions table, product documentation, accessed 31 July 2026. https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html
• [S3] Microsoft, List of Azure Regions, Azure reliability documentation, page updated 28 July 2026, accessed 31 July 2026. https://learn.microsoft.com/en-us/azure/reliability/regions-list
• [S4] Microsoft, Microsoft Confirms Saudi Arabia Datacenter Region Available for Customers to Run Cloud Workloads From Q4 2026, press release, February 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/
• [S5] Google Cloud, Dammam Region Access, product documentation, accessed 31 July 2026. https://docs.cloud.google.com/docs/dammam-region-access
• [S6] Google Cloud, Google Cloud Expands Services in Saudi Arabia, Delivering Enhanced Data Sovereignty and AI Capabilities, company blog, 20 August 2024. https://cloud.google.com/blog/products/identity-security/google-cloud-expands-services-in-saudi-arabia-delivering-enhanced-data-sovereignty-and-ai-capabilities
• [S7] Oracle, Regions and Availability Domains, Oracle Cloud Infrastructure documentation, accessed 31 July 2026. https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm
• [S8] Oracle, New Region in Jeddah, Saudi Arabia, OCI release note, 1 February 2020. https://docs.oracle.com/en-us/iaas/releasenotes/changes/b38848ee-ecd2-4c36-9491-95628f16dffd/index.htm
• [S9] Oracle, New Region in Riyadh, Saudi Arabia, OCI release note, 31 July 2024. https://docs.oracle.com/en-us/iaas/releasenotes/changes/45cb2bf5-290f-40fb-af89-b7b9455f35fe/index.htm — and Oracle Strengthens Saudi Arabia’s AI Economy With Opening of Second Public Cloud Region, press release, 6 August 2024. https://www.prnewswire.com/news-releases/oracle-strengthens-saudi-arabias-ai-economy-with-opening-of-second-public-cloud-region-302215035.html
• [S10] Alibaba Cloud, Regions and Zones (Elastic Compute Service), product documentation, accessed 31 July 2026. https://www.alibabacloud.com/help/en/ecs/regions-and-zones
• [S11] Tencent Cloud, Regions and Availability Zones, product documentation, accessed 31 July 2026. https://www.tencentcloud.com/document/product/213/6091
• [S12] National Cybersecurity Authority (Saudi Arabia), Cloud Cybersecurity Controls, CCC-2:2024, regulatory document register, page noting update of 31 July 2025, accessed 31 July 2026. https://nca.gov.sa/en/regulatory-documents/controls-list/ccc/
• [S13] Morgan Lewis, Saudi Arabia Cloud Compliance Part 1 — Data Residency and Contractual Expectations, Tech & Sourcing blog, 27 March 2026. https://www.morganlewis.com/blogs/sourcingatmorganlewis/2026/03/saudi-arabia-cloud-compliance-part-1-data-residency-and-contractual-expectations
• [S14] Saudi Data and Artificial Intelligence Authority / National Data Management Office, National Data Governance Interim Regulations, policy document. https://sdaia.gov.sa/ndmo/Files/PoliciesEn.pdf — classification-level detail here is drawn from compliance guidance summarising the regulations; the primary PDF was not retrieved in this session.
• [S15] Amazon Web Services, AWS Announces New Edge Location in the Kingdom of Saudi Arabia, What’s New post, 24 January 2025. https://aws.amazon.com/about-aws/whats-new/2025/01/new-edge-location-kingdom-saudi-arabia/
• [S16] Data Center Dynamics, Huawei Launches Saudi Cloud Region in Riyadh, news report, September 2023. https://www.datacenterdynamics.com/en/news/huawei-launches-saudi-cloud-region-in-riyadh/
• [S17] Data Center Dynamics, Tencent Cloud Launches First Middle East Cloud Region in Saudi Arabia, news report, February 2025. https://www.datacenterdynamics.com/en/news/tencent-cloud-launches-first-middle-east-cloud-region-in-saudi-arabia/
• [S18] gcloud-compute.com, Machine Type Availability by Region — me-central2 and us-central1, derived from the Google Cloud Compute Engine API, accessed 31 July 2026. https://gcloud-compute.com/me-central2.html
• [S19] Amazon, AWS and HUMAIN Announce Groundbreaking AI Zone to Accelerate AI Adoption in Saudi Arabia and Globally, press release, 13 May 2025. https://press.aboutamazon.com/2025/5/aws-and-humain-announce-groundbreaking-ai-zone-to-accelerate-ai-adoption-in-saudi-arabia-and-globally
• [S20] Saudi Press Agency, Five-Member Consortium Launches the Services of the Saudi Cloud Computing Company (SCCC), state news agency report, June 2022. https://www.spa.gov.sa/2360096
• [S21] CNBC, China Imposes Trade Curbs on Dozens of US Firms in Retaliation for Pentagon Blacklist, news report, 22 June 2026. https://www.cnbc.com/2026/06/22/china-trade-curbs-us-companies-export-controls-procurement-exclusion-pentagon-list-.html
• [S22] Arnold & Porter, China Imposes Export Control and Government Procurement Restrictions on Designated US Companies, client advisory, July 2026. https://www.arnoldporter.com/en/perspectives/advisories/2026/07/china-imposes-export-control-and-government-procurement-restrictions-on-designated-us-companies
• [S23] Data Center Dynamics, Saudi’s center3 Targets 1GW of Data Center Capacity by 2030, news report, 2025. https://www.datacenterdynamics.com/en/news/saudis-center3-targets-1gw-of-data-center-capacity-by-2030/
• [S24] Data Center Dynamics, Saudi Telco Mobily Invests $905m in Data Centers and Subsea Cables, news report, 2026. https://www.datacenterdynamics.com/en/news/saudi-telco-mobily-invests-905m-in-data-centers-and-subsea-cables/
• [S25] SAP, Saudi Arabia Becomes First in the World to Host SAP Business Network for Public Sector With Full Data Sovereignty Compliance, press release, October 2025. https://news.sap.com/mena/2025/10/saudi-first-in-world-to-host-sap-business-network-for-public-sector-with-full-data-sovereignty-compliance/
• [S26] WonderNetwork, Ping Times From Riyadh, network measurement data, sampled 31 July 2026. https://wondernetwork.com/pings/Riyadh
• [S27] Submarine Networks, center3 Lands 2Africa Cable in Jeddah and Yanbu, Saudi Arabia, industry report. https://www.submarinenetworks.com/en/systems/asia-europe-africa/2africa/center3-lands-2africa-cable-in-jeddah-and-yanbu