TPU v5p (1 Year CUD)
Service Name | SKU Name | SKU ID | Date Added |
---|---|---|---|
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Americas for 1 Year | A914-791A-D351 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Belgium for 1 Year | 9881-9A27-3C45 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Berlin for 1 Year | 686C-FF3B-B9A2 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Columbus for 1 Year | 0398-E744-D5DD | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Dallas for 1 Year | 0B6F-B626-A439 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Dammam for 1 Year | 8D77-919C-705D | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Delhi for 1 Year | 2C9E-AD97-E46E | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Finland for 1 Year | 1BF4-3481-44A4 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Frankfurt for 1 Year | 8669-6884-8F13 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Hong Kong for 1 Year | 3F23-A930-9FC8 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Israel for 1 Year | 3D30-C03A-FFBF | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Jakarta for 1 Year | F036-0C3A-3231 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Johannesburg for 1 Year | 879D-965E-CDD1 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Las Vegas for 1 Year | 3960-5957-1608 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in London for 1 Year | 9A82-FE2E-B5FB | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Los Angeles for 1 Year | 51DB-01A5-0584 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Madrid for 1 Year | 5FA4-09E3-4F0C | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Melbourne for 1 Year | A271-0A69-7843 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Milan for 1 Year | 32BE-9E70-042E | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Montreal for 1 Year | AFEE-CA74-7851 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Mumbai for 1 Year | 0957-1C48-7C8D | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Netherlands for 1 Year | F1B5-CDA5-2998 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Osaka for 1 Year | E64F-0E80-F5FC | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Paris for 1 Year | 9093-274D-17E7 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Phoenix for 1 Year | A511-1D6B-86B2 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Salt Lake City for 1 Year | 0245-8627-990A | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Santiago for 1 Year | 71BB-EB86-9670 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Sao Paulo for 1 Year | 2069-AFF8-E9BC | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Seoul for 1 Year | 5F24-70EC-69CD | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Singapore for 1 Year | D797-85DF-9A53 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Sydney for 1 Year | 75A9-E210-525D | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Taiwan for 1 Year | FB7C-409E-B155 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Tokyo for 1 Year | 02E3-5DA9-03A1 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Toronto for 1 Year | 8FDC-EA98-BF0C | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Virginia for 1 Year | A167-5892-9726 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Warsaw for 1 Year | CA70-7007-5A18 | February 28, 2024 |
Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Zurich for 1 Year | 39E5-7B5A-E235 | February 28, 2024 |