SKU Groups - G4 On Demand VMs

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

G4 On Demand VMs

Service NameSKU NameSKU IDDate Added
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in AlabamaFC7B-BA2E-8231February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Belgium67AA-87CA-3761February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Columbus45F9-DAE7-D44DFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in DallasD704-DD8E-56BFFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Dammam7CD1-8047-E9A9February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Delhi6F1B-B1C7-C485February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in FinlandD589-B56F-1E8CFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Frankfurt261A-BF9C-1561February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in IowaD5C5-C5F4-086CFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in JakartaC030-62B4-198EFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Las Vegas1385-2E8F-DE64February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in London8E6E-FF52-2928February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in MelbourneCB75-9B93-48C8February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Milan8BF9-21DC-D0D4February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Mumbai9EB8-9D0B-BC9EFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in NetherlandsAEE4-7ECE-5D91February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Northern Virginia4A48-8159-BA2CFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Oregon6499-1B74-5770February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Phoenix85F8-DDA3-AAC5February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Salt Lake City29CC-F82F-34ABFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in SeoulFBE2-5540-4F88February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in Singapore58D9-A387-D6B0February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in South Carolina195C-8FB9-4248February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in TaiwanFC72-3535-0B68February 24, 2026
Compute Engine
(6F81-5844-456A)
1/8 vGPU no lssd running in TokyoE075-7114-FE0BFebruary 24, 2026
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Belgium0870-5232-99BDOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in ColumbusACFA-8172-4B04October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Dallas98EF-6B39-E60BOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Delhi337C-7BB5-7F6DOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in FinlandF8DD-C231-67ACOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Iowa1DAC-C1C9-8A81October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in JakartaED2F-C976-9ED6October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Las Vegas0578-3EA1-184EOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in London1DFB-C964-D95DOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Milan8641-7495-283BOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Netherlands7261-95A7-F7FCOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Northern Virginia4D92-8C86-B69EOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in OregonA36E-7315-8862October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in PhoenixB0C1-244E-2AFBOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in Salt Lake CityEDC1-4A3E-6601October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in SingaporeAEE8-4D40-ED10October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Core running in South Carolina5A40-E626-9954October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Belgium1CB9-1F17-5393November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in ColumbusF3F0-7BCE-1298November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Dallas0619-AD5F-448ANovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Delhi5109-EBB0-2B1BNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in FinlandC215-BBE7-BA7FNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Iowa877C-189E-8BE3November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in JakartaA6CA-AAD0-1ED8November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Las Vegas81B6-2963-41DFNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in LondonB3C1-B360-801ANovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Milan20DC-935A-B95CNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Netherlands0B99-9855-3C38November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Northern Virginia907D-1EAF-7EDFNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in OregonFC94-13C6-4468November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Phoenix9A3B-A5F6-DC94November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Salt Lake City9D87-4842-23ECNovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in Singapore6D84-9337-453ANovember 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Local SSD running in South CarolinaC0E8-6878-2613November 16, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Belgium21DE-218E-E709October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Columbus2C76-185C-DBD2October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in DallasB896-28C3-12C0October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Delhi21E9-56C6-6DDDOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Finland0D6E-8CF3-66FBOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Iowa916E-67E0-A9F4October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Jakarta4A4B-A287-2A88October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Las Vegas84A0-258E-EA3AOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in London0511-2F4A-0396October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Milan3B58-BE24-2032October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in NetherlandsCE3A-E20F-F4A0October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Northern VirginiaF145-30B5-28B4October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in OregonC566-5B7E-28AAOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Phoenix5C8B-5F61-7B1DOctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Salt Lake City901C-8C9E-F33COctober 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in Singapore3759-9C91-CB30October 27, 2025
Compute Engine
(6F81-5844-456A)
G4 Instance Ram running in South CarolinaF566-E903-4FF9October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Belgium9F2A-B404-0849October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Columbus1CFC-C57A-B266October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Dallas605D-B0EB-E2B1October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Delhi64BD-A5BE-2CF5October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Finland6C31-6F29-0EE6October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in IowaB25E-068A-EFB2October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Jakarta02D0-3C0A-B826October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Las Vegas6784-B6D2-DD04October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in LondonD477-2A23-0FC5October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Milan049A-C48A-D49AOctober 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Netherlands8018-1FFE-DAB2October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Northern Virginia7026-FF0B-CB07October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Oregon73C5-0031-0BF3October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in PhoenixCDD1-5864-C14COctober 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Salt Lake CityF142-756B-2AABOctober 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in Singapore2ED4-348D-F042October 27, 2025
Compute Engine
(6F81-5844-456A)
RTX 6000 96GB running in South Carolina48A3-47D3-D4F7October 27, 2025