diff --git a/macros/compute/instances-block-bandwidth-overview.mdx b/macros/compute/instances-block-bandwidth-overview.mdx
index 80d3137623..859bc0171a 100644
--- a/macros/compute/instances-block-bandwidth-overview.mdx
+++ b/macros/compute/instances-block-bandwidth-overview.mdx
@@ -19,6 +19,30 @@ Bandwidth impacts how your applications perform and interact with other systems.
To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
+## BASIC-A range
+| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) |
+|-----------------------|-------------------------|---------------------|
+| BASIC-A2C-4G | 200 Mbit/s | 80 MiB/s |
+| BASIC-A2C-8G | 200 Mbit/s | 80 MiB/s |
+| BASIC-A4C-8G | 400 Mbit/s | 120 MiB/s |
+| BASIC-A4C-16G | 400 Mbit/s | 120 MiB/s |
+| BASIC-A8C-16G | 800 Mbit/s | 240 MiB/s |
+| BASIC-A8C-32G | 800 Mbit/s | 240 MiB/s |
+| BASIC-A16C-32G | 1.6 Gbit/s | 480 MiB/s |
+| BASIC-A16C-64G | 1.6 Gbit/s | 480 MiB/s |
+
+
+## STANDARD2 range
+| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) |
+|-----------------------|-------------------------|---------------------|
+| STANDARD-A2C-8G | 400 Mbit/s | 400 MiB/s |
+| STANDARD-A4C-16G | 800 Mbit/s | 800 MiB/s |
+| STANDARD-A8C-32G | 1.6 Gbit/s | 1.6 GiB/s |
+| STANDARD-A16C-64G | 3.2 Gbit/s | 3.2 GiB/s |
+| STANDARD2-A32C-128G | 6.4 Gbit/s | 4.8 GiB/s |
+| STANDARD2-A48C-192G | 9.6 Gbit/s | 4.8 GiB/s |
+| STANDARD2-A64C-256G | 12.8 Gbit/s | 4.8 GiB/s |
+
## COPARM1 range
| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) |
diff --git a/pages/instances/reference-content/instances-datasheet.mdx b/pages/instances/reference-content/instances-datasheet.mdx
index 02b59775f4..a228ce00e5 100644
--- a/pages/instances/reference-content/instances-datasheet.mdx
+++ b/pages/instances/reference-content/instances-datasheet.mdx
@@ -13,7 +13,70 @@ This datasheet provides a concise overview of the performance, technical feature
Note that the **Max. NIC bandwidth** specifies the maximum available bandwidth for this Instance type. Bandwidth is shared between public internet and Private Network traffic.
-## STARDUST1 Instances
+## General Purpose ARM Instances
+
+### BASIC-A Instances
+
+| Range | General Purpose ARM Instances |
+|:------------------------------|:------------------------------------------------------------------------------|
+| Instance type | BASIC-A |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW1, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 200 Mbps to 1.6 Gbps |
+| CPU type | ARM (Ampere Altra Max M128-30) |
+| CPU architecture | `arm64` |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 16 vCPUs
From 4 to 64 GiB RAM |
+| vCPU:RAM ratio | 1:2 or 1:4 |
+| SLO | 99% availability |
+
+### STANDARD2-A Instances
+
+| Range | General Purpose ARM Instances |
+|:------------------------------|:------------------------------------------------------------------------------|
+| Instance type | STANDARD2-A |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW1, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 400 Mbps to 12.8 Gbps |
+| CPU type | ARM (Ampere Altra Max M128-30) |
+| CPU architecture | `arm64` |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 64 vCPUs
From 8 to 256 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+| SLO | 99.5% availability |
+
+### COP-ARM Instances (Legacy)
+
+The table below displays the technical specifications of COP-ARM Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | COPARM1 |
+| Availability Zone | PAR2 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 200 Mbps to 3.2 Gbps |
+| CPU type | ARM (Ampere Altra Max M128-30) |
+| CPU architecture | `arm64` |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 64 vCPUs
From 8 to 256 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+| SLO | None |
+
+### Legacy ARM and new Instance types mapping
+
+The COPARM1 instances are being replaced by the new General Purpose and Standard instance types. Below is the mapping of COPARM1 instances to their replacements:
+
+| COPARM1 Instance Type | New Instance Type |
+|----------------------|-------------------|
+| COPARM1-2C-8G | BASIC-A2C-8G |
+| COPARM1-4C-16G | BASIC-A4C-16G |
+| COPARM1-8C-32G | BASIC-A8C-32G |
+| COPARM1-16C-64G | BASIC-A16C-64G |
+| COPARM1-32C-128G | STANDARD2-A32C-128G |
+
+## x86 Instances
+
+### STARDUST1 Instances
See below the technical specifications of Stardust Instances:
@@ -28,9 +91,9 @@ This datasheet provides a concise overview of the performance, technical feature
| Resources | Shared vCPUs |
| Sizing | 1 vCPU, 1 GiB RAM |
| vCPU:RAM ratio | 1:1 |
-| SLA | None |
+| SLO | None |
-## Development and General Purpose Instances
+### Development and General Purpose Instances
See below the technical specifications of Development and General Purpose Instances:
@@ -45,8 +108,9 @@ See below the technical specifications of Development and General Purpose Instan
| Resources | Shared vCPUs |
| Sizing | From 2 to 4 vCPUs
From 2 to 12 GiB RAM |
| vCPU:RAM ratio | Various
(1:1, 1:2, 1:3) |
+| SLO | None |
-## PLAY2 and PRO2 Instances
+### PLAY2 and PRO2 Instances
See below the technical specifications of PLAY2 and PRO2 Instances:
@@ -61,24 +125,10 @@ See below the technical specifications of PLAY2 and PRO2 Instances:
| Resources | Shared vCPUs |
| Sizing | From 1 to 32 vCPUs
From 2 to 128 GiB RAM |
| vCPU:RAM ratio | Various
(1:2, 1:4) |
+| SLO | None |
-## COP-ARM Instances
-
-The table below displays the technical specifications of COP-ARM Instances:
-
-| Range | Cost-Optimized |
-|:--------------------------------|:------------------------------------------------------------------------------|
-| Instance type | COPARM1 |
-| Availability Zone | PAR2 |
-| Storage | Block (from 10 GB to 10 TB) |
-| Max. NIC bandwidth | From 200 Mbps to 3.2 Gbps |
-| CPU type | ARM (Ampere Altra Max M128-30) |
-| CPU architecture | `arm64` |
-| Resources | Shared vCPUs |
-| Sizing | From 2 to 128 vCPUs
From 8 to 128 GiB RAM |
-| vCPU:RAM ratio | 1:4 |
-## Enterprise Instances
+### Enterprise Instances
See below the technical specifications of Enterprise Instances:
@@ -94,10 +144,11 @@ See below the technical specifications of Enterprise Instances:
| Security feature | Secure Encrypted Virtualization |
| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
| vCPU:RAM ratio | 1:4 |
+| SLO | None |
\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
-## Production-Optimized Instances
+### Production-Optimized Instances
See below the technical specifications of Production-Optimized Instances:
@@ -112,10 +163,11 @@ See below the technical specifications of Production-Optimized Instances:
| Resources | Dedicated vCPUs* |
| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
| vCPU:RAM ratio | 1:4 |
+| SLO. | 99.5% availability |
\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
-## Workload-Optimized Instances
+### Workload-Optimized Instances
See below the technical specifications of Workload-Optimized Instances:
@@ -134,5 +186,6 @@ See below the technical specifications of Workload-Optimized Instances:
| Security feature | Secure Encrypted Virtualization |
| Sizing | From 2 to 64 dedicated vCPUs
From 4 GiB to 512 GiB RAM |
| vCPU:RAM ratio | 1:8 (POP2-HM), 1:2 (POP2-HC and POP2-HN) |
+| SLO | 99.5% availability |
\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
\ No newline at end of file