TPU v5p (3 Year CUD)
| Service Name | SKU Name | SKU ID | Date Added |
|---|---|---|---|
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Americas for 3 Years | 8B69-A3B8-7361 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Belgium for 3 Years | CE1F-36CF-CCBC | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Berlin for 3 Years | F781-29AB-B175 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Columbus for 3 Years | 1478-CF20-B577 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Dallas for 3 Years | 0CB0-4673-1E49 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Dammam for 3 Years | FE93-136A-1EC8 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Delhi for 3 Years | 4DCD-6F14-EC60 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Finland for 3 Years | 3563-45EC-A0F8 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Frankfurt for 3 Years | 381E-A6FA-A608 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Hong Kong for 3 Years | 8294-8CFC-571E | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Israel for 3 Years | 95D0-D151-2BDE | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Jakarta for 3 Years | 045C-DFFC-E33A | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Johannesburg for 3 Years | 6E0B-8117-94F5 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Las Vegas for 3 Years | E128-F72C-CA21 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in London for 3 Years | 8B32-2113-E2A8 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Los Angeles for 3 Years | C729-4F04-D568 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Madrid for 3 Years | 7D6C-0D5B-D399 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Melbourne for 3 Years | 30DA-4FBB-0302 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Milan for 3 Years | AFF0-CBA5-0E24 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Montreal for 3 Years | 7F14-000F-B319 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Mumbai for 3 Years | B755-80BE-3E3F | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Netherlands for 3 Years | 0115-21ED-7F03 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Osaka for 3 Years | 3F63-743F-E15C | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Paris for 3 Years | 960B-6180-8A0C | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Phoenix for 3 Years | 3635-B8A7-58D4 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Salt Lake City for 3 Years | DB6C-8EAE-C207 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Santiago for 3 Years | 878C-20F6-1946 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Sao Paulo for 3 Years | CC6B-FFBE-E2D6 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Seoul for 3 Years | BC33-92BA-41EB | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Singapore for 3 Years | C68A-254C-B92A | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Stockholm for 3 Years | 60FA-DA1A-44F6 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Sydney for 3 Years | AFB0-B951-6087 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Taiwan for 3 Years | A7D8-F69D-B9D6 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Tokyo for 3 Years | 9B93-F3FE-5B3F | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Toronto for 3 Years | 645D-F0D5-FDD2 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Virginia for 3 Years | 7333-3E53-2E18 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Warsaw for 3 Years | 5F37-3C2D-47B8 | February 28, 2024 |
| Compute Engine (6F81-5844-456A) | Commitment v1: TpuV5p running in Zurich for 3 Years | F7EA-CF9D-212B | February 28, 2024 |