SKU Groups - TPU v5p (1 Year CUD)

This page lists SKU Groups that may be referenced in contracts and Cost Management. For more information, contact sales.

TPU v5p (1 Year CUD)

Service NameSKU NameSKU IDDate Added
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Americas for 1 YearA914-791A-D351February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Belgium for 1 Year9881-9A27-3C45February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Berlin for 1 Year686C-FF3B-B9A2February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Columbus for 1 Year0398-E744-D5DDFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Dallas for 1 Year0B6F-B626-A439February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Dammam for 1 Year8D77-919C-705DFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Delhi for 1 Year2C9E-AD97-E46EFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Finland for 1 Year1BF4-3481-44A4February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Frankfurt for 1 Year8669-6884-8F13February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Hong Kong for 1 Year3F23-A930-9FC8February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Israel for 1 Year3D30-C03A-FFBFFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Jakarta for 1 YearF036-0C3A-3231February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Johannesburg for 1 Year879D-965E-CDD1February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Las Vegas for 1 Year3960-5957-1608February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in London for 1 Year9A82-FE2E-B5FBFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Los Angeles for 1 Year51DB-01A5-0584February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Madrid for 1 Year5FA4-09E3-4F0CFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Melbourne for 1 YearA271-0A69-7843February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Milan for 1 Year32BE-9E70-042EFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Montreal for 1 YearAFEE-CA74-7851February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Mumbai for 1 Year0957-1C48-7C8DFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Netherlands for 1 YearF1B5-CDA5-2998February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Osaka for 1 YearE64F-0E80-F5FCFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Paris for 1 Year9093-274D-17E7February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Phoenix for 1 YearA511-1D6B-86B2February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Salt Lake City for 1 Year0245-8627-990AFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Santiago for 1 Year71BB-EB86-9670February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Sao Paulo for 1 Year2069-AFF8-E9BCFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Seoul for 1 Year5F24-70EC-69CDFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Singapore for 1 YearD797-85DF-9A53February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Stockholm for 1 Year840E-6FCE-6707May 24, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Sydney for 1 Year75A9-E210-525DFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Taiwan for 1 YearFB7C-409E-B155February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Tokyo for 1 Year02E3-5DA9-03A1February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Toronto for 1 Year8FDC-EA98-BF0CFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Virginia for 1 YearA167-5892-9726February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Warsaw for 1 YearCA70-7007-5A18February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Zurich for 1 Year39E5-7B5A-E235February 28, 2024