Regional Enterprise Agreement 2023-Johannesburg
| Service Name | SKU Name | SKU ID | Date Added |
|---|---|---|---|
| AlloyDB (C49F-B7F2-7416) | AlloyDB Backup Storage in Johannesburg | 7C0B-05E7-954C | May 31, 2024 |
| AlloyDB (C49F-B7F2-7416) | AlloyDB Cluster Database Storage in Johannesburg | 51D7-B58F-6C4D | May 31, 2024 |
| AlloyDB (C49F-B7F2-7416) | AlloyDB Instance RAM Usage in Johannesburg | B624-335E-9940 | May 31, 2024 |
| AlloyDB (C49F-B7F2-7416) | AlloyDB Instance vCPU Cores in Johannesburg | EFF9-A759-CF55 | May 31, 2024 |
| AlloyDB (C49F-B7F2-7416) | AlloyDB backup storage for point-in-time recovery logs in Johannesburg | E83B-7D20-B83D | May 31, 2024 |
| AlloyDB (C49F-B7F2-7416) | AlloyDB: Network Data Transfer Out Internet Premium within Africa | FF65-985D-237E | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Backup Restore Operation (named databases) Johannesburg | 6783-BCC4-C979 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Backup Restore Operation Johannesburg | 64C6-E2D5-4C60 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Entity Deletes (named databases) Johannesburg | DB0B-BDCD-E360 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Entity Deletes Johannesburg | 3302-8F3C-8DED | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Entity Writes (named databases) Johannesburg | D21A-CAF4-29FA | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Entity Writes Johannesburg | 1593-4F6D-4D34 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Point-in-time Recovery Storage (named databases) Johannesburg | 4AFC-0277-CCEC | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Point-in-time Recovery Storage Johannesburg | E8C4-366A-3053 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Read Ops (named databases) Johannesburg | 3A80-977A-E0F5 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Read Ops Johannesburg | C21D-66C3-A920 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Small Ops (named databases) Johannesburg | 6C31-3098-7237 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Small Ops Johannesburg | EFBB-415C-1C42 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Storage (named databases) Johannesburg | 784D-8D8F-A04E | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Storage Johannesburg | BDE6-81DE-92B3 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore TTL Deletes (named databases) Johannesburg | 3391-05CF-387C | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore TTL Deletes Johannesburg | 3FB8-AFBC-1FBF | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Zonal Backup Storage (named databases) Johannesburg | B0C4-AFF4-8516 | February 29, 2024 |
| App Engine (F17B-412E-CB64) | Cloud Firestore Zonal Backup Storage Johannesburg | ABFD-AEAE-4822 | February 29, 2024 |
| Artifact Registry (149C-F9EC-3994) | Artifact Registry Network Internet Egress Africa to Africa | D8E6-9C93-C7CA | February 29, 2024 |
| Backup for GKE (7929-AEC3-626F) | Backup for GKE management in Johannesburg | 648C-89AF-757A | February 29, 2024 |
| Backup for GKE (7929-AEC3-626F) | Standard storage consumed by backups in Johannesburg | 3CCF-0CA7-31D1 | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Active Logical Storage (africa-south1) | 0752-7FDA-AF5E | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Active Physical Storage (africa-south1) | 2555-691F-7B5D | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Analysis (africa-south1) | BAD2-039A-A5F9 | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Long Term Logical Storage (africa-south1) | E0F2-DB41-FC31 | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Long-Term Physical Storage (africa-south1) | 8F0B-76E7-1716 | February 29, 2024 |
| BigQuery (24E6-581D-38E5) | Notebook Persistent Disk Storage (africa-south1) | ABB3-F005-EF9D | March 27, 2024 |
| BigQuery (24E6-581D-38E5) | Notebook SSD Storage (africa-south1) | 5AE6-54DB-8837 | March 27, 2024 |
| BigQuery (24E6-581D-38E5) | Streaming Insert (africa-south1) | 8AC8-77B9-1C5F | February 29, 2024 |
| BigQuery BI Engine (650B-3C82-34DB) | BigQuery BI Engine Flat Rate for Johannesburg | 84F8-F921-0C9F | February 29, 2024 |
| BigQuery BI Engine (650B-3C82-34DB) | BigQuery BI Engine for Johannesburg | 049E-C562-6DD2 | February 29, 2024 |
| BigQuery Engine for Apache Flink (EC2C-A2D9-6ADE) | Slots in africa-south1 | 3FBB-7588-D17F | September 17, 2024 |
| BigQuery Engine for Apache Flink (EC2C-A2D9-6ADE) | State Storage in africa-south1 | 3767-308F-6429 | September 17, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Edition 1 Year for Johannesburg (africa-south1) | A100-194B-0F47 | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Edition 3 Years for Johannesburg (africa-south1) | 4F69-1B38-7913 | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Edition for Johannesburg (africa-south1) | AEF0-F928-571B | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Plus Edition 1 Year for Johannesburg (africa-south1) | 9786-D1FF-71FE | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Plus Edition 3 Years for Johannesburg (africa-south1) | 14A9-9063-239B | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Enterprise Plus Edition for Johannesburg (africa-south1) | A8BB-7332-3A45 | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Flat Rate Annual for Johannesburg (africa-south1) | C6EB-BA71-EEC1 | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Flat Rate Flex for Johannesburg (africa-south1) | 3195-9BFD-58D8 | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Flat Rate Monthly for Johannesburg (africa-south1) | B805-2164-D74B | February 29, 2024 |
| BigQuery Reservation API (16B8-3DDA-9F10) | BigQuery Standard Edition for Johannesburg (africa-south1) | CEF1-C508-EA3C | February 29, 2024 |
| BigQuery Storage API (DCC9-8DB9-673F) | BigQuery Storage API - Read Bytes Scanned (africa-south1) | A8CE-1C7D-4389 | February 29, 2024 |
| BigQuery Storage API (DCC9-8DB9-673F) | BigQuery Storage API - Write (africa-south1) | DFC1-1118-F402 | February 29, 2024 |
| BigQuery Storage API (DCC9-8DB9-673F) | BigQuery Storage API Network Internet Data Transfer Out Africa to Africa | 0D19-3979-6F21 | February 29, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | Backup storage in africa-south1 region | 9D32-DC75-70AC | February 29, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | Data Boost usage in africa-south1 region | BA8C-638D-C221 | February 29, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | HDD storage in africa-south1 region | 8935-91F1-0191 | February 29, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | Hot backup storage in africa-south1 region | 8225-7CF8-E9D5 | September 21, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | SSD storage in africa-south1 region | B48F-08E0-15C5 | February 29, 2024 |
| Cloud Bigtable (C3BE-24A5-0975) | Server Node in africa-south1 region | CA87-E807-0139 | February 29, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer 3 database storage (africa-south1) | A37C-C1AB-6E69 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer 3 standard milli DCU-hours (africa-south1) | D3FA-5A89-52C0 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer Compute Memory (africa-south1) | 498A-71C2-8D9B | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer Compute Storage (africa-south1) | 8049-63E7-CDD7 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer Compute mCPUs (africa-south1) | D98F-1EB5-6AEA | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer Database Storage (africa-south1). | 3262-80F3-895B | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Cloud Composer: Network Data Transfer Out Internet Premium within Africa | 2CFC-D365-1C8C | March 27, 2024 |
| Cloud Composer (1992-3666-B975) | Large Cloud Composer Environment Fee (africa-south1). | 4FE7-0293-FC1B | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Large Highly Resilient Cloud Composer Environment Fee (africa-south1) | 3822-5CAB-F994 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Medium Cloud Composer Environment Fee (africa-south1). | 0A06-D819-0A95 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Medium Highly Resilient Cloud Composer Environment Fee (africa-south1) | 6932-0827-6D53 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Small Cloud Composer Environment Fee (africa-south1). | 879C-3B6A-7A13 | May 17, 2024 |
| Cloud Composer (1992-3666-B975) | Small Highly Resilient Cloud Composer Environment Fee (africa-south1) | 9229-EE38-0024 | May 17, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Confidential RAM Time Johannesburg | 7B98-A96C-8363 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Confidential RAM Time Streaming Johannesburg | 03AF-9DFC-4C79 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Confidential vCPU Time Johannesburg | D12A-84EF-F8A4 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Dataflow Compute Units Batch Johannesburg | 9E35-EE77-8D41 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Dataflow Compute Units Streaming Johannesburg | A27C-B649-E8B1 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Dataprep Unit for Johannesburg | 96E5-D2F0-366D | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time A100 80GB Johannesburg | D3FF-8D2A-6B77 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time A100 Johannesburg | 5C97-BB0C-AE8A | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time L4 Johannesburg | 5A95-1DA1-B093 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time P100 Johannesburg | 99FF-D60B-6C60 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time P4 Johannesburg | FB4C-D636-1FC9 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time T4 Johannesburg | 1E31-AE77-5D3D | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | GPU Time V100 Johannesburg | E43F-0CD6-0B9F | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Local Disk Time PD SSD Johannesburg | 94A0-9819-DB5A | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Local Disk Time PD Standard Johannesburg | D0F4-18D3-AA07 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | RAM Time FlexRS Johannesburg | 3D82-FED7-320C | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | RAM Time Johannesburg | 8742-A1B0-835D | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | RAM Time Streaming Johannesburg | 46EA-E808-7965 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Shuffle chargeable data processed for Johannesburg | 2CB7-D489-0CD4 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Snapshot Disk Time Johannesburg | 2BE5-51E0-0B51 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Streaming Engine Compute Unit Johannesburg | E792-8576-D004 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | Streaming data processed for Johannesburg | 2575-2926-9DFA | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | vCPU Time Batch Johannesburg | 8644-A9A3-44DE | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | vCPU Time FlexRS Batch Johannesburg | 029D-2D21-3B85 | February 29, 2024 |
| Cloud Dataflow (57D6-8E6B-2DE0) | vCPU Time Streaming Johannesburg | 49A7-4D2C-E057 | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Cloud Filestore Network Internet Egress Africa to Africa | CBB7-ACBD-DC96 | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Filestore Backup Usage africa-south1 | B999-2B74-4D1C | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Filestore Capacity Basic HDD (Standard) Johannesburg | BD98-0C8E-B52B | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Filestore Capacity Basic SSD (Premium) Johannesburg | 6935-94EE-C26B | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Filestore Capacity Regional and Enterprise Johannesburg | 66F2-4E9E-0C9A | February 29, 2024 |
| Cloud Filestore (D97E-AB26-5D95) | Filestore Capacity Zonal and High Scale Johannesburg | FDAD-145C-AC96 | February 29, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Backup Restore Operation (with free tier) Johannesburg | 10A7-9D70-35BA | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Backup Restore Operation Johannesburg | 1E90-8551-0A06 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Entity Deletes (with free tier) Johannesburg | 6E97-9DB3-97EC | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Entity Deletes Johannesburg | 8C06-7274-6572 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Entity Writes (with free tier) Johannesburg | 9654-18C8-3350 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Entity Writes Johannesburg | B031-C246-F299 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Point-in-time Recovery Storage (with free tier) Johannesburg | B766-444C-0271 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Point-in-time Recovery Storage Johannesburg | 2E1D-BF7E-F579 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Read Ops (with free tier) Johannesburg | F7AB-1CEA-D9C3 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Read Ops Johannesburg | 6D34-6ACC-76C2 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Small Ops (with free tier) Johannesburg | A01D-C38F-FD6C | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Small Ops Johannesburg | D685-EC69-6227 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Storage (with free tier) Johannesburg | 24E4-2964-E814 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Storage Johannesburg | 2521-063A-15A9 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore TTL Deletes (with free tier) Johannesburg | 10AE-E69E-1005 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore TTL Deletes Johannesburg | 8EB7-573A-8380 | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Zonal Backup Storage (with free tier) Johannesburg | 43DA-C967-9A7B | October 15, 2024 |
| Cloud Firestore (EE2C-7FAC-5E08) | Cloud Firestore Zonal Backup Storage Johannesburg | C805-65F4-1A58 | October 15, 2024 |
| Cloud Memorystore (A2B5-E0F1-B0F3) | Highmem Medium Node Johannesburg | 8BB6-D609-BA6D | July 18, 2024 |
| Cloud Memorystore (A2B5-E0F1-B0F3) | Highmem XLarge Node Johannesburg | D429-86F7-BFF1 | July 18, 2024 |
| Cloud Memorystore (A2B5-E0F1-B0F3) | Memorystore for Valkey: AOF Storage Johannesburg | BF67-BB6A-3095 | August 21, 2024 |
| Cloud Memorystore (A2B5-E0F1-B0F3) | Shared Core Nano Node Johannesburg | 88E7-EFD5-CA6C | July 18, 2024 |
| Cloud Memorystore (A2B5-E0F1-B0F3) | Standard Small Node Johannesburg | 2046-09F0-73DC | July 18, 2024 |
| Cloud Memorystore for Memcached (9C2E-5AAC-D058) | Custom Core M1 Johannesburg | F4AD-33D0-04AE | February 29, 2024 |
| Cloud Memorystore for Memcached (9C2E-5AAC-D058) | Custom Core M2 Johannesburg | 6DE0-E547-AC6E | February 29, 2024 |
| Cloud Memorystore for Memcached (9C2E-5AAC-D058) | Custom RAM M1 Johannesburg | BB5C-52F3-F674 | February 29, 2024 |
| Cloud Memorystore for Memcached (9C2E-5AAC-D058) | Custom RAM M2 Johannesburg | 3DA5-F439-BEF6 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Memorystore for Redis Cluster: AOF Storage in Johannesburg | 5A1B-5522-FF55 | October 6, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Basic M1 Johannesburg | 665E-6195-8C68 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Basic M2 Johannesburg | 66A5-E886-BB8A | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Basic M3 Johannesburg | 3A84-67E3-2839 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Basic M4 Johannesburg | 0089-72AB-28A2 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Basic M5 Johannesburg | 6D0A-5B5F-A725 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Standard M1 Johannesburg | 87A7-841A-B127 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Standard M2 Johannesburg | 93A2-4C43-7A74 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Standard M3 Johannesburg | 9B5D-FB75-6A1C | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Standard M4 Johannesburg | 3588-BE8A-6A12 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Capacity Standard M5 Johannesburg | B147-B3A7-D5F6 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Cluster Node Highmem XLarge Johannesburg | 8388-3CD5-9729 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Cluster Node Shared Core Nano Johannesburg | 5FA2-733F-3E73 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Cluster Node Standard Small Johannesburg | 6723-6E3A-3C82 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Standard Node Capacity M2 Johannesburg | 39AD-3B7D-2C7C | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Standard Node Capacity M3 Johannesburg | 3B46-2D9E-374C | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Standard Node Capacity M4 Johannesburg | FCA8-5187-7643 | February 29, 2024 |
| Cloud Memorystore for Redis (5AF5-2C11-D467) | Redis Standard Node Capacity M5 Johannesburg | B867-FEE6-DBAB | February 29, 2024 |
| Cloud Run (152E-C115-5142) | CPU Allocation Time (Always-on CPU) in africa-south1 | 9829-409C-F303 | February 29, 2024 |
| Cloud Run (152E-C115-5142) | CPU Allocation Time (Jobs) in africa-south1 | F35A-5D39-DA9D | February 29, 2024 |
| Cloud Run (152E-C115-5142) | Cloud Run Network Internet Data Transfer Out Africa to Africa | 9E93-0D03-D5F8 | February 29, 2024 |
| Cloud Run (152E-C115-5142) | Memory Allocation Time (Always-on CPU) in africa-south1 | 7031-EC84-8991 | February 29, 2024 |
| Cloud Run (152E-C115-5142) | Memory Allocation Time (Jobs) in africa-south1 | 15ED-CA0B-6573 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - Low cost storage in Johannesburg | F394-6415-1A72 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - RAM in Johannesburg | 6072-4198-2E77 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - Serverless Exports in Johannesburg | 62D4-00F9-AD82 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - Standard storage in Johannesburg | B2D3-EB3D-57F1 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - vCPU + RAM in Johannesburg | 3BE1-E485-D158 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Read Replica (free with promotional discount until September 2021) - vCPU in Johannesburg | 82FA-E127-3FEE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 1 vCPU + 3.75GB RAM in Johannesburg | 9BF8-BE7B-5363 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 16 vCPU + 104GB RAM in Johannesburg | E7EF-E00C-E904 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 16 vCPU + 60GB RAM in Johannesburg | 427A-6C00-F305 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 2 vCPU + 13GB RAM in Johannesburg | 3BDC-8885-61DC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 2 vCPU + 7.5GB RAM in Johannesburg | F89F-FE2C-AED9 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 32 vCPU + 120GB RAM in Johannesburg | 21D4-6FB2-250E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 32 vCPU + 208GB RAM in Johannesburg | 7969-956C-268C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 4 vCPU + 15GB RAM in Johannesburg | 2589-2629-5148 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 4 vCPU + 26GB RAM in Johannesburg | 74EE-B771-FEAF | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 64 vCPU + 240GB RAM in Johannesburg | 2752-1422-54DF | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 64 vCPU + 416GB RAM in Johannesburg | 8B9D-D912-158C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 8 vCPU + 30GB RAM in Johannesburg | 6488-5E3C-7988 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 8 vCPU + 52GB RAM in Johannesburg | 5532-D907-30DF | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 96 vCPU + 360GB RAM in Johannesburg | BC8B-7BAB-AABF | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - 96 vCPU + 624GB RAM in Johannesburg | 7E0F-51BF-E6BE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Enterprise Plus N RAM in Johannesburg | 8D85-7479-3C81 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Enterprise Plus N vCPU in Johannesburg | 6B48-9829-7D8F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Enterprise Plus Standard Storage in Johannesburg | BB34-61DF-BB89 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - IP address reservation in Johannesburg | BDB7-ED92-047E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Low cost storage in Johannesburg | 45FA-58F8-DAFB | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Micro instance in Johannesburg | E5DB-80FD-1EDA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - RAM in Johannesburg | 21A0-800D-93C9 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Serverless Exports in Johannesburg | 5EC7-9E20-6E72 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Small instance in Johannesburg | 6777-FA0A-99E8 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - Standard storage in Johannesburg | BA95-AF87-701C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Regional - vCPU in Johannesburg | F084-EF5C-5C21 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 1 vCPU + 3.75GB RAM in Johannesburg | 27C6-5D39-789C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 16 vCPU + 104GB RAM in Johannesburg | 7CCF-7577-E0EA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 16 vCPU + 60GB RAM in Johannesburg | B19C-C437-8D94 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 2 vCPU + 13GB RAM in Johannesburg | EF6F-9D2A-149F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 2 vCPU + 7.5GB RAM in Johannesburg | 9436-7317-AD8A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 32 vCPU + 120GB RAM in Johannesburg | 25D3-3777-A8E8 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 32 vCPU + 208GB RAM in Johannesburg | C55E-D8BE-75E6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 4 vCPU + 15GB RAM in Johannesburg | 172E-1A5E-437A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 4 vCPU + 26GB RAM in Johannesburg | EBD7-587E-6369 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 64 vCPU + 240GB RAM in Johannesburg | BC6D-29B6-71AE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 64 vCPU + 416GB RAM in Johannesburg | 1FC9-D75B-D079 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 8 vCPU + 30GB RAM in Johannesburg | 08E4-82B2-A3DD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 8 vCPU + 52GB RAM in Johannesburg | D0EE-D7BA-A7B3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 96 vCPU + 360GB RAM in Johannesburg | 53D2-1DAC-6703 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - 96 vCPU + 624GB RAM in Johannesburg | 9628-DF6B-4EBD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Enterprise Plus Data Cache Storage in Johannesburg | 7A90-103B-AB14 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Enterprise Plus N RAM in Johannesburg | ACB4-DD85-66FD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Enterprise Plus N vCPU in Johannesburg | AC5B-C6F3-A9C9 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Enterprise Plus Standard Storage in Johannesburg | 8212-2F08-2734 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - IP address reservation in Johannesburg | 0BCD-5CDB-D1E9 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Low cost storage in Johannesburg | 20C0-DA87-5FFC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Micro instance in Johannesburg | D77E-D627-346F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - RAM in Johannesburg | 489A-57A2-CCD8 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Serverless Exports in Johannesburg | B794-DE16-D787 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Small instance in Johannesburg | 0518-D601-F8EB | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - Standard storage in Johannesburg | AE00-DAF2-41DB | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for MySQL: Zonal - vCPU in Johannesburg | A2D6-8889-1E43 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Enterprise Plus Data Cache Storage in Johannesburg | 352C-8C1B-0623 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Enterprise Plus N RAM in Johannesburg | 7A2B-5237-0AE7 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Enterprise Plus N vCPU in Johannesburg | 9AE1-1717-EE4A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Enterprise Plus Standard Storage in Johannesburg | EB68-A4B4-932A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - IP address reservation in Johannesburg | EEEF-D1F8-5F7D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Low cost storage in Johannesburg | 8789-605D-93E4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Micro instance in Johannesburg | 7C6D-D26D-9279 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - RAM in Johannesburg | FF7B-9A16-3BDC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Serverless Exports in Johannesburg | C8C2-DE09-3B64 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Small instance in Johannesburg | 2B37-01EA-04CA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - Standard storage in Johannesburg | 21EB-A0BB-84B0 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Regional - vCPU in Johannesburg | 231D-8BBD-784F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Enterprise Plus Data Cache Storage in Johannesburg | 91FB-509C-D8AA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Enterprise Plus N RAM in Johannesburg | 7442-60A1-D24C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Enterprise Plus N vCPU in Johannesburg | 9F64-6C7A-7834 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Enterprise Plus Standard Storage in Johannesburg | C05B-9BE3-3886 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - IP address reservation in Johannesburg | 85A3-345C-2461 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Low cost storage in Johannesburg | 187F-AC36-CE79 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Micro instance in Johannesburg | A76C-7042-A1CE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - RAM in Johannesburg | E05E-67D4-D127 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Serverless Exports in Johannesburg | 4B43-42D2-1EF4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Small instance in Johannesburg | 858C-0D28-2F3B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - Standard storage in Johannesburg | AC5B-0D94-6BD4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for PostgreSQL: Zonal - vCPU in Johannesburg | F237-8221-C04C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus Data Cache Storage in Johannesburg | 5680-75E7-B957 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus MoN RAM in Johannesburg | 7953-017B-78BD | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus MoN vCPU in Johannesburg | 3091-8103-AB9C | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus N RAM in Johannesburg | AE45-3A71-6572 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus N vCPU in Johannesburg | 155E-54ED-5439 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Enterprise Plus Standard Storage in Johannesburg | 383A-C602-B800 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - IP address reservation in Johannesburg | 1671-4E77-3E43 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - RAM in Johannesburg | 3AAE-4351-24C5 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - Standard storage in Johannesburg | 813F-2736-B3CA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Regional - vCPU in Johannesburg | 2A07-4439-49EE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus Data Cache Storage in Johannesburg | 7484-5509-C5F9 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus MoN RAM in Johannesburg | 01E5-5B7E-0FF9 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus MoN vCPU in Johannesburg | 186F-41D1-A26D | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus N RAM in Johannesburg | 108B-364E-D165 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus N vCPU in Johannesburg | A309-E664-C7B9 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Enterprise Plus Standard Storage in Johannesburg | 9C42-D0B3-69F3 | July 12, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - IP address reservation in Johannesburg | 660F-CBEC-85B3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - RAM in Johannesburg | ED43-793B-8394 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - Standard storage in Johannesburg | 6662-7F08-D8A6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL for SQL Server: Zonal - vCPU in Johannesburg | E2A6-1C90-D8E2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Cloud SQL: Backups in Johannesburg | 29AB-E369-2E26 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - IP address reservation in Johannesburg | C71B-18FF-5908 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - Low cost storage in Johannesburg | C28C-8713-ECA7 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - Micro instance in Johannesburg | 538E-DF18-37FD | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - RAM in Johannesburg | DC27-817B-726D | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - Serverless Exports in Johannesburg | B44A-954F-1B0C | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - Small instance in Johannesburg | CFDB-E55F-CE14 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - Standard storage in Johannesburg | 8B22-ED49-08EC | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Regional - vCPU in Johannesburg | 8437-F161-DBFB | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - IP address reservation in Johannesburg | 3D56-AD28-60F1 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - Low cost storage in Johannesburg | 6385-B21C-43ED | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - Micro instance in Johannesburg | 0F6A-9D95-31F6 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - RAM in Johannesburg | 3521-15C0-D5EF | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - Serverless Exports in Johannesburg | EA87-6F71-C0EF | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - Small instance in Johannesburg | B744-4AC5-13EC | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - Standard storage in Johannesburg | 17D9-4E97-11A7 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | FDC Trial in Cloud SQL for PostgreSQL: Zonal - vCPU in Johannesburg | AB5D-CE9F-6B71 | May 1, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to APAC | 3AAB-6714-A668 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Africa | 1E81-3551-2689 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Americas | B2A2-0821-04FA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Australia | 1667-6831-1331 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Berlin | 48F9-69AD-0F50 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Central America | DAE1-74C0-D4D3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to China | A705-369C-9F72 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Columbus | 21FA-87EA-8BB1 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Dallas | A2D9-2866-1A5C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Dammam | BC60-1111-FFF3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Day0 (Alabama) | 9A7F-3E0B-2AF3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Delhi | AEF1-7150-AD54 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Doha | AE93-FDA2-FC38 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to EMEA | EB2D-9186-2ADD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Eastern Europe | 8146-FA58-B8C3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Finland | 7D15-8E8A-3B3C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Frankfurt | 1B91-7F6B-753C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Hong Kong | 9688-1AA0-5208 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to India | 08A9-BF53-608E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Israel | 1064-07E6-9F05 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Jakarta | 4B8C-EF98-E09F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Japan | E2DE-E591-8FF6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Johannesburg | C33C-D5C4-D1D5 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Las Vegas | 4852-F6D2-8465 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to London | 7260-A2F5-A4F4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Los Angeles | 0B0D-ECF2-DAFD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Madrid | BBB1-DD24-A565 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Melbourne | 9B26-6294-7BF1 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Middle East | 2FB9-7639-A8B4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Milan | 4B20-9E8F-BB49 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Montreal | 9DB0-1043-D131 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Mumbai | 883A-55D7-36A0 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Netherlands | E532-5919-0367 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Northern Virginia | F2C5-B1A6-B6A3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Osaka | F831-2E18-D06D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Paris | 162F-62CB-9268 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Phoenix | 620C-3BBD-7556 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Salt Lake City | 3578-1DA7-806F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Santiago | 7007-5CB1-87D6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Sao Paulo | 6726-BDC5-D77C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Seoul | C6C6-34A4-B820 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Singapore | 1B6D-7943-38BF | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to South America | 6456-D65F-2F98 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Sydney | 5968-70EA-842D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Toronto | D1A8-4761-5256 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Turin | A309-039D-F290 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Warsaw | A867-C527-B2F8 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Western Europe | D7CD-7814-4425 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Data Transfer to Google Services from Johannesburg to Zurich | FD18-5F98-05C0 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Google Egress from Johannesburg to Mexico | 591C-0A3F-E0D9 | September 7, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Google Egress from Johannesburg to Stockholm | 2555-1784-5D02 | May 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Connect Data Transfer Out Johannesburg | 700E-52F5-4E2B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to APAC | 3EB3-4C35-601F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Africa | CB35-E8F9-D287 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Americas | DCD1-D444-EDA2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Australia | 83CD-4350-A09D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Berlin | 1295-86F4-12B1 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Central America | 1624-8265-2323 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to China | CA4B-541A-2EDD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Columbus | 84DF-5176-1C5E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Dallas | 89A9-EE1C-80F6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Dammam | 3F19-877E-B9CC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Day0 (Alabama) | 1C29-E1AA-0824 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Delhi | 1DE8-82B9-00EC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Doha | D5F0-DAD5-0307 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to EMEA | 0238-21E9-5514 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Eastern Europe | 1FFD-1C9C-6242 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Finland | 25C3-BF78-45F3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Frankfurt | 9CFE-4768-0B8B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Hong Kong | 5650-0166-421D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to India | 0BAD-8260-2379 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Israel | 41F5-E268-2F73 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Jakarta | BD3F-06EE-6DD6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Japan | 1788-3D14-874D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Johannesburg | C156-C759-65F7 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Las Vegas | B7E3-3295-CD39 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to London | BAB7-FEC4-0F8B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Los Angeles | E1DD-DC05-B5E0 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Madrid | 28D4-D33C-512B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Melbourne | E12D-FFC4-9142 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Middle East | BB20-6122-6B82 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Milan | E1DC-9B88-1223 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Montreal | 2FD0-4C60-A507 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Mumbai | 0B70-94C0-3920 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Netherlands | AABD-562B-3502 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Northern Virginia | 2E16-C62A-7AC8 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Osaka | 4760-4F7B-82AB | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Paris | 3C9B-46F8-23C2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Phoenix | 9797-349F-90E9 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Salt Lake City | 0A28-07A0-E53A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Santiago | 6419-611F-C93B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Sao Paulo | 1E0B-3B63-6D9C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Seoul | F1FA-212E-96FC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Singapore | 6D3F-7BC1-C9FD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to South America | 26A6-AA3F-FFDA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Sydney | A4FD-F62A-2E80 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Toronto | 92B4-DBDF-BBC7 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Turin | 8756-62BC-CC2C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Warsaw | 23DA-1ED0-6C24 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Western Europe | 6E52-3768-7CE2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Data Transfer Out from Johannesburg to Zurich | DDA3-0420-7805 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Egress from Johannesburg to Mexico | A7F0-BDC7-CB0B | September 7, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Region Egress from Johannesburg to Stockholm | 2432-B8A3-42A0 | May 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Inter Zone Data Transfer Out in Johannesburg | AE8A-31DA-486D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to APAC | 88CD-73EF-4E3C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Africa | D9F5-2BE6-215B | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Americas | 8A3B-18E1-1657 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Australia | 0A52-C763-0047 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Berlin | 08B1-3FF4-12C2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Central America | D136-D3BF-E398 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to China | 39A4-6A8A-9677 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Columbus | DE50-DA90-29C2 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Dallas | 4AB2-A4DF-A7DC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Dammam | 513A-51F3-76F4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Day0 (Alabama) | 3F28-1B35-17F4 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Delhi | 8E65-3FB6-685D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Doha | EE18-FC76-AB72 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to EMEA | ABC9-9640-7FEA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Eastern Europe | 04BE-4A2A-A63F | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Finland | 264F-1DFB-0AEE | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Frankfurt | B42E-7D3A-6B2E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Hong Kong | 735D-3EE0-EDC5 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to India | 8012-CD1D-FF87 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Israel | F975-A485-EF26 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Jakarta | 48C4-C4F8-5037 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Japan | 27D7-6BE5-0D0D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Johannesburg | 119F-A106-197D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Las Vegas | CBD0-896B-90D6 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to London | D0DF-F881-A0DA | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Los Angeles | 596C-9D77-2282 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Madrid | 9899-B60F-0CAD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Melbourne | 92C6-188C-A506 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Middle East | ED1E-2481-396D | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Milan | 9C17-48BB-A464 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Montreal | C7DE-E283-0D00 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Mumbai | 6620-5D65-DBFD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Netherlands | 36F6-D60F-F2B7 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Northern Virginia | 4647-0CB2-06D3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Osaka | 43FB-CF6B-156A | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Paris | CF3E-47D9-A3ED | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Phoenix | 6978-3B98-0ACD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Salt Lake City | B3FE-D736-2B49 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Santiago | 51EE-1322-F5BD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Sao Paulo | F63B-9694-DFAD | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Seoul | 6E8E-C712-461E | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Singapore | F1D8-8F61-D6B3 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to South America | 814E-D77A-5AD0 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Sydney | 12A0-7BCB-DA87 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Toronto | 4038-AF18-3272 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Turin | 8004-A1AE-CF71 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Warsaw | 8EC9-B7D5-12DC | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Western Europe | F93A-49C0-712C | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Data Transfer Out from Johannesburg to Zurich | 78CC-6393-4725 | February 29, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Egress from Johannesburg to Mexico | 38AB-94E7-76A0 | September 7, 2024 |
| Cloud SQL (9662-B51E-5089) | Network Internet Egress from Johannesburg to Stockholm | 20EF-A82C-5084 | May 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Additional Read Only Replica (Johannesburg) | 2CF7-A292-66BB | February 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Backup storage for Regional Configuration (Johannesburg) | CDCE-1681-8BD7 | February 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Data Boost charges (Africa South 1) | 03D0-89E1-C365 | March 5, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Read-Only Replica for Enterprise Edition in Johannesburg (africa-south1) | 55FB-39FD-C614 | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Read-Only Replica for Enterprise Plus Edition in Johannesburg (africa-south1) | E10C-B67A-EFF0 | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Read-Write Replica for Enterprise Edition in Johannesburg (africa-south1) | 32C3-3838-3029 | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Read-Write Replica for Enterprise Plus Edition in Johannesburg (africa-south1) | 1C10-1DC2-DC7A | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Read-Write Replica for Standard Edition in Johannesburg (africa-south1) | A500-FFB1-7813 | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | SSD Storage for Replica in Johannesburg (africa-south1) | 35B3-3A91-437C | August 2, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Server Node for Regional Configuration (Johannesburg) | 876A-6496-61FA | February 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Storage for Additional Read Only Replica (Johannesburg) | 673C-B106-C031 | February 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Storage for Regional Configuration (Johannesburg) | 9BB1-D870-A040 | February 29, 2024 |
| Cloud Spanner (CC63-0873-48FD) | Witness Replica for Enterprise Plus Edition in Johannesburg (africa-south1) | 288A-97E9-9180 | August 2, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Archive Storage Johannesburg | D145-9D81-101D | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Archive Storage Johannesburg (Early Delete) | D472-34C7-6FA7 | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Autoclass Archive Storage Johannesburg | CF16-78C4-2B5A | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Autoclass Coldline Storage Johannesburg | CABD-3777-D226 | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Autoclass Nearline Storage Johannesburg | A92A-D153-D7CB | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Autoclass Standard Storage Johannesburg | 6E86-5BFD-DCDA | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Coldline Storage Johannesburg | 9A27-B3AE-E1C9 | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Coldline Storage Johannesburg (Early Delete) | 3332-1402-862C | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Durable Reduced Availability Storage Johannesburg | 6582-97C7-B6DD | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Nearline Storage Johannesburg | C056-22B3-40B3 | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Nearline Storage Johannesburg (Early Delete) | 5A0D-2598-CFD1 | February 29, 2024 |
| Cloud Storage (95FF-2EF5-5EA1) | Standard Storage Johannesburg | 4EC6-27CA-3AA0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Johannesburg | 73DD-2955-6A0A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Johannesburg | 711F-53E5-6E97 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | A3 Instance Core running in Johannesburg | 4A6B-1C23-CD35 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | A3 Instance Ram running in Johannesburg | D713-49E6-1754 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Asynchronous Replication Protection - PD Balanced in Johannesburg | C521-7267-3FAB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Asynchronous Replication Protection - PD SSD in Johannesburg | 8B16-1C55-1071 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Asynchronous Replication Protection - Regional PD Balanced in Johannesburg | D7A2-CE8C-3965 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Asynchronous Replication Protection - Regional PD SSD in Johannesburg | CE7B-2295-D303 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Johannesburg | 104E-81CB-48E3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Balanced PD Instant Snapshot data storage in Johannesburg | F4B1-9C57-1EB5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Johannesburg | 9364-03D6-8C8C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Johannesburg | B59E-3A0E-766B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3 Instance Core running in Johannesburg | 09A2-479C-53A6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3 Instance Ram running in Johannesburg | E37D-C096-B602 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3 Sole Tenancy Instance Core running in Johannesburg | 045A-61E9-546B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3 Sole Tenancy Instance Ram running in Johannesburg | 5512-6729-8C3E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3D Instance Core running in Johannesburg | 60F0-0531-3651 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3D Instance Ram running in Johannesburg | 1E39-39FE-3429 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3D Sole Tenancy Instance Core running in Johannesburg | EB8A-E443-0A3C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | C3D Sole Tenancy Instance Ram running in Johannesburg | A36A-19AA-B29E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A2 Cpu in Johannesburg for 1 Year | 5F7B-96CC-6375 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A2 Cpu in Johannesburg for 3 Years | CCE1-258F-8797 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A2 Ram in Johannesburg for 1 Year | 0397-455B-8D64 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A2 Ram in Johannesburg for 3 Years | 043C-E1E8-F7C2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A3 Cpu in Johannesburg for 1 Year | 8B81-F82B-1F08 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A3 Cpu in Johannesburg for 3 Years | B45D-9DA9-36D0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A3 Ram in Johannesburg for 1 Year | 3073-3B7E-9E4A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: A3 Ram in Johannesburg for 3 Years | 0603-7E9F-4DB3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C2D AMD Cpu in Johannesburg for 1 Year | C265-20A3-F904 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C2D AMD Cpu in Johannesburg for 3 Years | 90CC-145F-5AEC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C2D AMD Ram in Johannesburg for 1 Year | B387-6314-1527 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C2D AMD Ram in Johannesburg for 3 Years | 274E-0CBC-52E4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3 Cpu in Johannesburg for 1 Year | 9F8E-83D2-D753 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3 Cpu in Johannesburg for 3 Years | BBF8-AB87-0B70 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3 Ram in Johannesburg for 1 Year | 0198-394B-6CCF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3 Ram in Johannesburg for 3 Years | B666-C67B-1275 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3D Cpu in Johannesburg for 1 Year | 9467-E8FB-AA89 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3D Cpu in Johannesburg for 3 Years | 3900-4F48-5406 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3D Ram in Johannesburg for 1 Year | 7363-FBCB-F420 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: C3D Ram in Johannesburg for 3 Years | 78B6-F85C-9D0B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Compute optimized Cpu in Johannesburg for 1 Year | 4BB5-BF1F-81D9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Compute optimized Cpu in Johannesburg for 3 Years | FFA5-A2F7-4894 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Compute optimized Ram in Johannesburg for 1 Year | CF28-3A99-BAD6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Compute optimized Ram in Johannesburg for 3 Years | 141F-65EF-B0B2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: E2 Cpu in Johannesburg for 1 Year | 6F44-1E26-287E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: E2 Cpu in Johannesburg for 3 Years | 1184-C225-561B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: E2 Ram in Johannesburg for 1 Year | 3380-9723-63F0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: E2 Ram in Johannesburg for 3 Years | 3594-142D-9D31 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: G2 Cpu in Johannesburg for 1 Year | 6667-0866-D765 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: G2 Cpu in Johannesburg for 3 Years | BFE0-9E03-A61D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: G2 Ram in Johannesburg for 1 Year | 3BCD-661F-D51A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: G2 Ram in Johannesburg for 3 Years | 5393-24B7-48FB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: H3 Cpu in Johannesburg for 1 Year | 1424-D2FA-C871 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: H3 Cpu in Johannesburg for 3 Years | 2F2F-4633-EB97 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: H3 Ram in Johannesburg for 1 Year | 47D6-5EDE-2AA8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: H3 Ram in Johannesburg for 3 Years | 1C69-E85D-5E6D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Local SSD in Johannesburg for 1 Year | 56AB-6330-0810 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Local SSD in Johannesburg for 3 Year | 901A-D30A-C008 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: M3 Memory-optimized Cpu in Johannesburg for 1 Year | 5D01-DC1E-D685 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: M3 Memory-optimized Cpu in Johannesburg for 3 Years | 49EA-B5AD-986B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: M3 Memory-optimized Ram in Johannesburg for 1 Year | 0493-2E21-9212 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: M3 Memory-optimized Ram in Johannesburg for 3 Years | 2165-7F38-30E8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Memory-optimized Cpu in Johannesburg for 1 Year | A77B-6468-AAE4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Memory-optimized Cpu in Johannesburg for 3 Years | B314-D97D-317B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Memory-optimized Ram in Johannesburg for 1 Year | 935F-B3CB-82D4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Memory-optimized Ram in Johannesburg for 3 Years | 0201-6A65-58B1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N1 Cpu in Johannesburg for 1 Year | ED66-B119-0C8F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N1 Cpu in Johannesburg for 3 Years | EE9B-426E-9D33 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N1 Ram in Johannesburg for 1 Year | ECB6-03A9-1E40 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N1 Ram in Johannesburg for 3 Years | 7E83-E559-B3B5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2 Cpu in Johannesburg for 1 Year | 2EE1-B98B-865B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2 Cpu in Johannesburg for 3 Years | 4F50-DBAD-D6C2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2 Ram in Johannesburg for 1 Year | E047-6119-C46D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2 Ram in Johannesburg for 3 Years | EB99-5169-F795 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2D AMD Cpu in Johannesburg for 1 Year | E343-7438-52B2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2D AMD Cpu in Johannesburg for 3 Years | 4072-AF72-E723 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2D AMD Ram in Johannesburg for 1 Year | F0E1-61E7-6ABC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: N2D AMD Ram in Johannesburg for 3 Years | 7E48-DC97-7745 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia H100 80GB GPU running in Johannesburg for 1 Year | 8457-1A66-DC99 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia H100 80GB GPU running in Johannesburg for 3 Years | FD26-E458-CBA3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia L4 GPU running in Johannesburg for 1 Year | 8F3A-CF4F-ACB7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia L4 GPU running in Johannesburg for 3 Years | 320B-324A-4809 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla A100 80GB GPU running in Johannesburg for 1 Year | E009-764E-F743 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla A100 80GB GPU running in Johannesburg for 3 Years | 616F-36FD-6C77 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla A100 GPU running in Johannesburg for 1 Year | 5A0D-6234-83BB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla A100 GPU running in Johannesburg for 3 Years | A6AA-26BD-485E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla P100 GPU running in Johannesburg for 1 Year | E3D6-FA03-86DE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla P100 GPU running in Johannesburg for 3 Years | AFF0-5693-E12B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla P4 GPU running in Johannesburg for 1 Year | F9FF-276C-69C5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla P4 GPU running in Johannesburg for 3 Years | CFD1-967A-3C2F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla T4 GPU running in Johannesburg for 1 Year | 2ED1-05EF-6011 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla T4 GPU running in Johannesburg for 3 Years | B687-E571-20A4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla V100 GPU running in Johannesburg for 1 Year | C76F-B76B-8A19 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Nvidia Tesla V100 GPU running in Johannesburg for 3 Years | E87D-5F3C-6F26 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: T2D AMD Cpu in Johannesburg for 1 Year | 191A-4188-826C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: T2D AMD Cpu in Johannesburg for 3 Years | 01B2-38E5-0C43 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: T2D AMD Ram in Johannesburg for 1 Year | 6BE2-3C18-CB25 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: T2D AMD Ram in Johannesburg for 3 Years | 055D-1CD0-73AF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5e running in Johannesburg for 1 Year | F2EE-630A-2D9F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5e running in Johannesburg for 3 Years | 3D29-A1E3-809F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Johannesburg for 1 Year | 879D-965E-CDD1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Johannesburg for 3 Years | 6E0B-8117-94F5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Z3 Cpu in Johannesburg for 1 Year | 1C0F-C06C-4674 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Z3 Cpu in Johannesburg for 3 Years | EFA0-74FA-1FFF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Z3 Ram in Johannesburg for 1 Year | D5C6-2EC2-5067 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: Z3 Ram in Johannesburg for 3 Years | B6D9-9A46-A2F2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for Custom Instance Core running in Johannesburg | DE76-9193-D701 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for Custom Instance Ram running in Johannesburg | 662A-2E30-C89B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for E2 Custom Instance Core running in Johannesburg | E587-D0EB-370B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for E2 Custom Instance Ram running in Johannesburg | 304E-4E85-0875 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for G2 Custom Instance Core running in Johannesburg | 7C98-5D40-BAFE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for G2 Custom Instance Ram running in Johannesburg | 2617-F166-8FE3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for N2 Custom Instance Core running in Johannesburg | 84FF-5864-BDBB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for N2 Custom Instance Ram running in Johannesburg | 85C5-8902-CFCB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for N2D AMD Custom Instance Core running in Johannesburg | 30CA-A4C9-98FA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Committed Use Discount Premium for N2D AMD Custom Instance Ram running in Johannesburg | 8E7F-EFEB-DAA2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Johannesburg | 225D-93F0-5B57 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Johannesburg | E986-53A1-EAA8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Johannesburg | 09AC-31B4-0AED | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Johannesburg | 6738-0198-0A4D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Johannesburg | 1E20-53DB-3A56 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Johannesburg | 60F1-9944-4B48 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Johannesburg | EE14-97CB-4205 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Johannesburg | 868F-5971-152F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Johannesburg | 855D-C33E-F06B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Johannesburg | DC64-21B2-0622 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Johannesburg | 545C-0B0B-55EE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Johannesburg | F9EA-ECD9-A733 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Johannesburg | 3240-A5EF-FA06 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD Instant Snapshot data storage in Johannesburg | 1506-1F0E-8ECA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Custom Instance Core running in Johannesburg | 4D4F-129F-4A9E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Custom Instance Ram running in Johannesburg | D894-C133-9DC2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Instance Core running in Johannesburg | 07D3-2C12-0F51 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Instance Ram running in Johannesburg | C4F2-0856-E477 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Sole Tenancy Instance Core running in Johannesburg | 7507-A801-7399 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | G2 Sole Tenancy Instance Ram running in Johannesburg | D07B-EF48-1AC9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | H3 Instance Core running in Johannesburg | 5C49-BFBA-4DF3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | H3 Instance Ram running in Johannesburg | A7D9-A71E-9EB7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | H3 Sole Tenancy Instance Core running in Johannesburg | 1EA8-62CB-781D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | H3 Sole Tenancy Instance Ram running in Johannesburg | C23C-F587-AF31 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Capacity Confidential Mode in Johannesburg | 8AAB-C788-32AC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Capacity in Johannesburg | E2B7-321A-8F3C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced High Availability Capacity in Johannesburg | D68F-9207-5386 | June 18, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced High Availability Iops in Johannesburg | 4596-A9DE-EAB1 | June 18, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced High Availability Throughput in Johannesburg | B5D8-A98E-7156 | June 18, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced IOPS Confidential Mode in Johannesburg | F8B5-AB53-381B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced IOPS in Johannesburg | 2970-AD24-0493 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Advanced Capacity - Johannesburg | EAF8-50D8-623B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Advanced IOPS - Johannesburg | 6791-1FE5-EEE4 | June 5, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Advanced Throughput - Johannesburg | AB21-B19F-1F3E | June 5, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Standard Capacity - Johannesburg | 9092-40B2-858E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Standard IOPS - Johannesburg | C4C3-1B87-185E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Storage Pools Standard Throughput - Johannesburg | 22BB-2816-8570 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Throughput Confidential Mode in Johannesburg | C1C5-3D74-927C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Balanced Throughput in Johannesburg | B150-B38C-32EC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Extreme Capacity in Johannesburg | DE94-1529-874C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Extreme IOPS in Johannesburg | BB17-D195-3F75 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk ML Capacity in Johannesburg | 34BF-C809-1B2F | April 6, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk ML Throughput in Johannesburg | BC8B-6302-F0F9 | April 6, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Throughput Storage Pools Advanced Capacity - Johannesburg | 43F2-C852-98C5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Throughput Storage Pools Advanced Throughput - Johannesburg | 1041-2052-51FC | June 5, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Throughput Storage Pools Standard Capacity - Johannesburg | 0527-0F9F-1020 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Hyperdisk Throughput Storage Pools Standard Throughput - Johannesburg | A79A-F50F-9CCE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Johannesburg | 18C2-38D4-4B92 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Johannesburg | 9D85-4C45-0AAA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 39AC-14FC-6FCF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | FDD4-53AD-53EE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Johannesburg | 73CA-C558-D786 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Johannesburg | C9F6-B904-AE6A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Johannesburg | 3DF8-AF05-BA4E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Johannesburg | F6AA-F426-BD45 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 211C-6A50-A5F1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 5A43-3E1E-8A1F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Johannesburg | 5AEF-5436-7205 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Johannesburg | FE0B-E0C0-0034 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Johannesburg | 0298-73DA-B49E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Johannesburg | FD04-C6CD-56FF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Johannesburg | 2DC2-2DB0-925E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Johannesburg | 634C-B735-3E12 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Johannesburg | EE46-3F79-CA9D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Johannesburg | 2877-22EB-5946 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Johannesburg | 6162-8660-EE3D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Johannesburg | E089-B561-1E7E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Johannesburg | 3C85-25F1-A0B8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Johannesburg | 7693-1EF9-B6A1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Johannesburg | 7866-0AD5-B78D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Johannesburg | A903-CE02-AD33 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Johannesburg | D455-945C-A274 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Johannesburg | 9CC1-342B-FCE6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 822B-0FE0-5F2C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Data Transfer In from Google Services from Johannesburg to Johannesburg | 208F-F639-05C9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Data Transfer to Google Services from Johannesburg to Johannesburg | 05B5-AC0E-003B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from APAC to Johannesburg | 9300-8301-B6A8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Americas to Johannesburg | 3133-D3EE-FECE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Berlin to Johannesburg | F3D9-C73C-5D7B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Columbus to Johannesburg | F2B0-9323-30DE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Dallas to Johannesburg | 101D-1E08-4965 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Dammam to Johannesburg | C66E-5CD6-CA02 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Delhi to Johannesburg | 5C0E-DCCB-71DD | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Doha to Johannesburg | E31F-D386-1C4A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from EMEA to Johannesburg | 45D0-7732-8BEB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Finland to Johannesburg | 2338-28C2-F801 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Frankfurt to Johannesburg | 0173-A5F3-1267 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Hong Kong to Johannesburg | CE46-3912-98D1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Israel to Johannesburg | 061A-DAAB-DC06 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Jakarta to Johannesburg | 0C6F-F6FE-50CF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Japan to Johannesburg | 7F44-B284-EB3F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Las Vegas to Johannesburg | 9052-196F-AAE3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from London to Johannesburg | E84B-6A98-3FC2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Los Angeles to Johannesburg | 92FE-C9C1-5A19 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Madrid to Johannesburg | E5DF-87FF-8B16 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Melbourne to Johannesburg | 216E-2655-5FC6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Mexico to Johannesburg | 44C3-4D1A-8A65 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Milan to Johannesburg | 13CF-6BC2-11A9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Montreal to Johannesburg | 0D27-9B1E-1BA4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Mumbai to Johannesburg | A24B-C0EF-8E96 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Netherlands to Johannesburg | 25AB-AC6C-589E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Osaka to Johannesburg | 8504-ECE6-40A3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Paris to Johannesburg | 9FCA-4996-E039 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Phoenix to Johannesburg | C40B-A71B-01C7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Salt Lake City to Johannesburg | 20EE-AFD6-BCAC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Santiago to Johannesburg | D269-AF3E-BD9E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Sao Paulo to Johannesburg | A4FC-D48E-3DBA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Seoul to Johannesburg | 5BAE-9C73-A23A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Singapore to Johannesburg | 7A65-E462-6AB9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Stockholm to Johannesburg | BFFF-847E-ED87 | May 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Sydney to Johannesburg | B774-898C-DB93 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Toronto to Johannesburg | 4292-766A-6297 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Turin to Johannesburg | 9B38-2031-58EB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Virginia to Johannesburg | 80F6-728E-922C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Warsaw to Johannesburg | 8DFD-AF9C-E0F5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer In from Zurich to Johannesburg | 2FD8-0C83-73F4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to APAC | 6C53-A1E2-4C8A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Americas | F5B8-7AA0-537F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Berlin | 38B2-7066-BE33 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Columbus | 94DE-9702-2172 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Dallas | 5EE5-84C1-34DE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Dammam | 40B7-0F32-96C9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Delhi | 6268-8774-F3E3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Doha | 4EC3-A2C8-FBA4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to EMEA | 82C4-ACF0-2521 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Finland | 2686-0338-D928 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Frankfurt | 8248-15D0-9220 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Hong Kong | 833F-BEE7-8C46 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Israel | 63EA-7301-77E6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Jakarta | CCAB-2067-F91C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Japan | FE7E-2C22-E2B8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Las Vegas | 8F19-F4D0-C9F5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to London | 27F5-ABD6-7A03 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Los Angeles | 61DB-3C55-48AE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Madrid | 2891-1CF1-31C7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Melbourne | 5D20-CEE4-4971 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Mexico | 0515-DFED-B04C | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Milan | C3F8-C340-9DC3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Montreal | 4EA3-E9B4-3705 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Mumbai | CF07-E946-675D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Netherlands | A832-FCC0-86B7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Osaka | 1364-18BE-F998 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Paris | 8545-560A-8EF5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Phoenix | B3CA-0C28-2AE6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Salt Lake City | 22EC-D5D1-9D90 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Santiago | 64ED-BB90-C9CA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Sao Paulo | FD2B-21FD-54C0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Seoul | 649C-07ED-759B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Singapore | 6A85-8002-8553 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Stockholm | 8570-417B-3E8B | May 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Sydney | 6510-8C42-6F40 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Toronto | 8FD1-659B-6AA1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Turin | 110E-755B-6C09 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Virginia | F3B3-E6C2-E9A1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Warsaw | B4AA-AA73-1212 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Inter Region Data Transfer Out from Johannesburg to Zurich | 48E4-60A3-EBF0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from APAC to Johannesburg | BE48-C2F1-88D7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Africa to Johannesburg | 8291-64EB-244C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Americas to Johannesburg | 7E35-1B00-752C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Apac(Excluding Korea and Indonesia) to Johannesburg | A1E5-D131-560D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Australia to Johannesburg | ECDF-14AE-9E3E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Central America to Johannesburg | 2B2C-BF5E-3576 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from China to Johannesburg | 195B-3D01-D27E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from EMEA to Johannesburg | 4B7C-D53B-2CEF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Eastern Europe to Johannesburg | F747-4240-8978 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from India to Johannesburg | 157C-DA7B-5E0B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Indonesia to Johannesburg | 2910-409F-9FC2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Middle East to Johannesburg | 0092-2455-AB1E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from South America to Johannesburg | D0D5-16C1-6417 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from South Korea to Johannesburg | 939E-1D14-E795 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer In from Western Europe to Johannesburg | 6997-BD31-4A04 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to APAC | 3D4E-101E-27B5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Africa | 6796-9E53-E9A4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Americas | 9646-C040-2C1C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Apac(Excluding Korea and Indonesia) | 1C91-35D5-62C5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Australia | BF7A-716B-0E79 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Central America | 46C0-CAE6-EEAB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to China | 99F2-3537-8155 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to EMEA | 329A-B687-FDF3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Eastern Europe | E64D-A5C7-E569 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to India | 069E-CF83-47E1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Indonesia | CA9D-4DCD-B50B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Middle East | 1FE9-291B-FD8B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to South America | DCCB-57C0-4ABC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to South Korea | 7BF8-99F7-3579 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Internet Data Transfer Out from Johannesburg to Western Europe | 83D4-745E-F6E1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Packet Mirroring: Data Processing Charge in Johannesburg | 55E9-AA88-19BD | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Standard Data Transfer Out to Internet from Johannesburg | DAD4-BC8E-2E55 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Standard Internet Data Transfer In to Johannesburg | 658B-8A99-E918 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from APAC to Johannesburg | E5DD-D75D-53C7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Americas to Johannesburg | 1093-2C9E-D79A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Berlin to Johannesburg | F0F9-28B5-6880 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Columbus to Johannesburg | C9FC-9825-13CA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Dallas to Johannesburg | 8269-A744-5CB7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Dammam to Johannesburg | 4FCD-A86E-72B5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Delhi to Johannesburg | 8EBF-D8EB-D45A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Doha to Johannesburg | 2F8F-19A4-2E8E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from EMEA to Johannesburg | 8993-E909-09BB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Finland to Johannesburg | E61B-CCE7-63AB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Frankfurt to Johannesburg | F25D-28AA-7166 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Hong Kong to Johannesburg | BB96-93DF-D393 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Israel to Johannesburg | EE2B-797A-3292 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Jakarta to Johannesburg | 5D79-403A-3EBC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Japan to Johannesburg | A0B0-A4E3-94CC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Las Vegas to Johannesburg | 8082-81E5-A7E8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from London to Johannesburg | 1DBD-4DC6-5BFF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Los Angeles to Johannesburg | BA86-C166-639D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Madrid to Johannesburg | 3394-B0E6-9C5B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Melbourne to Johannesburg | 999D-814A-3C5A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Mexico to Johannesburg | 0918-7BDE-3639 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Milan to Johannesburg | 2E9C-F61C-3CD2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Montreal to Johannesburg | C1F8-F5F8-9AAF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Mumbai to Johannesburg | 5AC3-3513-7FD9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Netherlands to Johannesburg | DADE-943E-4775 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Osaka to Johannesburg | E42B-35AB-F9F2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Paris to Johannesburg | C702-014F-60B2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Phoenix to Johannesburg | 7764-1EB4-41D5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Salt Lake City to Johannesburg | 8620-4263-8BC3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Santiago to Johannesburg | C548-2BF4-9374 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Sao Paulo to Johannesburg | 124A-DEC2-2C19 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Seoul to Johannesburg | B82B-1098-B39F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Singapore to Johannesburg | 4B4D-D52B-C384 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Stockholm to Johannesburg | B405-E35D-7B34 | May 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Sydney to Johannesburg | 523D-9260-DFBB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Toronto to Johannesburg | BE53-8D77-01E2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Turin to Johannesburg | 89EA-3632-D8E0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Virginia to Johannesburg | 087F-49D3-6E60 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Warsaw to Johannesburg | 235F-F658-720F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer In from Zurich to Johannesburg | 1926-D195-5064 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to APAC | DC01-B7D2-1CAE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Americas | 6A51-F0EE-79E7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Berlin | 494A-7E22-AC94 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Columbus | 8464-C3EF-4377 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Dallas | F2FD-AA6D-04CB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Dammam | 292A-AC1A-D9E3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Delhi | 60B2-3F69-51B3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Doha | 4F9E-3D75-1341 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to EMEA | F343-2DAD-67F4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Finland | 5143-34C4-8372 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Frankfurt | 6022-E70C-3E9B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Hong Kong | 89A5-54AC-0EB8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Israel | 86F9-83FD-BE14 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Jakarta | 6461-D3EB-8B9B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Japan | 0776-3169-F14C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Las Vegas | 6219-4CE7-49A3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to London | 1957-4CC3-63F5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Los Angeles | E445-B0A7-6E80 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Madrid | 30A2-1397-D1A9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Melbourne | 5215-2155-BF20 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Mexico | F1D0-AF65-7E15 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Milan | 7F7D-54DC-7EB9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Montreal | 708C-992E-4665 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Mumbai | 2D22-3FBB-4360 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Netherlands | 41C6-E940-460E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Osaka | 8B0B-2452-B39A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Paris | 013B-68C0-84F1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Phoenix | AF4E-DF22-9034 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Salt Lake City | C86F-7B1D-C157 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Santiago | EA57-F0A9-251E | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Sao Paulo | 3DBD-9295-6009 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Seoul | 68FE-FE20-2A61 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Singapore | BDA3-B073-0611 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Stockholm | BEBC-A82E-B9A7 | May 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Sydney | B92E-82E9-52F3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Toronto | A48B-B907-EFAD | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Turin | D226-4F0D-8C72 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Virginia | FDB8-A75F-EA02 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Warsaw | 7CA1-4807-712A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Inter Region Data Transfer Out from Johannesburg to Zurich | 7095-C238-B50B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from APAC to Johannesburg | 01F6-BCFB-3E30 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Africa to Johannesburg | D29D-E438-34BA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Americas to Johannesburg | 92A1-8474-B3A9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Australia to Johannesburg | 4D48-7D16-FD88 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Central America to Johannesburg | 055E-B3B5-FBFF | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from China to Johannesburg | 12D2-B7EA-5060 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from EMEA to Johannesburg | 03A8-5B06-9BF7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Eastern Europe to Johannesburg | 4C3D-888B-DD1A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from India to Johannesburg | FFE6-0C9E-4569 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Middle East to Johannesburg | AFF3-526E-0A3F | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from South America to Johannesburg | 7212-D8C7-BAB5 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer In from Western Europe to Johannesburg | DCDD-F6C9-E030 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to APAC | 6942-5E94-E7B6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Africa | 3D0C-D002-8309 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Americas | 8CBF-6DAC-BB8D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Australia | 8779-EC61-D780 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Central America | 0BC5-0794-4F23 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to China | 9A19-8069-DFFE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to EMEA | 2FFA-0A2E-9DD6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Eastern Europe | E867-B6D1-9174 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to India | 0701-D868-30B4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Middle East | E0BC-BEA3-80DC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to South America | 93E5-0B20-62E4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Network Vpn Internet Data Transfer Out from Johannesburg to Western Europe | 5392-BF84-4DBB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia H100 80GB GPU running in Johannesburg | 64A6-EE3E-D6C1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia L4 GPU running in Johannesburg | D098-F9B5-7DA2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Johannesburg | DF7B-A9A2-2710 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Johannesburg | 6F4F-446B-3D40 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Johannesburg | B87E-401F-15FE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Johannesburg | 3E61-572B-CB63 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Johannesburg | 4E64-C68C-198C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Johannesburg | 47AD-5ED1-71DE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Johannesburg | 8692-465A-518D | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Johannesburg | 1599-A2EA-2B54 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Johannesburg | 57A1-6EC5-2A62 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Johannesburg | 7FE8-7B38-5305 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Archive Snapshot Data Storage in Johannesburg | A397-2E8D-3FCC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Archive Snapshot Early Deletion in Johannesburg | 7815-5DDB-42A4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Archive Snapshot Retrieval in Johannesburg | 8AAB-CFB8-4059 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Johannesburg | DA42-2123-4782 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Instant Snapshot data storage in Johannesburg | 151A-EC61-5013 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional SSD PD Instant Snapshot data storage in Johannesburg | 7486-6E39-5804 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Johannesburg | 4A9E-5877-B916 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Standard PD Instant Snapshot data storage in Johannesburg | E2BC-50C5-14A9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Standard Snapshot Early Deletion in Johannesburg | 274B-7C21-5260 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Johannesburg | 6A49-499D-3637 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Reserved A2 Core in Johannesburg | 0A19-1D14-2EAB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Reserved A2 Ram in Johannesburg | D56D-6AFB-E7E4 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Reserved Nvidia Tesla A100 80GB GPU in Johannesburg | C424-63B4-DFB2 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Reserved Nvidia Tesla A100 GPU in Johannesburg | 1C28-AD71-51D3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | SSD PD Instant Snapshot data storage in Johannesburg | 0389-304F-8EEB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Johannesburg | 64C3-AF0B-D8C1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Johannesburg | 138B-0046-2B0C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Johannesburg | 695F-24A0-9B21 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Johannesburg | AEB4-2466-CBBE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Johannesburg | 8B14-A8F9-9239 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Johannesburg | 33DB-3B66-132A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Johannesburg | 9A82-A9A2-C89C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Johannesburg | DD22-23F3-4322 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Johannesburg | F776-A177-C7F3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 90A3-BE7F-92B6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Johannesburg | E344-29C7-E6F9 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Johannesburg | 8A19-F1A1-2FD3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for C3 Sole Tenancy Instance Core running in Johannesburg | C550-882D-B2B1 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for C3 Sole Tenancy Instance Ram running in Johannesburg | 0E01-96C9-2424 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for C3D Sole Tenancy Instance Core running in Johannesburg | C691-EBD3-6EDA | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for C3D Sole Tenancy Instance Ram running in Johannesburg | 79D1-CDEE-8CF8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Johannesburg | 98F3-31F7-E336 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Johannesburg | 0C16-A20C-4552 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for G2 Sole Tenancy Instance Core running in Johannesburg | 3F75-6BFF-6CD3 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for G2 Sole Tenancy Instance Ram running in Johannesburg | 8AB8-D20B-A39B | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for H3 Sole Tenancy Instance Core running in Johannesburg | FCAE-29B3-FB98 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for H3 Sole Tenancy Instance Ram running in Johannesburg | CC80-F2D7-53FB | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 4926-5349-72C0 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 714A-1906-4019 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Johannesburg | C09D-D7A7-DCDC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 62B4-F0AD-520A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Johannesburg | EA0A-26D6-23AE | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Johannesburg | E734-EF5C-DD75 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Johannesburg | CFBF-EA17-0485 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 5183-92C5-0667 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Johannesburg | 477A-52C3-5F58 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Johannesburg | D2F6-502A-F98C | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Standard PD Instant Snapshot data storage in Johannesburg | 1FA7-E1AA-012A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Static Ip Charge in Johannesburg | FD9E-F24C-FDA7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Storage Image in Johannesburg | 90B0-57E1-0A96 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Storage Machine Image in Johannesburg | 80A7-680E-9D96 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Johannesburg | EEFE-F863-E07A | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Johannesburg | EC86-922F-4ED8 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Johannesburg | 6AC7-5DA4-3E28 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Johannesburg | E827-970B-40FC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | TpuV5e attached to Spot Preemptible VMs running in Johannesburg | E286-42C6-C4DC | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | TpuV5e running in Johannesburg | 8793-2414-CFE6 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | TpuV5p attached to Spot Preemptible VMs running in Johannesburg | D9FE-981F-1737 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | TpuV5p running in Johannesburg | 7C1C-7160-4E67 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Johannesburg | B0D1-AA0B-61B7 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Z3 Instance Core running in Johannesburg | 0464-7B59-8D22 | February 29, 2024 |
| Compute Engine (6F81-5844-456A) | Z3 Instance Ram running in Johannesburg | 47ED-BC03-07A9 | February 29, 2024 |
| Database Migration (116A-ED39-D1F0) | Database migration service CDC bytes copied in Johannesburg | 1A2C-BB0A-107A | February 29, 2024 |
| Database Migration (116A-ED39-D1F0) | Database migration service full dump bytes copied in Johannesburg | D3A2-5C57-D0AE | February 29, 2024 |
| Dataplex (51C6-B3F5-9B38) | Dataplex Metadata Storage Johannesburg | 64BC-0D0F-DB5E | July 25, 2024 |
| Dataplex (51C6-B3F5-9B38) | Dataplex Processing (milli DCU-hr) Johannesburg | C99C-F71A-151F | March 29, 2024 |
| Dataplex (51C6-B3F5-9B38) | Dataplex Shuffle Storage Johannesburg | DDB1-E954-A836 | March 23, 2024 |
| Dataproc (363B-8851-170D) | A100-40 Accelerator (milli) Hours - Dataproc Serverless Batch - africa-south1 | EBF4-D2B8-230F | February 29, 2024 |
| Dataproc (363B-8851-170D) | A100-40 Accelerator (milli) Hours - Dataproc Serverless Interactive - africa-south1 | 48AA-FE25-9F5B | February 29, 2024 |
| Dataproc (363B-8851-170D) | A100-80 Accelerator (milli) Hours - Dataproc Serverless Batch - africa-south1 | 204E-BE53-C808 | February 29, 2024 |
| Dataproc (363B-8851-170D) | A100-80 Accelerator (milli) Hours - Dataproc Serverless Interactive - africa-south1 | 6641-A687-9EC1 | February 29, 2024 |
| Dataproc (363B-8851-170D) | Data Compute Unit (milli) Hours - Dataproc Serverless Batch - africa-south1 | 740B-5FAE-039C | February 29, 2024 |
| Dataproc (363B-8851-170D) | Data Compute Unit (milli) Hours - Dataproc Serverless Interactive - africa-south1 | FBAD-D644-02B4 | February 29, 2024 |
| Dataproc (363B-8851-170D) | Data Compute Unit Premium (milli) Hours - Dataproc Serverless Batch - africa-south1 | C27E-86E1-3759 | February 29, 2024 |
| Dataproc (363B-8851-170D) | Dataproc Serverless Shuffle Storage GB-Months - africa-south1 | FA85-F30D-3D39 | February 29, 2024 |
| Dataproc (363B-8851-170D) | Dataproc Serverless Shuffle Storage Premium GB-Months - africa-south1 | 132B-B7BE-DC18 | February 29, 2024 |
| Dataproc (363B-8851-170D) | L4 Accelerator (milli) Hours - Dataproc Serverless Batch - africa-south1 | 056D-085A-FA03 | February 29, 2024 |
| Dataproc (363B-8851-170D) | L4 Accelerator (milli) Hours - Dataproc Serverless Interactive - africa-south1 | ED22-4236-B207 | February 29, 2024 |
| Datastream (7EC6-CE53-9E39) | Backfill Bytes Processed Johannesburg | 106D-5832-B040 | February 29, 2024 |
| Datastream (7EC6-CE53-9E39) | CDC Bytes Processed Johannesburg | D3CD-5513-1F0D | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Balanced Pod Memory Requests (africa-south1) | 5467-100D-82E8 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Balanced Pod mCPU Requests (africa-south1) | DBBF-8FCB-9CE9 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Balanced Spot Pod Memory Requests (africa-south1) | DDA2-7DD7-F40A | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Balanced Spot Pod mCPU Requests (africa-south1) | 64D8-E1C5-608F | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Local SSD Premium (africa-south1) | B36F-BE55-570B | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Local SSD Spot Premium (africa-south1) | 31E5-F6B8-7F0B | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot PD Balanced Premium (africa-south1) | 2D56-72D5-F117 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Performance CPU Premium (africa-south1) | 2003-E88C-3A9F | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Performance Memory Premium (africa-south1) | D8D4-F71A-E5C0 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Performance Spot CPU Premium (africa-south1) | 342F-EB83-4C83 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Performance Spot Memory Premium (africa-south1) | 1144-033D-9FF7 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Pod Ephemeral Storage Requests (africa-south1) | B501-52AB-3A5A | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Pod Memory Requests (africa-south1) | A14F-F8C9-627C | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Pod mCPU Requests (africa-south1) | C30F-700B-0257 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot SSD Pod Ephemeral Storage Requests (africa-south1) | 6A21-9F84-41C8 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Spot Pod Memory Requests (africa-south1) | 3E52-93FA-BDF2 | February 29, 2024 |
| Kubernetes Engine (CCD8-9BF1-090E) | Autopilot Spot Pod mCPU Requests (africa-south1) | 6907-A278-CFB8 | February 29, 2024 |
| Managed Service for Apache Kafka (9544-7B1C-811D) | Data Compute Units in africa-south1 | 4FFF-BC53-EA94 | August 29, 2024 |
| Managed Service for Apache Kafka (9544-7B1C-811D) | Local Storage in africa-south1 | AB59-A115-AACE | August 29, 2024 |
| Managed Service for Apache Kafka (9544-7B1C-811D) | Long Term Regional Storage in africa-south1 | 3FC1-EF88-38D9 | August 29, 2024 |
| NetApp Volumes (FC86-5113-7C81) | NetApp Volumes Capacity Flex Regional Johannesburg | 3716-6BC3-39ED | September 4, 2024 |
| NetApp Volumes (FC86-5113-7C81) | NetApp Volumes Capacity Flex Zonal Johannesburg | D06B-D1FA-8865 | July 26, 2024 |
| Networking (E505-1604-58F8) | Cloud Load Balancer Forwarding Rule Additional for Johannesburg (africa-south1) | CE0F-A297-888E | February 29, 2024 |
| Networking (E505-1604-58F8) | Cloud Load Balancer Forwarding Rule Minimum for Johannesburg (africa-south1) | C2D1-893E-F33B | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Application Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | ED2E-6FA8-C959 | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Application Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 22CD-705F-6995 | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Application Load Balancer Proxy Instance Charge for Johannesburg (africa-south1) | 6EC6-86A7-9DA0 | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Proxy Network Load Balancer Forwarding Rule Additional for Johannesburg (africa-south1) | E2AC-16D2-2A7F | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Proxy Network Load Balancer Forwarding Rule Minimum for Johannesburg (africa-south1) | EA21-22B1-A981 | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Proxy Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | CD96-9232-A1ED | February 29, 2024 |
| Networking (E505-1604-58F8) | Cross Regional Internal Proxy Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 6971-59FF-A65D | February 29, 2024 |
| Networking (E505-1604-58F8) | Global External Application Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 63FE-DC58-DF68 | February 29, 2024 |
| Networking (E505-1604-58F8) | Global External Application Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | F232-E90A-C200 | February 29, 2024 |
| Networking (E505-1604-58F8) | Global External Proxy Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 41D0-1E3F-DA0F | February 29, 2024 |
| Networking (E505-1604-58F8) | Global External Proxy Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 574E-F126-1B9B | February 29, 2024 |
| Networking (E505-1604-58F8) | Networking Cloud VPN Tunnel Africasouth1 | 7809-BAEF-088A | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Application Load Balancer Forwarding Rule Additional for Johannesburg (africa-south1) | A3A5-8281-B766 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Application Load Balancer Forwarding Rule Minimum for Johannesburg (africa-south1) | CF6E-2DE4-8861 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Application Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 1603-E19B-DD92 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Application Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 2A55-54D9-70F4 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Passthrough Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 6848-877A-A16D | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Passthrough Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 7DC3-50B8-45A2 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Proxy Network Load Balancer Forwarding Rule Additional for Johannesburg (africa-south1) | 50B2-4818-AE19 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Proxy Network Load Balancer Forwarding Rule Minimum for Johannesburg (africa-south1) | 479D-6BCD-11E7 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Proxy Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | E3C5-0479-4FC8 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional External Proxy Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | B282-5A11-6972 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Application Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 815B-9961-F84D | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Application Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 9EAD-34FC-E9B9 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Application Load Balancer Proxy Instance Charge for Johannesburg (africa-south1) | BC92-1DE8-B1D1 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Passthrough Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 35C9-7009-D82B | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Passthrough Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | 63F4-DA4B-2658 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Proxy Network Load Balancer Forwarding Rule Additional for Johannesburg (africa-south1) | 4E21-8B87-06A5 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Proxy Network Load Balancer Forwarding Rule Minimum for Johannesburg (africa-south1) | 3474-8D03-C700 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Proxy Network Load Balancer Inbound Data Processing for Johannesburg (africa-south1) | 8628-9561-8E01 | February 29, 2024 |
| Networking (E505-1604-58F8) | Regional Internal Proxy Network Load Balancer Outbound Data Processing for Johannesburg (africa-south1) | F045-FE0A-3BFC | February 29, 2024 |
| Pub/Sub Lite (3A1B-66C4-2BAE) | Pub/Sub Lite Network Internet Data Transfer Out Africa to Africa | 5797-C34C-E9D3 | February 29, 2024 |
| Vertex AI (C7E2-9256-1C43) | Feature Store Bigtable online serving node for africa-south1 | 3C61-11BF-95D8 | March 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Feature Store data processing node in africa-south1 | 4CD1-F340-5B97 | March 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Feature Store optimized online serving node in africa-south1 | C815-958F-33BB | March 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Feature Store storage for Bigtable online serving in africa-south1 | 56BD-B651-EFBD | March 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction E2 Predefined Instance Core running in Johannesburg | A520-F93F-1D04 | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction E2 Predefined Instance Ram running in Johannesburg | 7B3A-CCB8-2588 | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction N2 Predefined Instance Core running in Johannesburg | 8C4B-973A-0064 | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction N2 Predefined Instance Ram running in Johannesburg | 743E-14E7-7176 | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction N2D Predefined Instance Core running in Johannesburg | A5A3-2278-A05F | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Online/Batch Prediction N2D Predefined Instance Ram running in Johannesburg | 131C-E89A-D691 | April 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on E2 Instance Core running in Johannesburg | 5B56-3016-EC49 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on E2 Instance RAM in Johannesburg | 93E0-57F2-B078 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on N2 Instance Core running in Johannesburg | 40C1-8201-11C8 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on N2 Instance Ram running in Johannesburg | C778-9E7F-3BA7 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on SSD backed PD Capacity in Johannesburg | 6110-7384-EE99 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Ray on Vertex/Pipelines on Storage PD Capacity in Johannesburg | 28FF-73A7-21FB | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on E2 Instance Core in Johannesburg | 106A-CDB8-677B | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on E2 Instance RAM in Johannesburg | 9333-8744-0335 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on N2 Instance Core in Johannesburg | D547-1ABD-D5F6 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on N2 Instance RAM in Johannesburg | 6F87-CEE5-9464 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on SSD backed PD Capacity in Johannesburg | 3526-556F-8587 | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines Management fee on Storage PD Capacity in Johannesburg | DF6A-C672-6EDA | September 26, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on E2 Instance Core in Johannesburg | 3E58-73CC-54E9 | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on E2 Instance RAM in Johannesburg | 80DC-CA7E-C17D | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on N2 Instance Core in Johannesburg | 9170-2238-2CED | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on N2 Instance RAM in Johannesburg | 4CA5-4B1D-397B | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on SSD backed PD Capacity in Johannesburg | 74A6-C9D1-F51E | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex AI: Training/Pipelines on Storage PD Capacity in Johannesburg | AA73-9E5B-5CC5 | April 18, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab CPU for GCE usage - A2 Instance Cores in africa-south1 | 5AC1-15AB-6B02 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab CPU for GCE usage - E2 Instance Cores in africa-south1 | 5759-2DD2-5335 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab CPU for GCE usage - G2 Instance Cores in africa-south1 | 4190-337F-5285 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab CPU for GCE usage - N1 Instance Cores in africa-south1 | F503-3034-CA5B | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab CPU for GCE usage - N2 Instance Cores in africa-south1 | A894-2E6B-0DA4 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - A100(40 GB) in africa-south1 | 68B7-E8D7-2FA2 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - A100(80 GB) in africa-south1 | F2E1-9A7D-7F22 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - L4 in africa-south1 | 2CF8-ED2A-5811 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - P100 in africa-south1 | 7F22-DABC-D3D7 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - P4 in africa-south1 | 9B7A-A540-87D6 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - T4 in africa-south1 | A4FF-498C-6896 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab GPU for GCE usage - V100 in africa-south1 | AEEC-A291-955C | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab RAM for GCE usage - A2 Instance Ram in africa-south1 | 0CC4-A69B-1046 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab RAM for GCE usage - E2 Instance Ram in africa-south1 | 8BE0-B23E-D626 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab RAM for GCE usage - G2 Instance Ram in africa-south1 | 4904-BEF9-0036 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab RAM for GCE usage - N1 Instance Ram in africa-south1 | A48E-34AF-57E5 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab RAM for GCE usage - N2 Instance Ram in africa-south1 | 875C-F2EE-C055 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab Storage for GCE usage - Balanced Persistent Disk in africa-south1 | D490-C5AD-E995 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab Storage for GCE usage - Extreme Persistent Disk in africa-south1 | 5B7E-9BC9-D59D | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab Storage for GCE usage - Hyperdisk Extreme Persistent Disk in africa-south1 | 3EF5-3CF1-9B96 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab Storage for GCE usage - SSD Persistent Disk in africa-south1 | 2D30-1E3C-CB87 | March 28, 2024 |
| Vertex AI (C7E2-9256-1C43) | Vertex Colab Storage for GCE usage - Standard Persistent Disk in africa-south1 | F4A1-7937-4239 | March 28, 2024 |