SKU Groups - TPU v5p (3 Year CUD)

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

TPU v5p (3 Year CUD)

Service NameSKU NameSKU IDDate Added
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Americas for 3 Years8B69-A3B8-7361February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Belgium for 3 YearsCE1F-36CF-CCBCFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Berlin for 3 YearsF781-29AB-B175February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Columbus for 3 Years1478-CF20-B577February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Dallas for 3 Years0CB0-4673-1E49February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Dammam for 3 YearsFE93-136A-1EC8February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Delhi for 3 Years4DCD-6F14-EC60February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Finland for 3 Years3563-45EC-A0F8February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Frankfurt for 3 Years381E-A6FA-A608February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Hong Kong for 3 Years8294-8CFC-571EFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Israel for 3 Years95D0-D151-2BDEFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Jakarta for 3 Years045C-DFFC-E33AFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Johannesburg for 3 Years6E0B-8117-94F5February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Las Vegas for 3 YearsE128-F72C-CA21February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in London for 3 Years8B32-2113-E2A8February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Los Angeles for 3 YearsC729-4F04-D568February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Madrid for 3 Years7D6C-0D5B-D399February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Melbourne for 3 Years30DA-4FBB-0302February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Milan for 3 YearsAFF0-CBA5-0E24February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Montreal for 3 Years7F14-000F-B319February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Mumbai for 3 YearsB755-80BE-3E3FFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Netherlands for 3 Years0115-21ED-7F03February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Osaka for 3 Years3F63-743F-E15CFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Paris for 3 Years960B-6180-8A0CFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Phoenix for 3 Years3635-B8A7-58D4February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Salt Lake City for 3 YearsDB6C-8EAE-C207February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Santiago for 3 Years878C-20F6-1946February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Sao Paulo for 3 YearsCC6B-FFBE-E2D6February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Seoul for 3 YearsBC33-92BA-41EBFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Singapore for 3 YearsC68A-254C-B92AFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Stockholm for 3 Years60FA-DA1A-44F6May 24, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Sydney for 3 YearsAFB0-B951-6087February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Taiwan for 3 YearsA7D8-F69D-B9D6February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Tokyo for 3 Years9B93-F3FE-5B3FFebruary 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Toronto for 3 Years645D-F0D5-FDD2February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Virginia for 3 Years7333-3E53-2E18February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Warsaw for 3 Years5F37-3C2D-47B8February 28, 2024
Compute Engine
(6F81-5844-456A)
Commitment v1: TpuV5p running in Zurich for 3 YearsF7EA-CF9D-212BFebruary 28, 2024