On-Demand Compute
| Service Name | SKU Name | SKU ID | Date Added |
|---|---|---|---|
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in APAC | 72B5-DF54-F398 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Americas | 2922-40C5-B19F | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Berlin | 110A-0409-5061 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Columbus | 0514-BECA-FCF2 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Dallas | 0C8C-D2A1-5295 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Dammam | 350C-352C-3298 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Delhi | E2E6-6EE7-8C54 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in EMEA | 833D-F28B-BCD2 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Finland | 7165-2044-C3F4 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Frankfurt | 7133-941A-A06A | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Hong Kong | 418C-EF96-E65D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Israel | 988D-5EDA-ABE7 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Jakarta | 4909-A7D2-BC75 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Japan | 1B27-8A7C-73FB | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Johannesburg | 73DD-2955-6A0A | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Las Vegas | D6D3-2DF1-E401 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in London | 9998-6CED-8C7E | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Los Angeles | 8B1C-33B9-6EF2 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Madrid | 699C-0724-50D5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Melbourne | 50DF-9489-0F9A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Milan | 3EBC-11D3-A174 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Montreal | EFF0-014D-FACE | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Mumbai | 4388-EE08-6E33 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Netherlands | 896E-DB80-1131 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Osaka | D802-9CCA-7F20 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Paris | E1BA-02E5-EFB0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Phoenix | B388-92CE-A7BF | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Salt Lake City | E782-1842-A331 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Santiago | 32CB-4D0F-9796 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Sao Paulo | D3A6-F1A0-30F0 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Seoul | 15D3-067D-B0A0 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Singapore | 10F0-EE60-26C7 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Stockholm | 838F-590D-9B85 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Sydney | 0CC0-AED1-001C | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Toronto | 1CD3-9D89-855A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Virginia | 5EF9-7776-45FD | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Warsaw | 25FD-871F-A197 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Core running in Zurich | 330C-9690-BF04 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in APAC | EA6C-8D56-8BC9 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Americas | 2390-DCAF-DA38 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Berlin | B04E-B7CF-D95C | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Columbus | 04E2-007C-D4D7 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Dallas | DDB1-97ED-78EA | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Dammam | DE95-C622-3022 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Delhi | EA9D-C75E-1BED | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in EMEA | 933C-9C81-5D7F | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Finland | CD9D-B084-85DC | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Frankfurt | 116F-A071-C2FA | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Hong Kong | 9A97-8B61-24A5 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Israel | 9F42-2A73-F0B1 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Jakarta | 32ED-2577-54DB | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Japan | CF0E-5F75-C747 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Johannesburg | 711F-53E5-6E97 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Las Vegas | 5696-2B41-DD39 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in London | E269-F1C0-239D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Los Angeles | 3926-DD4A-F51E | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Madrid | BD1B-CDF6-3B81 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Melbourne | 9D9B-6FCD-5F14 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Milan | 87AD-A144-CCF1 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Montreal | B959-591F-5291 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Mumbai | 4065-7D70-B4BF | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Netherlands | A78A-A063-7D5A | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Osaka | 410A-28B4-7E79 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Paris | 8879-6072-AAD9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Phoenix | 8C31-34D1-13D5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Salt Lake City | 0C2B-9F28-53BD | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Santiago | 1503-840F-B5AF | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Sao Paulo | 6612-DF52-B8E6 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Seoul | 4110-E0B0-3947 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Singapore | 03D0-B47F-1938 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Stockholm | C632-87F2-6C52 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Sydney | 42CE-1AAC-A1C2 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Toronto | AFE8-6059-2A98 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Virginia | A592-E65A-C71A | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Warsaw | 0F0B-B8A6-61FD | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | A2 Instance Ram running in Zurich | 7559-0926-4CF0 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity | 6AE1-525F-8B80 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Alabama | C6EF-9E23-4A16 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Berlin | C99E-D411-4C3C | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Columbus | B5F4-F738-1AA4 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Dallas | 45C5-3E36-ED09 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Dammam | 2355-97B9-3C07 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Delhi | E709-23E2-DCD9 | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Finland | ABEC-4750-B9EF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Frankfurt | B1B5-0BAA-CB31 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Hong Kong | 6CB7-B05F-97AD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Israel | 6250-56B4-000E | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Jakarta | 7CD6-D519-82F7 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Japan | 6D8C-DF09-314D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Johannesburg | 104E-81CB-48E3 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Las Vegas | 4701-2C6F-375F | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in London | D7FE-969C-E339 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Los Angeles | DF86-0465-7120 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Madrid | 66F2-6BE3-1229 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Melbourne | 256B-1E8B-9398 | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Mexico | 0824-EC08-36D2 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Milan | 5D09-05FD-782D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Montreal | 5785-6130-358E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Mumbai | C24C-88D9-75ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Netherlands | 5CFD-16B2-4F41 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Osaka | 2458-CD97-92B1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Paris | D09D-F329-003F | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Phoenix | 9759-0570-C17A | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Salt Lake City | C5EF-0CEF-175D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Santiago | 8CC1-0077-DE99 | September 9, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Sao Paulo | 6F9F-D10A-6613 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Seoul | 5666-EFB4-5C79 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Singapore | 16D2-FC49-A127 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Stockholm | 4581-3E00-63BC | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Sydney | B046-9075-75BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Toronto | 3A7C-54DD-2577 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Virginia | 7D52-6D58-14FF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Warsaw | 7F37-4B04-C4BF | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Balanced PD Capacity in Zurich | CAF4-ADE9-58BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in APAC | 0D7F-A435-7137 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Americas | 5E86-72F2-5688 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Berlin | 9C9F-9D5A-51DD | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Columbus | E5C4-B0A1-3C53 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Dallas | E3E7-FD8A-45F5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Dammam | AC23-1D95-6059 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Delhi | DEED-126A-11E2 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in EMEA | A285-6828-844B | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Finland | 9105-C1D3-C656 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Frankfurt | 2898-B9EC-B5B3 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Hong Kong | 72AE-6ED0-BC0A | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Israel | DDBE-FFEB-7E00 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Jakarta | 6890-D011-C0B9 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Japan | 6F84-E8ED-5693 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Johannesburg | 9364-03D6-8C8C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Las Vegas | AB48-568E-4D8C | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in London | 4EEE-267C-CBD5 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Los Angeles | 0CB5-FB1A-2C2A | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Madrid | B694-F6C6-4A34 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Melbourne | 2A15-2E0C-DD15 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Milan | 6058-A759-D852 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Montreal | A475-B8A8-FFD8 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Mumbai | 406A-AA4B-1013 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Netherlands | 55B4-3310-52AB | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Osaka | 3D5E-7A24-1316 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Paris | 6F6A-DEAC-EC39 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Phoenix | EF17-7B8D-6B0E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Salt Lake City | 9BD1-9DF4-DEBB | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Santiago | DA89-6E14-CEA1 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Sao Paulo | A530-3230-5BFF | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Seoul | 8E7C-9BC6-1C3E | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Singapore | A8BB-FA67-F9D8 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Stockholm | B915-6FC2-96A3 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Sydney | 9566-60C0-E2AD | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Toronto | 7D62-DC5A-2CFE | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Virginia | D276-7CD3-D61E | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Warsaw | AB94-9F50-2B3C | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Core running in Zurich | 07BE-F49E-7CA0 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in APAC | F5C9-B05F-9CE6 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Americas | C79B-C925-A9B9 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Berlin | 2D83-03C2-08FD | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Columbus | AA97-2E68-29AD | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Dallas | 4143-72A6-4D0D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Dammam | 2CC5-F3CB-DDA4 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Delhi | 929E-B2DA-110A | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in EMEA | 440B-D83B-3002 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Finland | 8F75-88CB-2114 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Frankfurt | 40DE-6073-970E | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Hong Kong | 7D01-D6C8-232D | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Israel | 9787-23D2-3EA1 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Jakarta | 2D8C-67E1-8A23 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Japan | 8665-882C-752D | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Johannesburg | B59E-3A0E-766B | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Las Vegas | 5251-53C9-1BE7 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in London | B05B-D678-A6E4 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Los Angeles | 64AA-5374-1604 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Madrid | E7A0-3D1C-A1DD | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Melbourne | 8692-6A2A-805E | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Milan | CA1C-D795-AC79 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Montreal | 463B-471C-6C73 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Mumbai | BD36-0399-11EF | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Netherlands | AC07-0CAE-D814 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Osaka | 2991-6710-4CAF | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Paris | B523-3FC4-04D9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Phoenix | E671-8BC3-92A9 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Salt Lake City | 93E0-6C5C-3A1B | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Santiago | 79B3-DAF6-7537 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Sao Paulo | A9BE-9B87-DB83 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Seoul | 9FCB-D94C-DDFF | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Singapore | 6E53-DF71-F575 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Stockholm | 3272-DBBA-38DA | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Sydney | 2FC9-4C2C-BB3C | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Toronto | 7D85-4666-E9F7 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Virginia | 23B5-B451-5151 | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Warsaw | 4FA8-5F47-948C | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | C2D AMD Instance Ram running in Zurich | 73B7-DE4F-DDFF | May 16, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in APAC | 0431-1BCC-0DDB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Americas | 0F79-08F1-0D8A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Columbus | 81B5-0ABE-0794 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Delhi | 2D2F-5C26-C9E2 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in EMEA | E6D3-3221-80B3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Finland | 5737-D08F-2536 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Frankfurt | 2108-24F6-8A71 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Hong Kong | 65CE-4AE3-C38C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Jakarta | 78DA-97B7-4636 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Japan | 1E2A-8F3B-7752 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Las Vegas | A489-6BFE-F142 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in London | 271A-7F2A-C5C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Los Angeles | 24CA-4FEE-D2D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Melbourne | 2FE9-4DEF-C3E5 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Montreal | FACC-0440-C9FE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Mumbai | 215B-2E7C-E190 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Netherlands | 6753-90C9-DA11 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Osaka | F736-13ED-2488 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Salt Lake City | 8826-59B8-3246 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Santiago | 2B89-23AC-930C | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Sao Paulo | A961-9CB4-C6C2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Seoul | C2BF-525E-B2BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Singapore | BFA6-56C0-FB9C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Sydney | 7927-0B13-F795 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Toronto | 222D-AFB1-F546 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Virginia | A9BF-E313-5815 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Warsaw | DF1E-7668-DC09 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Core running in Zurich | 2B93-9A67-0964 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Berlin | A89D-C6E4-DEB6 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Dallas | 005F-FF3C-58A2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Dammam | B1FA-9857-E6F5 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Israel | 926D-D5F6-C901 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Johannesburg | 225D-93F0-5B57 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Madrid | 81F3-6EFB-5D5D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Milan | 80BF-5305-1799 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Paris | 5519-CBBB-703E | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Phoenix | 82FE-0ED0-A734 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Core running in Stockholm | 39CD-70BB-DF5E | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Berlin | 1E8A-AC0A-FD43 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Dallas | C887-9E05-5DB4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Dammam | 31A9-ADA2-840D | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Israel | 93F7-F37A-BFCF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Johannesburg | E986-53A1-EAA8 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Madrid | CE1E-BD50-3F1F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Mexico | ABBB-A5B5-25D1 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Milan | 35E0-21D4-141B | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Paris | 703F-3C03-0293 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Phoenix | 6EF9-2C0B-7EE7 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute optimized Instance Ram running in Stockholm | 8A30-C97D-7DE3 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in APAC | A2FA-87E4-4955 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Americas | E7E5-0449-5933 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Columbus | 79EF-5FBE-25C8 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Delhi | 5778-D00B-664E | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in EMEA | 72E8-3980-C96D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Finland | BE7B-727C-97BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Frankfurt | 85FB-E63F-9C09 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Hong Kong | B463-9C97-CE40 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Jakarta | 8018-291A-18DA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Japan | 1B15-60C2-6B63 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Las Vegas | 1C54-BD47-F4E3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in London | 0BD6-E233-D705 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Los Angeles | C714-6232-656B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Melbourne | 522B-F7B5-2E7A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Montreal | 7F19-4937-CDCA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Mumbai | F111-FD6B-27B0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Netherlands | 0F6A-F245-7139 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Osaka | D07A-1640-0B76 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Salt Lake City | 1D4E-8988-9C5F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Santiago | 21CC-CA8C-0EC1 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Sao Paulo | 8811-1C6A-4662 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Seoul | 6001-A27E-20E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Singapore | 0A77-34FA-6E87 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Sydney | 65A7-D228-0663 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Toronto | 8D9D-C7F3-E7D7 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Virginia | 93DA-DFF5-ED89 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Warsaw | 0564-D752-EF07 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Compute optimized Ram running in Zurich | C0BD-78A7-3057 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in APAC | 57D2-B7BA-7967 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Americas | 6989-9534-9B06 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Berlin | 154F-E1AB-75D1 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Columbus | 62F2-30A7-0F1D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Dallas | 923E-A872-8A9E | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Dammam | B440-28D6-135C | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Delhi | 5671-B6EC-97AB | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in EMEA | 9426-8C95-6867 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Finland | ACF3-71F6-2825 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Frankfurt | 48F2-3917-C659 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Hong Kong | E1C6-C146-2709 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Israel | C731-33AD-D9FE | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Jakarta | F1C9-E01F-C7E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Japan | 33F9-F00C-3712 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Johannesburg | 09AC-31B4-0AED | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Las Vegas | 9E93-08C7-AE0B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in London | AAC5-5A5B-B655 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Los Angeles | F215-B65C-385A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Madrid | D3CB-FF40-F604 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Melbourne | DC0A-FB25-0A25 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Mexico | 9E89-D277-53E4 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Milan | 793B-948F-5ABB | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Montreal | 4814-D6A2-627D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Mumbai | 8BB4-B8A1-7874 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Netherlands | A8FF-BEA1-3E4B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Osaka | 4A7E-BC7A-196E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Paris | 0DCB-D25A-B36E | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Phoenix | 225A-792E-8B63 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Salt Lake City | 0869-1CB9-F169 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Santiago | FEAF-29EF-33D0 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Sao Paulo | C8FF-EED0-C760 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Seoul | B6B1-4218-1701 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Singapore | DD7D-19D7-CA2A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Stockholm | 1FF7-3446-2D01 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Sydney | FFA6-ACCA-9A35 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Toronto | 57EB-9AB3-5FB7 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Virginia | 4C90-A6E6-22D2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Warsaw | F221-F759-31A7 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Core running in Zurich | E631-42E6-7675 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in APAC | 0101-B684-19CF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Americas | 0121-930D-8661 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Columbus | A5C9-64C3-D68B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Delhi | 730B-DAE4-300B | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in EMEA | A138-A0E1-E597 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Finland | 6BFF-6D02-8D81 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Frankfurt | 6F6A-B2D0-BF85 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Hong Kong | 64A0-E4C3-6E86 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Jakarta | EE57-6CBE-F8D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Japan | 976C-F73E-2F03 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Las Vegas | 5C8D-C4FF-C77A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in London | DC34-5DD8-D560 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Los Angeles | A53E-99E3-0255 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Melbourne | 519F-7BF4-94A6 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Montreal | 01E3-ED50-D786 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Mumbai | 519F-242D-E23F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Netherlands | 5F1F-0405-7231 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Osaka | D22D-1331-9BD5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Salt Lake City | A20A-8D42-7DEB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Santiago | 415F-413D-2767 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Sao Paulo | CFF4-B9D5-1587 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Seoul | C5A7-351A-3776 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Singapore | FC01-6CA0-D3E0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Sydney | 4891-41E0-7BCD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Toronto | AA5C-69E2-48B8 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Virginia | 0BDF-E99E-853E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Warsaw | B6CB-669F-4555 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance RAM running in Zurich | 3436-4113-3F1C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Berlin | 77BD-FE75-8763 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Dallas | 761A-A60E-777D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Dammam | 8F12-C55E-3D5F | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Israel | FB21-9BFF-4D39 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Johannesburg | 6738-0198-0A4D | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Madrid | 5F40-CBC4-E4BD | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Mexico | 56AC-EB1F-9582 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Milan | 196D-5B92-AAC5 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Paris | A622-7629-AAED | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Phoenix | 97DB-05E0-2EC0 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Compute-optimized Sole Tenancy Instance Ram running in Stockholm | 75C8-5298-19A6 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in APAC | 171B-A8E4-FD07 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Americas | 972B-1B48-9D16 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Berlin | A12A-97FF-3194 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Columbus | C332-221D-9FA4 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Dallas | B417-1DFA-ADB4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Dammam | DF3F-5B13-A6E3 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Delhi | C97E-8E35-9B07 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in EMEA | 1EB9-1221-1475 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Finland | B6AB-4AB5-35E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Frankfurt | 4816-A0E6-FF7E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Hong Kong | 914B-3C9E-6C47 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Israel | 3F11-4749-C21C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Jakarta | 1854-0F1D-CA02 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Japan | EAA8-2755-8551 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Johannesburg | 1E20-53DB-3A56 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Las Vegas | 5C68-BA09-A3EF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in London | 3E1C-D283-78BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Los Angeles | 472A-2C0D-17F3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Madrid | 1E16-7C3D-9751 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Melbourne | 22AF-8F49-D846 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Milan | B859-003F-F31E | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Montreal | 5665-F102-CEB4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Mumbai | 2746-CF05-967D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Netherlands | 4E98-EAEF-A131 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Osaka | F91C-7514-9896 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Paris | 939A-CB35-76F9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Phoenix | 502C-8BE9-CB89 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Salt Lake City | B577-8556-86B0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Santiago | 0D37-3240-2695 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Sao Paulo | 611C-42A7-DC0D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Seoul | 1C6A-936B-163B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Singapore | 79C6-8EC6-8D49 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Stockholm | 84AE-80BF-BF76 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Sydney | 4B13-D85C-B34B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Toronto | 73A2-7349-47CC | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Virginia | 10A2-75B9-56F6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Warsaw | AA5C-01E9-C91F | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Extended Instance Ram running in Zurich | 6BB6-7EB4-076B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in APAC | AD5A-163C-B46D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Americas | ACBC-6999-A1C4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Berlin | EBF6-52E6-6B93 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Columbus | 3AF0-0FC8-64D6 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Dallas | CF3C-9726-4283 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Dammam | FF60-E92F-35DB | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Delhi | EA0B-E301-56C5 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in EMEA | 606D-D514-8E64 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Finland | 68E9-E852-F624 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Frankfurt | 47BE-44D0-C86F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Hong Kong | 4F6F-42CB-DEB6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Israel | D962-9ABB-6389 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Jakarta | F296-7177-913D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Japan | DEA0-DBFB-BAB4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Johannesburg | 60F1-9944-4B48 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Las Vegas | 829C-1D7A-6108 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in London | 201A-CE43-C161 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Los Angeles | 2037-B859-1728 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Madrid | A7CE-4D25-DE95 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Melbourne | 5BB6-9832-5811 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Mexico | 70AA-8520-5DCD | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Milan | E00B-CBB3-1864 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Montreal | 78F8-6D1D-AA67 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Mumbai | 9544-CFBE-3F3F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Netherlands | F052-0029-BECD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Osaka | E4B1-A889-8192 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Paris | DE43-21F1-A4D0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Phoenix | D752-9963-43D0 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Salt Lake City | 6F37-7D45-DD1E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Santiago | C182-0C7C-8D2E | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Sao Paulo | E4B6-CD20-6438 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Seoul | 00F6-BFEA-8A67 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Singapore | 0A28-6329-2B56 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Stockholm | 17D0-058C-A136 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Sydney | B560-AF92-C8D2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Toronto | E366-0409-790A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Virginia | 5B11-C3DF-56CB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Warsaw | 76F7-C3FC-E954 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Core running in Zurich | 6301-E865-C5F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in APAC | 2C62-87C2-6676 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Americas | 51E2-59BD-7A6E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Berlin | 412A-562C-ABD8 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Columbus | BA22-6F9D-E49E | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Dallas | 276E-569E-A006 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Dammam | 0177-6401-4E6A | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Delhi | 17BF-5750-DD75 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in EMEA | 0F35-41DB-4950 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Finland | 4C2C-416E-C448 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Frankfurt | 6971-C36E-2B52 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Hong Kong | D93C-AF72-8A40 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Israel | B741-8DC3-76DF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Jakarta | 1F22-A0B8-F505 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Japan | 84B7-7FE3-1329 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Johannesburg | EE14-97CB-4205 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Las Vegas | 4CDD-4E82-7B74 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in London | 7B74-5AE0-3F99 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Los Angeles | B371-4493-0816 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Madrid | 725E-1E36-D64B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Melbourne | 595E-31A4-927E | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Mexico | FA12-DB43-7C2B | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Milan | 6763-2A9A-5BB4 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Montreal | EBD0-6FAD-1A64 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Mumbai | 1FD0-7EA0-91ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Netherlands | 874F-A8D5-0916 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Osaka | 50C6-870C-5C47 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Paris | D8A3-D708-2866 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Phoenix | 1777-C5BD-B630 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Salt Lake City | 48D5-743F-47DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Santiago | 34AF-2333-9C9B | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Sao Paulo | A0B9-8027-D832 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Seoul | 0C00-D1BB-1424 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Singapore | 7A71-9CF7-E88F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Stockholm | 6A49-C4F6-97F9 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Sydney | 190B-1F63-1A57 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Toronto | EF99-61F6-F5D6 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Virginia | 81CA-E30A-62DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Warsaw | EE8C-8C3B-96EE | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Custom Instance Ram running in Zurich | 4D06-A8A0-31AB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in APAC | F1F0-D469-8A46 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Americas | 61C6-6F89-DCF4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Berlin | 5A42-DED0-260E | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Columbus | EB78-61A0-4A07 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Dallas | A17D-9B4B-3EA8 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Dammam | 6780-8A5C-2BBE | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Delhi | E4A0-2D5F-084A | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in EMEA | 41D8-1BCA-04D7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Finland | 1535-9220-60D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Frankfurt | E075-1B11-D9CC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Hong Kong | 1F19-67C7-6259 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Israel | B8A5-7015-C90D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Jakarta | 3D91-3C71-3551 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Japan | 8F43-1E25-3209 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Johannesburg | 868F-5971-152F | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Las Vegas | 6517-7D1E-8E0F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in London | AB81-BB10-23C3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Los Angeles | 383D-13D7-41BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Madrid | EC8E-058C-B204 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Melbourne | A0B4-7640-BD70 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Mexico | 110E-0063-42CF | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Milan | 8110-905B-B25C | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Montreal | 99B7-0215-987F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Mumbai | 55F6-6BA6-1CC5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Netherlands | 9495-1F5E-995B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Osaka | F723-4D34-9E07 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Paris | B619-0511-D5AC | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Phoenix | 1A07-B76C-20C3 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Salt Lake City | DF99-3D89-DC6E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Santiago | 04BA-94C0-B61C | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Sao Paulo | B583-9669-C300 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Seoul | F10F-0364-8D62 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Singapore | 3619-8579-8AA5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Stockholm | 0C2C-DE2C-3115 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Sydney | 9444-ED37-A0F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Toronto | 7602-2494-12D8 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Virginia | DBE9-C639-5D42 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Warsaw | 0FBC-88AA-1326 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Core running in Zurich | 38D9-0D65-ED0E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in APAC | 8CA7-5B88-D299 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Americas | 8D24-CB74-5E70 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Berlin | 4FC9-329E-DD06 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Columbus | 3B3C-B11D-AB55 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Dallas | 0FF2-D7FF-45B9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Dammam | 17FF-7417-13CB | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Delhi | 9B29-4E63-CD5C | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in EMEA | ECD0-014C-69E6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Finland | A96C-E3F3-1FEE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Frankfurt | 779C-C26D-9379 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Hong Kong | 2EC1-279F-00CB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Israel | 7969-4454-120B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Jakarta | 5D50-95DC-DC58 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Japan | BEDB-6B58-4D4C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Johannesburg | 855D-C33E-F06B | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Las Vegas | B2DF-94BA-50F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in London | C4A9-B857-9C7C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Los Angeles | 0217-3F66-471E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Madrid | 092E-6F3E-B850 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Melbourne | D387-00F2-8856 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Mexico | 61EE-7DA8-7F5E | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Milan | 4EFC-CD18-32A0 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Montreal | 9291-3AA0-B0D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Mumbai | 3387-C0E5-71C8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Netherlands | B1BC-108E-2AD9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Osaka | 295C-5708-4C87 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Paris | 973F-2C7F-C4AC | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Phoenix | FFC9-CE82-CEC5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Salt Lake City | A998-D079-F3B6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Santiago | 7F2A-6FB4-3F1E | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Sao Paulo | 1BC8-F7A8-91B0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Seoul | B5E6-7318-DBF9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Singapore | 7F45-FC8B-2F18 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Stockholm | 2EF7-1097-BF7A | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Sydney | 7B6F-50ED-226C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Toronto | 4523-DE98-E801 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Virginia | BFAB-B8CA-60A2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Warsaw | DE0F-A915-3853 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Custom Instance Ram running in Zurich | 0CCF-5CF6-E756 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in APAC | 92C8-7C92-6AEF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Americas | CF4E-A0C7-E3BF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Berlin | CB05-9728-E731 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Columbus | 2B10-8ED1-31C6 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Dallas | 066E-621A-A1F0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Dammam | 8179-70FE-C2F1 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Delhi | 210D-FDFA-448C | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in EMEA | 9FE0-8F60-A9F0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Finland | 0981-D144-B18E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Frankfurt | C921-088E-792A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Hong Kong | 4111-7FF1-D50A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Israel | 41F4-F6BE-4AF2 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Jakarta | 621C-41D1-4D05 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Japan | EAED-8A05-843B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Johannesburg | DC64-21B2-0622 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Las Vegas | A084-A7CD-D375 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in London | 0F2A-2FA8-3F6A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Los Angeles | 00FD-B743-831B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Madrid | A01C-8201-12AB | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Melbourne | 3871-2725-BC3D | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Mexico | 943D-1CC9-B70E | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Milan | 20B9-2A8D-4BFA | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Montreal | F362-BA10-04D7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Mumbai | DFC1-04D4-B4A1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Netherlands | 012A-5DBB-1352 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Osaka | A126-1AD8-408B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Paris | 0034-652F-8BC9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Phoenix | D8BD-67EB-48A8 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Salt Lake City | 4722-1DF4-2BB8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Santiago | ABB2-1186-100F | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Sao Paulo | 0442-C445-D66A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Seoul | 9304-94C4-2117 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Singapore | 7102-B9AA-2ACF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Stockholm | AFD3-EF83-44EC | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Sydney | 9819-4AB8-1A87 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Toronto | FD61-2026-F53C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Virginia | D5C5-E209-22D3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Warsaw | 955B-B00E-ED15 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Core running in Zurich | CCEF-2733-ADEB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in APAC | FD4D-A383-8DAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Americas | F449-33EC-A5EF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Berlin | 4126-F537-64DC | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Columbus | 5BEB-8229-1894 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Dallas | 45F6-3C6D-3FA6 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Dammam | 8E93-7978-344C | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Delhi | 0B33-C7D0-C5A9 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in EMEA | F268-6CE7-AC16 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Finland | 779E-BED5-F31F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Frankfurt | 7D80-F9E4-6A44 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Hong Kong | 8A68-3C47-7367 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Israel | 9876-7A20-67F0 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Jakarta | 2526-CC04-D642 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Japan | CB4B-B875-93B4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Johannesburg | 545C-0B0B-55EE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Las Vegas | 060E-C97B-2CC6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in London | 5D70-7762-2DE7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Los Angeles | 7785-EEEA-EFBC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Madrid | EDF4-1ECA-4BD7 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Melbourne | 4B8E-50FF-C280 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Mexico | 3BAC-F037-23C4 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Milan | 98C4-AD9B-3F32 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Montreal | 699E-FF84-4093 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Mumbai | 90AB-A7A8-F873 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Netherlands | D9EA-4FF0-E394 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Osaka | A5A3-A6E0-AEA8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Paris | 6AE0-5081-89AF | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Phoenix | 764E-AF79-0ABE | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Salt Lake City | 329A-453B-3410 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Santiago | 9D64-D4B3-E5D6 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Sao Paulo | C3E6-8086-831A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Seoul | D715-4E57-BAFB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Singapore | E277-7DC2-2C7D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Stockholm | 123D-01A4-AFB7 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Sydney | F9E1-E6EF-86F3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Toronto | A340-8EB8-CC38 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Virginia | 6D24-3682-D284 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Warsaw | 56D3-3D40-B0F6 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | E2 Instance Ram running in Zurich | 9C82-E173-62D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity | 165B-942F-F345 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Alabama | E89B-6DF3-B8D2 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Berlin | A78F-D4B3-EEB6 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Columbus | 8D52-248B-14A1 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Dallas | BFD8-FA98-C995 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Dammam | 9B60-C29C-2FDD | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Delhi | 8165-205F-711E | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Finland | 8078-7604-44CD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Frankfurt | E9B5-99AA-9530 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Hong Kong | FD21-FE9B-6812 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Israel | 8F4E-F343-9D5C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Jakarta | 3F95-F829-7A29 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Japan | C8BD-2296-8EBF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Johannesburg | F9EA-ECD9-A733 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Las Vegas | 0070-FFFB-5C9C | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in London | ABE8-FC47-08DA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Los Angeles | 1153-5169-4D99 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Madrid | EC99-B5EB-ADBC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Melbourne | 76BA-9E11-CC81 | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Mexico | 7BB7-823F-0FD9 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Milan | B1A9-8642-C333 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Montreal | 2A72-A01D-2118 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Mumbai | 544A-6896-5E1B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Netherlands | 0900-3806-D6D5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Osaka | 1B96-B520-DE0C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Paris | 4B9C-005C-D40B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Phoenix | F17E-079C-4176 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Salt Lake City | BF7A-DC1E-431F | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Santiago | 75F8-7143-DA31 | September 9, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Sao Paulo | AD1B-A282-28A7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Seoul | 4BAD-7BAB-46D9 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Singapore | CDB7-FDDC-E5A6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Stockholm | 0C39-F9F5-0FEC | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Sydney | D19E-0601-2165 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Toronto | 8BA9-0C58-EF45 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Virginia | 9350-54C3-9969 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Warsaw | FF3C-3701-DC33 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD Capacity in Zurich | 5C9E-11ED-0E14 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS | DCA4-F1BE-57C4 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Alabama | 2C10-5254-ECBC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Berlin | B278-3F9D-C633 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Columbus | 5BB6-CF5B-0039 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Dallas | 14E0-F474-841B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Dammam | EF9D-BA25-CA6E | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Delhi | D1D9-ED54-A77E | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Finland | B094-C781-2DD1 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Frankfurt | 2F7D-C0D5-8557 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Hong Kong | 51FA-4D79-919D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Israel | BED4-19A5-A7A9 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Jakarta | 5D0B-2838-F524 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Japan | 3735-8421-48EE | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Johannesburg | 3240-A5EF-FA06 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Las Vegas | D484-50A2-CF90 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in London | DA94-9FEA-C94D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Los Angeles | 6AEF-31FC-F5EC | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Madrid | 17E0-5D72-A77D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Melbourne | 6E2A-A559-15DA | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Mexico | 91D1-5B7F-C5AB | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Milan | 261D-091E-A806 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Montreal | 44F5-6213-3360 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Mumbai | 011B-2D29-8EE6 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Netherlands | AB93-9814-15BF | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Osaka | DA57-E232-4770 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Paris | 13FE-CC46-A012 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Phoenix | EEFE-1879-EDAC | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Salt Lake City | 5E3C-12F7-65F1 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Santiago | E0D6-C6B3-BF9A | September 9, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Sao Paulo | CB34-A0B2-21B6 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Seoul | 4205-230E-FA26 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Singapore | E97A-3CDB-37DD | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Stockholm | 0FC4-815B-7B73 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Sydney | 509B-3F1D-C7F8 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Toronto | D38D-0AE3-A629 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Virginia | 7D3D-03D2-A977 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Warsaw | 1800-7268-0492 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Extreme PD IOPS in Zurich | 880A-22CA-2143 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Americas | 2B4F-981A-703B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Belgium | C248-9879-00EA | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Berlin | 90BD-9F93-32EF | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Columbus | E5CB-2341-6961 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Dallas | F102-E6A7-CB1A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Dammam | 6DB3-942C-6E90 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Delhi | 5BDA-9EAD-9F82 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Finland | 35DA-1EAC-2E22 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Frankfurt | D246-F057-34C4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Hong Kong | 90FB-E297-CE14 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Israel | 56D4-617B-4538 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Jakarta | 9A38-CF43-4B36 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Johannesburg | 18C2-38D4-4B92 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Las Vegas | 954F-E2D9-A7AE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in London | 6F36-48E1-9EAE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Los Angeles | 876B-4220-9380 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Madrid | 9CE1-2028-E38D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Melbourne | 77F5-046F-788A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Milan | BBDB-5A3D-1AB8 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Montreal | 37FC-A264-13AB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Mumbai | DAC5-4645-999C | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Netherlands | 9BB1-2BB9-A32A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Osaka | 94AF-BE37-F2DC | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Paris | 7A5F-6624-6CE3 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Phoenix | 0503-B69F-BF44 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Salt Lake City | D4DC-1053-6073 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Santiago | 791A-8659-97D0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Sao Paulo | 173E-E4AD-D7B4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Seoul | 4D47-E876-CA6F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Singapore | 12CB-75EB-8C97 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Stockholm | 80AE-809B-76E4 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Sydney | BA58-DF4C-1C69 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Taiwan | 0ABD-1F8A-957A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Tokyo | 0F1B-4FEC-1F12 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Toronto | 5458-B701-7C91 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Virginia | A5FF-47EB-4878 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Warsaw | D1AA-BA93-DE21 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Core running in Zurich | 2B22-CD49-FFC9 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Americas | D493-0B62-1972 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Belgium | 44B6-634A-135A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Berlin | 0B49-72EE-479F | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Columbus | 501E-4E33-F899 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Dallas | 9A05-9452-81F9 | February 26, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Dammam | 174B-6BE6-FD58 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Delhi | 6465-AA8B-1148 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Finland | 182F-5916-6D31 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Frankfurt | DC14-8104-C4A6 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Hong Kong | 3B13-06E4-C077 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Israel | C6C9-B189-E8B9 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Jakarta | 7034-ECCA-F00A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Johannesburg | 9D85-4C45-0AAA | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Las Vegas | 1C23-2BD3-6F08 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in London | 5D19-ECA3-7B1F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Los Angeles | F32C-98FC-C65F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Madrid | 4707-8F1E-A2BB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Melbourne | E7AC-5E09-CC84 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Milan | 476F-8E7E-3806 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Montreal | A870-3B96-9271 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Mumbai | FCC3-050A-255F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Netherlands | B43D-28F8-F88B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Osaka | 8E0F-B83C-E418 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Paris | D5A5-72D1-D13A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Phoenix | CB17-1525-7219 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Salt Lake City | 355B-9980-4212 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Santiago | 0099-DF25-4A7D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Sao Paulo | 159B-F22B-2D4D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Seoul | B26F-4418-74D4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Singapore | 1B31-5195-94B0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Stockholm | D1EA-B7D8-8986 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Sydney | C6AA-8287-105A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Taiwan | BD72-A3F9-3FE5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Tokyo | 5AD5-0836-8CC8 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Toronto | 624F-B9BC-DEEA | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Virginia | DF7E-9292-2EF7 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Warsaw | E68C-9D92-69E4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Instance Ram running in Zurich | E91A-929B-6578 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Americas | C325-0593-DAE5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Belgium | 329F-CF1D-7711 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Berlin | C16D-35FD-E60F | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Columbus | 3D41-724C-51F2 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Dallas | ED90-A978-BB59 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Dammam | 2C0E-E67A-829B | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Delhi | 073A-6215-79E5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Finland | 6C98-9784-3D2D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Frankfurt | 470D-96E2-88F1 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Hong Kong | F375-B069-3B76 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Israel | 0C66-A411-F6E0 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Jakarta | FCBE-492C-A177 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 39AC-14FC-6FCF | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Las Vegas | 95C1-2AEA-7EF0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in London | 1475-5E5D-F4CE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Los Angeles | A701-06DD-1F55 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Madrid | 85DD-5C44-47EB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Melbourne | 0ECB-927A-D806 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Milan | 09B4-2177-12EF | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Montreal | AB0F-E02C-A5D5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Mumbai | 06C3-15E5-C70E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Netherlands | 0660-DB76-8387 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Osaka | A24D-B9BA-E0DD | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Paris | 5E0A-8AEC-F3C0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Phoenix | 3F8A-EF11-DD96 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Salt Lake City | 86C6-1766-DBA0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Santiago | B44B-7879-5F68 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Sao Paulo | 5E8D-079C-2CF6 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Seoul | 8588-0C23-B21A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Singapore | AAC2-07A8-95BC | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Stockholm | 71F3-6ADB-1C47 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Sydney | 3DA8-BBDF-2A2A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Taiwan | 2E03-ADA0-DC73 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Tokyo | 7F4E-EAEF-1954 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Toronto | 278C-DFA9-7FCC | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Virginia | 77C8-DB6A-62F5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Warsaw | E87A-CF2F-54AF | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Core running in Zurich | FCC6-2937-A20E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Americas | ED78-1B46-DA17 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Belgium | DA63-07A8-4A68 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Berlin | 440A-B5F1-A2F4 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Columbus | 9561-7362-D97C | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Dallas | 7EF6-2D01-E597 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Dammam | 4DBB-CBED-4B43 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Delhi | 7FBC-39E7-28DB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Finland | 856B-5F4B-6AF8 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Frankfurt | 6E51-040E-D918 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Hong Kong | DDD7-8802-8A12 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Israel | 266D-8A17-22B9 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Jakarta | C429-8151-8D98 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | FDD4-53AD-53EE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Las Vegas | B8AC-C3B3-D150 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in London | 5428-61EF-4890 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Los Angeles | 2344-555E-B575 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Madrid | 22C9-2E63-0E41 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Melbourne | 5C3B-AE8A-3EC3 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Milan | 796A-9BA9-C7C4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Montreal | 9CB8-C983-66F5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Mumbai | 2FB1-1DA7-B053 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Netherlands | 182D-A898-0299 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Osaka | 935F-8E69-B5A7 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Paris | 3355-9DCB-8B94 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Phoenix | D47A-233A-077E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Salt Lake City | 5766-90F4-1C79 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Santiago | 89E9-E703-06CD | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Sao Paulo | BB9D-166C-65ED | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Seoul | ACB4-1767-07B1 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Singapore | FE49-604E-0130 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Stockholm | 2A9E-1D1C-4F4B | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Sydney | 6FA4-E838-9EDB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Taiwan | A83D-D759-8554 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Tokyo | 55AB-91CB-7ED4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Toronto | B2B8-FE89-2C9B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Virginia | 6EE6-596D-6719 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Warsaw | D9A1-01B9-EE50 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | M3 Memory-optimized Sole Tenancy Instance Ram running in Zurich | 5277-928A-FE79 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in APAC | 700D-1C95-9737 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Americas | 19A3-E481-8933 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Berlin | 5928-6398-51F2 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Columbus | D5A5-B68D-1CB4 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Dallas | 5BDF-951F-83A9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Dammam | 7BC2-EE68-8B40 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Delhi | 82A7-FCC1-44F7 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in EMEA | D96B-4204-D344 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Finland | 828B-D098-4857 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Frankfurt | 5418-F60E-640B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Hong Kong | 9673-E538-107B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Israel | EDBA-6724-327F | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Jakarta | A185-8836-CBED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Japan | 9398-9081-75AC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Johannesburg | 73CA-C558-D786 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Las Vegas | 564C-233E-992A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in London | F36B-8F24-A2B2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Los Angeles | 3FD6-B2CD-20FE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Madrid | 04EF-6969-72F5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Melbourne | 7081-3F3E-9F2C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Mexico | 41A0-330F-691C | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Milan | 8895-68AF-DFAF | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Montreal | 7212-57EC-46B6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Mumbai | 1A49-702D-0F31 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Netherlands | F2AB-D02C-7EF8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Northern Virginia | DBC5-722E-D90B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Osaka | 5460-4F65-2EDE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Paris | 83DE-DB2A-4922 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Phoenix | B9C6-2889-0B66 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Salt Lake City | 65D1-E560-A5E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Santiago | BC5D-89DE-7123 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Sao Paulo | 5E64-9DC9-7BF4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Seoul | 233E-3796-2768 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Singapore | 79D9-7C0D-4C27 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Singapore | 9731-585C-311D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Stockholm | A98B-9BA2-5197 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Sydney | 7276-CBBE-8A53 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Tokyo | ECDF-ED08-82EF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Toronto | C5F1-BB1D-BCAC | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Virginia | 54D4-6C7C-9867 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Warsaw | E2E3-64A9-15C2 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Core running in Zurich | 0605-21AC-8677 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in APAC | 326E-4200-7C31 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Americas | 646C-54DD-382D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Berlin | 9A68-6968-F7A0 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Columbus | 8843-B5D1-B4CA | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Dallas | 279E-ACF9-BBE2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Dammam | 2325-3470-B9BB | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Delhi | 98E2-B3F4-DB5A | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in EMEA | E9B5-1B06-BBB4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Finland | 7E29-C046-7ACD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Frankfurt | 1A7B-7A7A-0E38 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Hong Kong | 67C9-E8AA-8148 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Israel | AFD4-44AD-0A7B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Jakarta | 641A-372C-334C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Japan | 68D5-29AA-798E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Johannesburg | C9F6-B904-AE6A | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Las Vegas | FC09-74DD-736E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in London | AC10-00B6-A091 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Los Angeles | 7FD3-4C6C-1F7B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Madrid | B69F-8B1A-B793 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Melbourne | A10B-AF57-F201 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Mexico | B12C-00C3-431D | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Milan | CC64-0215-BD61 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Montreal | 2FE5-2518-95A9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Mumbai | 6E36-283B-B3DC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Netherlands | AE19-350A-10F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Northern Virginia | 159B-2200-EAB3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Osaka | 481F-7B2A-B0BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Paris | DB19-9256-2E92 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Phoenix | 73ED-5BFC-7456 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Salt Lake City | 789B-9AE1-E401 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Santiago | 3FA2-2794-E408 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Sao Paulo | 047D-68B8-486E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Seoul | 37AB-7806-366F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Singapore | 1F3C-AD92-C1E7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Singapore | E2AD-9D0E-234E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Stockholm | A606-C403-B740 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Sydney | D12A-E85E-E53A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Tokyo | 2EC7-75E5-E2A2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Toronto | 1A8D-A974-2C37 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Virginia | C3F8-15E1-F3CF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Warsaw | 217C-C5B4-691E | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory Optimized Upgrade Premium for Memory-optimized Instance Ram running in Zurich | 0919-7726-2405 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in APAC | 368F-A091-4474 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Americas | AE53-03EE-A981 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Berlin | BC41-03EC-09A0 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Columbus | 9EBE-220C-B050 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Dallas | D79A-F6EA-CAFD | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Dammam | 839B-9346-6EC0 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Delhi | DA92-15C8-5168 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in EMEA | 8756-8763-C679 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Finland | B26C-33C9-659D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Frankfurt | 61F7-427C-1CD4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Hong Kong | EAB6-6DF7-0B44 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Israel | EE3C-6709-B55E | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Jakarta | EC69-8D9F-B6F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Japan | 255E-0C41-3813 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Johannesburg | 3DF8-AF05-BA4E | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Las Vegas | 0B8E-FF88-28DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in London | FBD3-5D63-8863 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Los Angeles | 520C-E3E0-82F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Madrid | 4029-BA69-CE04 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Melbourne | 791C-9A73-82B9 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Mexico | D655-A96B-7279 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Milan | 3AF4-5009-4BF6 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Montreal | 22FE-C374-7975 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Mumbai | 3FC5-50D3-F70B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Netherlands | 932F-6530-0191 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Northern Virginia | 28D5-8C18-1FE2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Osaka | B386-201E-15BC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Paris | 460D-8D0E-C64D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Phoenix | EDFD-0133-3C89 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Salt Lake City | A5BD-7970-24DB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Santiago | 3E67-3AC1-6570 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Sao Paulo | 7EAC-C91A-83B4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Seoul | 22C9-A969-59CD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Singapore | B428-ABC6-FFED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Singapore | 4EA6-5E74-B349 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Stockholm | 2EC9-7FFF-2F3C | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Sydney | DDC6-8AE6-ECF6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Tokyo | 23EB-5861-7872 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Toronto | 707F-8C83-9E85 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Virginia | C208-228E-1A82 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Warsaw | B9D0-6764-AE9A | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Core running in Zurich | F9CE-88E7-95F7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in APAC | 4549-962B-5169 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Americas | 9DFC-84DE-A1D6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Berlin | 61E6-81D9-9D4A | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Columbus | 2836-2A88-C1E7 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Dallas | 2F67-CDF9-388D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Dammam | E869-1E67-A4ED | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Delhi | F9E6-2E85-137B | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in EMEA | A187-AA4A-8383 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Finland | BB08-FB96-AEC3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Frankfurt | E0B1-8FC0-EFC3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Hong Kong | F11D-CB9F-801C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Israel | 4F6E-B230-F7EE | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Jakarta | 4406-4684-A0CE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Japan | 757F-6F9E-CCEC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Johannesburg | F6AA-F426-BD45 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Las Vegas | 6478-11AD-0696 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in London | D5BC-B267-D021 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Los Angeles | 3861-1526-7A78 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Madrid | 2C51-3006-D843 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Melbourne | 06F6-4D72-DF7C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Mexico | 6EB9-97DB-E27A | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Milan | 2B87-3BAC-34F5 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Montreal | 21DD-50C0-34A1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Mumbai | 1EB9-E952-4664 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Netherlands | 24D0-8D63-21AA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Northern Virginia | 2525-4ED2-E479 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Osaka | DF16-B759-DA06 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Paris | C478-1F01-6831 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Phoenix | 3C96-3262-4283 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Salt Lake City | 57A3-FC48-F966 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Santiago | FBE6-3336-92D2 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Sao Paulo | 6545-FD2E-F55F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Seoul | C235-7637-B9CC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Singapore | 71A5-A7E8-C37C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Singapore | C18E-DD54-9DD1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Stockholm | 96D7-C986-1F21 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Sydney | 3ED9-BF4D-E2BC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Tokyo | 570B-10D7-C81F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Toronto | 1BB6-13B7-E7D0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Virginia | A09C-017D-4EEB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Warsaw | 7810-E748-7C61 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Instance Ram running in Zurich | F410-ABCD-B49C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in APAC | 3A0E-7351-5451 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Americas | 56BE-7687-FE88 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Berlin | 6F6A-5CF3-F45D | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Columbus | EA15-694D-B1BF | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Dallas | D43C-B693-37DB | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Dammam | 43D3-3900-B438 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Delhi | 87ED-225D-C68C | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in EMEA | 354E-6EBD-B241 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Finland | EAA8-D538-673D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Frankfurt | 836F-3D87-3FAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Hong Kong | C9BC-2EEF-D2EA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Israel | D45B-77F4-440D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Jakarta | 0217-F90D-0A84 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Japan | 05E3-E0BE-6E28 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 211C-6A50-A5F1 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Las Vegas | AE07-6BD7-24ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in London | 714E-7359-4327 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Los Angeles | 4288-85B4-85BF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Madrid | E8EB-F143-F958 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Melbourne | 973F-AE9E-E761 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Mexico | 4826-B7FF-FEFD | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Milan | 9FFF-A93F-1508 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Montreal | A209-CF3E-A311 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Mumbai | 01FA-D9B9-1E14 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Netherlands | 063E-2EE5-4983 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Northern Virginia | B2D1-9F5D-A66D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Osaka | 762B-BF4D-B49E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Paris | 5077-9ABA-1503 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Phoenix | 0EC8-C401-15C4 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Salt Lake City | 66C6-AEF4-72E2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Santiago | 71DB-4FED-5568 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Sao Paulo | DC11-9C2F-AAE2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Seoul | C9E0-3779-CF2A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Singapore | 048B-9038-B2BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Stockholm | 12C4-25F3-1A40 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Sydney | C778-136F-B252 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Tokyo | 4BFA-7A6A-E893 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Toronto | E577-19A2-4677 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Virginia | 5C61-B65A-4357 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Warsaw | E11F-2524-0AB2 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Core running in Zurich | 397F-7B98-3759 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in APAC | 6AD9-F7EF-5BBF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Americas | 682E-93BF-F222 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Columbus | F68F-6348-B7AF | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Delhi | 67B6-AA3B-5A76 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in EMEA | EA03-9A82-6C01 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Finland | E343-C613-AFE1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Frankfurt | 9EE6-5AD6-B216 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Hong Kong | 1497-042C-D4F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Jakarta | 7418-9246-4B32 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Japan | 718E-3B86-DC0C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Las Vegas | D8A0-D8D2-A2D3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in London | 8158-970E-78E6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Los Angeles | 93FA-9B1A-E858 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Melbourne | 8C2C-3E02-0A01 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Montreal | 9666-853D-4F28 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Mumbai | 762E-9DA9-9AEB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Netherlands | 3194-D33A-2910 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Northern Virginia | 0854-84EF-C13D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Osaka | 3ED5-AFCC-B89D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Salt Lake City | 1C27-FDB3-1784 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Santiago | 0EB3-4560-5443 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Sao Paulo | 6BA3-5061-61C7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Seoul | 05A9-FF4D-25B3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Singapore | 8169-ECB1-EF35 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Sydney | 704A-3C13-E154 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Tokyo | 151B-110A-F463 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Toronto | 21E9-90F9-9F91 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Virginia | 0FDF-61CE-C317 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Warsaw | DCFF-0689-3F43 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance RAM running in Zurich | 5244-C45F-7A05 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Berlin | 043F-A779-AB33 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Dallas | D41C-9679-9F82 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Dammam | 616D-4923-B191 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Israel | 4570-83AC-F516 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 5A43-3E1E-8A1F | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Madrid | 39A9-2968-0B7F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Milan | 0E39-7589-44FD | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Paris | 8A02-6CE4-0B34 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Phoenix | C00E-8036-66BE | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Memory-optimized Sole Tenancy Instance Ram running in Stockholm | ACD5-049D-F660 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in APAC | E3EE-02EB-33B4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Americas | 5CE5-087B-6C3C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Berlin | 812B-E03C-FE54 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Columbus | 83F4-1982-B5E7 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Dallas | 5174-67E3-AFC9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Dammam | FCB4-B4EC-B8B0 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Delhi | 206F-A601-F965 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in EMEA | 5619-DD14-5F41 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Finland | 1228-0F9A-097E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Frankfurt | 91C1-5F17-3531 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Hong Kong | 5B27-7C3B-BD40 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Israel | 1C77-F91B-782D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Jakarta | 14E2-D496-E290 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Japan | 9E0C-B73D-E7DF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Johannesburg | 5AEF-5436-7205 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Las Vegas | BD92-3AC2-EFF7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in London | 389D-815E-FE97 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Los Angeles | C4BD-9ECC-F4BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Madrid | BED7-360C-3CFF | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Melbourne | 6B38-30CE-DACE | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Mexico | B26D-A34E-3AB6 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Milan | 2AB3-C07F-7C9C | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Montreal | 4B61-2549-9309 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Mumbai | A929-7679-DC50 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Netherlands | F412-9959-3D98 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Osaka | 2218-6824-F7A6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Paris | FECE-F8D4-9A11 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Phoenix | 4657-4EE1-B7F7 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Salt Lake City | 54E4-6B72-6E7E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Santiago | FF1C-A5F9-3E5C | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Sao Paulo | B67B-E4F8-5950 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Seoul | B268-F734-C372 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Singapore | 21D7-4648-AED4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Stockholm | BE34-62A4-9FF8 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Sydney | C42F-D794-5133 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Toronto | 1364-5302-CFF8 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Virginia | 9938-D7EE-FCAC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Warsaw | 46AD-1AB9-0881 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Micro Instance with burstable CPU running in Zurich | 6863-F40A-3E86 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in APAC | 4842-5B9D-3916 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Americas | 2E27-4F75-95CD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Berlin | B2D6-C457-C79B | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Columbus | 92E1-B0B2-5F30 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Dallas | 8DC7-851C-E04B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Dammam | BE35-80CB-92E2 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Delhi | 41A7-739E-F721 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in EMEA | 9431-52B1-2C4F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Finland | C39A-7330-9248 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Frankfurt | A9C0-BADB-1C34 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Hong Kong | 3916-2122-654D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Israel | 9F7C-A991-8475 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Jakarta | E495-6D54-813B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Japan | 9050-A990-A974 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Johannesburg | FE0B-E0C0-0034 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Las Vegas | E088-3290-2E7A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in London | E3BF-72A4-1954 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Los Angeles | ADC5-CFA0-B149 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Madrid | E2C7-669A-E422 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Melbourne | 8127-289B-AF2D | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Milan | B73D-B322-1BAB | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Montreal | 12C8-4A10-BA76 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Mumbai | 75BE-4FB0-E4E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Netherlands | 62A6-21EE-5C6A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Osaka | 86F0-A9F2-C89D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Paris | 5C82-ADFD-7768 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Phoenix | 16EA-EA7F-FEC1 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Salt Lake City | 87B9-CB23-ACF7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Santiago | 21DB-5509-B869 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Sao Paulo | E8F8-A4B0-C91F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Seoul | 1C6C-CD98-D14F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Singapore | 7ED6-57D6-C844 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Stockholm | 7737-F377-3B4D | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Sydney | EC56-26CB-F016 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Toronto | 9E97-34EA-479F | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Virginia | 2026-872A-3AB3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Warsaw | 8131-C7CF-24C6 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Core running in Zurich | 718A-81BA-2CBB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in APAC | C274-DFF1-D882 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Americas | 6C71-E844-38BC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Berlin | 75B1-0AD9-928F | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Columbus | 2FBD-DC66-6037 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Dallas | CF96-DC31-6F1B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Dammam | EF4D-4471-320B | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Delhi | 674E-4FDB-1648 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in EMEA | 39F4-0112-6F39 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Finland | 924B-F033-FB24 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Frankfurt | 5C8C-3C2D-B331 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Hong Kong | 0CFE-58D2-2D8D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Israel | EBE1-B0A8-9215 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Jakarta | CDA7-F08D-9E3B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Japan | A444-A355-F28C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Johannesburg | 0298-73DA-B49E | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Las Vegas | 5A9F-8B65-5A3D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in London | FCA7-22FF-B1CC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Los Angeles | 3500-0487-459B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Madrid | 6538-255A-391B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Melbourne | 8412-9F62-9561 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Mexico | 6823-4BAC-1823 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Milan | 0BBB-3733-F409 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Montreal | E131-9E4D-4A38 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Mumbai | 5736-3E10-2B21 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Netherlands | 7919-4540-EDB2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Osaka | B407-487E-1CB5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Paris | B3D3-FF1D-90CE | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Phoenix | BB22-EF82-5A8A | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Salt Lake City | F21A-1162-D59D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Santiago | 801A-E14C-F067 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Sao Paulo | E128-228B-EA2A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Seoul | 6B10-CEC7-0965 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Singapore | 0143-7EA7-329F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Stockholm | 23C7-6154-9EA0 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Sydney | F2CE-80F1-A345 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Toronto | 89D7-D029-1311 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Virginia | 6E2A-DCD9-87ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Warsaw | 1B51-BAD1-3C07 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N1 Predefined Instance Ram running in Zurich | 000F-E31B-1D6F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in APAC | 725E-B154-E759 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Americas | E8A6-06D8-F69C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Berlin | 99FD-790A-621B | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Columbus | 406C-D746-818B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Dallas | 74D3-9B15-2860 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Dammam | 5293-0DEA-76F7 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Delhi | C554-B3C0-3F64 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in EMEA | 6E4E-1FAC-3BA5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Finland | D5DF-A49F-8441 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Frankfurt | 2965-7160-04A2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Hong Kong | 4E0C-ACF7-FC86 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Israel | DF18-4911-23E8 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Jakarta | 15C6-E5BC-2A2A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Japan | DFBC-35ED-C31F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Johannesburg | FD04-C6CD-56FF | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Las Vegas | DEAA-CEB1-1AB2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in London | E2F1-104D-AE7B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Los Angeles | 14FA-1848-4CAA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Madrid | F968-A714-EAC4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Melbourne | 5194-768F-C9EF | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Milan | 06A1-489E-8CF4 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Montreal | 45AE-0DD2-E4D9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Mumbai | 3C1F-0B09-F3E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Netherlands | C5A2-E156-F885 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Osaka | 53FC-0398-CA27 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Paris | 697B-E151-D936 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Phoenix | EE0F-C482-899A | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Salt Lake City | 8762-1BBD-3265 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Santiago | 0CBB-2C0B-EFE3 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Sao Paulo | 46FD-5CA2-0007 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Seoul | 3663-7764-1304 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Singapore | E97F-57F5-F341 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Stockholm | 257D-305A-82E3 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Sydney | 0FA3-772E-09BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Toronto | F2F7-6855-64A3 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Virginia | 4649-0BEC-F3AD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Warsaw | CEAF-6497-FE85 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Extended Instance Ram running in Zurich | A260-4B3D-F56A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in APAC | A48D-90EC-00EC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Americas | 3E94-1AB5-33F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Berlin | 2647-F9BF-BAC5 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Columbus | 06A6-75A1-B68C | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Dallas | A556-79B4-6EF5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Dammam | 6A26-753A-9449 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Delhi | AD5D-95DE-BD1B | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in EMEA | 0976-7487-062C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Finland | 038E-428B-6479 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Frankfurt | C836-3D4C-F874 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Hong Kong | 5B72-95CA-B29A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Israel | 16B8-C368-B5D6 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Jakarta | 2EB0-5403-B893 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Japan | 3C79-46FF-0C0A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Johannesburg | 2DC2-2DB0-925E | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Las Vegas | 880D-C64E-B27A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in London | 6924-2ADC-063A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Los Angeles | 39D2-E298-5C3E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Madrid | 277B-B3D2-0923 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Melbourne | 0736-BFB2-B4FD | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Milan | 0B58-50EB-721F | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Montreal | B4CA-178A-4909 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Mumbai | FC69-4A67-C34D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Netherlands | DA9A-6614-3548 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Osaka | E891-CC68-96D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Paris | FD64-0479-B501 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Phoenix | 6F3C-A600-9371 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Salt Lake City | 2F7D-94FD-735C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Santiago | B77B-EB0D-C9DB | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Sao Paulo | 391C-E3D4-4D3A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Seoul | 6F2A-8ADB-88C3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Singapore | D432-F64C-0F60 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Stockholm | 542E-F40B-A2DE | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Sydney | CACB-AC79-18A4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Toronto | EEF4-F364-6FBD | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Virginia | 0B2D-BDE1-6668 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Warsaw | E22C-E9CF-D326 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Core running in Zurich | 9C19-672A-2011 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in APAC | ACE4-4FE6-641C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Americas | 5304-5146-9088 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Berlin | D837-3A75-8F61 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Columbus | 034D-E8B5-A072 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Dallas | 96D6-3C56-D45B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Dammam | 4210-10B7-07DC | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Delhi | F961-9D5F-4383 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in EMEA | CA5F-A13B-29EA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Finland | 595E-74E5-DABD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Frankfurt | 837D-1134-9F72 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Hong Kong | 159F-AB01-4F9C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Israel | AABE-3818-B87B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Jakarta | 8128-3483-7333 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Japan | F68A-05BC-1EE9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Johannesburg | 634C-B735-3E12 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Las Vegas | 7691-78AA-E288 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in London | 3A49-05F0-7CF0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Los Angeles | 70E7-9889-C9EC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Madrid | B9A1-ED2E-87B8 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Melbourne | 3E23-9FB5-5BE0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Milan | D68C-640D-68BA | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Montreal | FAD2-8331-1006 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Mumbai | 88AC-E248-BFC6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Netherlands | C1AD-7471-F6C1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Osaka | F6A3-5FF6-F21E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Paris | BC94-0B24-FAE5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Phoenix | 049F-6A94-1D23 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Salt Lake City | B909-FCCF-B2F9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Santiago | B74D-E53E-CB05 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Sao Paulo | C76B-0D36-2457 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Seoul | 2CCC-E20A-06DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Singapore | 1F19-9175-5B89 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Stockholm | 1B62-D241-534E | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Sydney | 12C4-F201-DA07 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Toronto | 1E49-E90F-92F9 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Virginia | A996-8018-FA18 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Warsaw | D2CE-FD05-CEC2 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Custom Instance Ram running in Zurich | A43B-CA38-009A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in APAC | 1B8C-264F-447E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Americas | BB77-5FDA-69D9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Berlin | 2AAC-5430-5052 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Columbus | AC56-47BD-703D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Dallas | 62EC-22E4-6E3D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Dammam | F892-6AA0-B93C | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Delhi | 73EE-1419-7501 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in EMEA | 9F61-45D7-D4FB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Finland | 59FD-DA88-2A13 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Frankfurt | 53BB-FF1B-0C91 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Hong Kong | 68CB-4CDF-D6C2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Israel | 989D-20AE-D4FC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Jakarta | 1E79-A719-6653 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Japan | E137-7DDF-1143 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Johannesburg | EE46-3F79-CA9D | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Las Vegas | 5467-593D-DD72 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in London | 6EA2-F2F1-BBB4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Los Angeles | A118-C0E0-D091 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Madrid | C8C8-6EAA-E72D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Melbourne | F1DD-9B94-5C6C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Milan | 7293-75B6-FE15 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Montreal | CBC9-2071-267A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Mumbai | 3A1A-7CFC-5747 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Netherlands | B46B-6090-FA88 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Osaka | C4D8-6E4C-3BF9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Paris | F264-E520-0277 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Phoenix | DAAA-3573-68F7 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Salt Lake City | 662F-0A9B-36DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Santiago | 7426-261D-34A4 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Sao Paulo | 8F60-4F60-EE56 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Seoul | D71C-9B8F-0ED9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Singapore | 2514-CA24-299A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Stockholm | 3340-7253-199C | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Sydney | 0382-1327-146D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Toronto | EC56-EBB7-DAB3 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Virginia | 5571-8F21-9137 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Warsaw | 35E6-B2EE-DE63 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Core running in Zurich | 6320-5E2C-96C1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in APAC | 2297-D3C7-1085 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Americas | 5B01-D157-A097 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Berlin | EFD6-197E-0212 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Columbus | 25E5-DDFF-6CD2 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Dallas | 2756-7DCF-9D01 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Dammam | 1CE2-252E-D1EA | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Delhi | 4FC1-0994-5D3A | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in EMEA | A109-54C1-7CB0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Finland | C458-9509-E762 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Frankfurt | A5A6-3EDC-7F3C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Hong Kong | 2C8B-C962-467D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Israel | A85D-97DD-5B85 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Jakarta | 852E-0449-B664 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Japan | CFB3-624B-6A52 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Johannesburg | 2877-22EB-5946 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Las Vegas | FA34-B408-E0FF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in London | A557-29AB-E13A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Los Angeles | 28C0-92D5-8DE5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Madrid | B6B6-38EC-824B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Melbourne | 1B7D-AA31-0142 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Milan | B319-78AD-242C | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Montreal | 45C7-42BE-4253 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Mumbai | 23FA-BF9A-7C7A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Netherlands | EFCB-2D7A-52B6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Osaka | AB68-2A46-1E54 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Paris | F83E-0ED3-1C12 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Phoenix | 3A30-DAD5-14D3 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Salt Lake City | CCE4-BB91-51FE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Santiago | 0DC1-8F7F-175B | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Sao Paulo | 6487-C110-BE19 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Seoul | A9FC-4BD1-8E21 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Singapore | C84B-1AD4-8EAE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Stockholm | 6EE2-5F49-98AC | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Sydney | FC62-C94D-BE38 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Toronto | 6BEF-1529-C828 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Virginia | A96B-6699-99E0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Warsaw | 64D3-DA96-E5F0 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Instance Ram running in Zurich | A7C6-F754-76FF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in APAC | C541-C59B-8BC3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Americas | 04AB-D481-4CDD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Berlin | 775D-E99A-9D12 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Columbus | 8C38-40C0-CABF | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Dallas | 8A4B-3E3B-6DB2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Dammam | 0A33-D14F-5869 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Delhi | 65C7-8DB4-AB11 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in EMEA | 0C66-E858-A69B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Finland | E613-8861-2215 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Frankfurt | 5A7D-6451-7F1D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Hong Kong | 42C4-DDD6-9753 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Israel | 6E57-9A83-7FA4 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Jakarta | B436-D5FB-EDAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Japan | 193E-2B18-C454 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Johannesburg | 6162-8660-EE3D | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Las Vegas | 21D2-AA41-ECAA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in London | E77A-4E37-6F7D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Los Angeles | 2B29-3D5B-17AD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Madrid | 8A6E-3EFE-4610 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Melbourne | 2B98-E121-3179 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Milan | 0425-B74A-1147 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Montreal | C2BA-6D03-F906 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Mumbai | 5742-2AB8-EA52 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Netherlands | 46EC-B5F3-0739 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Osaka | 434E-C707-7577 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Paris | 116A-B692-0885 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Phoenix | 10C1-126F-1FD3 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Salt Lake City | C602-0665-25A3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Santiago | C988-2862-6823 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Sao Paulo | 492D-AB2D-B452 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Seoul | 9A7D-5E02-B202 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Singapore | F2A2-F46C-3699 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Stockholm | 626E-23D9-0164 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Sydney | E9E5-8EA7-BD81 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Toronto | 1E4B-7A05-7838 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Virginia | 96C9-0B75-FD04 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Warsaw | 10B3-C77B-83CD | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Core running in Zurich | 39B8-FB68-ED92 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in APAC | 4FF0-963E-6E7C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Americas | A8F6-5698-E691 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Columbus | B632-332B-82CF | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Delhi | 71CA-2AAD-9AEC | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in EMEA | 9F5F-3505-91ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Finland | 1F42-C00F-7920 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Frankfurt | 64AE-46F4-186F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Hong Kong | B426-1C1A-6232 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Jakarta | 2D67-92B7-B82F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Japan | C9F7-74AD-1DAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Las Vegas | 374C-9E59-006B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in London | 48DC-3EAE-7373 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Los Angeles | 9163-29BE-983D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Melbourne | 684A-BEED-C127 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Montreal | 2551-2088-C813 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Mumbai | 1893-8C3C-B582 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Netherlands | F328-3354-D246 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Osaka | B7D0-5EB7-BCAC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Salt Lake City | ADC7-289E-CC96 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Santiago | F75E-1A3A-3F3E | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Sao Paulo | 9EE1-5093-843A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Seoul | 03B8-4A28-DA9D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Singapore | 3780-FD58-C69E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Sydney | B2A9-06E8-1B3E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Toronto | 979F-4C15-9D9A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Virginia | F48F-3B6B-0746 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Warsaw | 9C55-6E60-8F26 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance RAM running in Zurich | 733F-CA93-10E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Berlin | 90F4-56A5-C8E8 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Dallas | 8154-4F1C-ABB8 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Dammam | 6325-3E07-B335 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Israel | 1980-69B3-183D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Johannesburg | E089-B561-1E7E | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Madrid | A7CB-C8A9-10E6 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Milan | 04D1-B5EB-81C3 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Paris | B328-A80C-CEED | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Phoenix | 7A03-FA84-4008 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2 Sole Tenancy Instance Ram running in Stockholm | 9AC7-03E3-3C3F | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Berlin | A645-6E83-63DC | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Dallas | 16FD-5A81-A046 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Dammam | 2A0F-47E9-9511 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Israel | 6A55-631D-0630 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Johannesburg | 3C85-25F1-A0B8 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Madrid | 6289-381E-CC22 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Milan | 6FD4-A50F-E621 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Paris | F891-C53B-1522 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Phoenix | 80F0-7CA0-7005 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Instance Ram running in Stockholm | D187-E9F8-C580 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in APAC | 1383-93D0-ABBE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Americas | CC77-3AED-816F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Columbus | 313D-8B90-8869 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Delhi | 8D23-D0EF-F245 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in EMEA | 9D38-DE1F-5156 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Finland | FAE4-B8CB-E760 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Frankfurt | E905-3719-ECEA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Hong Kong | A107-E302-8F25 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Jakarta | EF71-FEA7-E4DB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Japan | EC8D-F249-CAC5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Las Vegas | E76C-AF5C-B38F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in London | 554D-4D67-8448 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Los Angeles | 543F-D4A9-7F18 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Melbourne | F992-2F68-08DE | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Montreal | B9FB-BE8C-82F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Mumbai | BAA0-4B92-1383 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Netherlands | 32F0-F990-057F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Osaka | 15D9-B4DA-B5F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Salt Lake City | F4C6-4D85-E73F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Santiago | F235-C9DF-9D1B | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Sao Paulo | 5A54-5B10-D577 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Seoul | 9AE4-8F6A-68BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Singapore | DAE7-6982-9522 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Sydney | BD91-7947-8736 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Toronto | A0A8-8FD1-4D76 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Virginia | 1D9B-FAF5-F7FC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Warsaw | E879-10F8-2BD7 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Extended Ram running in Zurich | 9748-7F3D-CD38 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in APAC | AE97-3760-ECCC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Americas | 55FE-5117-DF8B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Berlin | ADD9-A5B9-8FA9 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Columbus | 76D6-D2DE-EFFA | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Dallas | FA52-64A8-04DA | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Dammam | CC8D-EBE1-3364 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Delhi | C7AE-4A32-32AB | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in EMEA | 6672-F702-DDC4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Finland | AD11-3DC6-E076 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Frankfurt | 4BD7-1A01-048A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Hong Kong | 9669-248F-CE45 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Israel | FA92-F0A9-2158 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Jakarta | 2F99-211F-C567 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Japan | 6C99-977D-2500 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Johannesburg | 7693-1EF9-B6A1 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Las Vegas | 8ACA-B986-2E54 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in London | CB66-DAAE-8837 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Los Angeles | 01FE-1823-247B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Madrid | FED1-B3A4-C434 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Melbourne | 1A77-D337-E793 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Milan | 3073-3750-EFF0 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Montreal | 5108-9DAD-44E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Mumbai | 665E-E4CD-1D74 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Netherlands | 675D-892B-446A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Osaka | 8B64-9CD1-2EA7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Paris | E7CF-E368-B379 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Phoenix | 5C04-4C13-B383 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Salt Lake City | C87C-9C22-51BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Santiago | 20EA-3D53-8590 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Sao Paulo | BA32-D484-6243 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Seoul | 275F-34D4-FDFD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Singapore | FDBB-84BE-0AF7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Stockholm | 4593-7038-D420 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Sydney | 8556-A774-DEC2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Toronto | D50E-3221-4EEC | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Virginia | 115C-7108-8B9E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Warsaw | AE9F-20D5-91BA | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Core running in Zurich | 8FDA-012F-7B65 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in APAC | 65A9-01F9-3FB2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Americas | CED4-7119-A546 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Berlin | 1B8B-A937-37D7 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Columbus | C4A9-EB2B-626D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Dallas | 31D1-3C96-3913 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Dammam | BD34-11BF-9DC4 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Delhi | E0F4-268A-2316 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in EMEA | 3914-87EF-A9CA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Finland | E958-DC4F-A16B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Frankfurt | 89BC-9DB5-3AB6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Hong Kong | 4E3E-640F-F228 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Israel | 9932-0DC6-DFFA | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Jakarta | 374F-4D56-58C0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Japan | D484-8C81-94CA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Johannesburg | 7866-0AD5-B78D | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Las Vegas | BAB5-46F3-C9B8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in London | B1CB-59AC-0785 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Los Angeles | 1781-1A20-1DD7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Madrid | E9B2-4079-92D2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Melbourne | F57D-3E8B-E7AD | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Milan | 2ABE-B865-878B | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Montreal | BFDA-E726-2761 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Mumbai | 60E6-333B-57BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Netherlands | 377F-267F-8F7F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Osaka | F787-522B-80EB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Paris | 27F2-8847-8993 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Phoenix | 3B38-900E-8D4A | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Salt Lake City | EE37-2679-BDEA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Santiago | 49B5-AD7B-C95F | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Sao Paulo | 1C2E-D456-0B92 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Seoul | 3860-1A51-6AC0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Singapore | 4CBB-9DAF-2D6E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Stockholm | 2CA6-1826-1AE3 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Sydney | 3F85-10A4-440C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Toronto | 4823-FD0B-55AF | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Virginia | 5719-5C5A-9EAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Warsaw | 6BD0-613F-5874 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Custom Instance Ram running in Zurich | 07C7-3B6C-C92A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in APAC | EF6C-66BA-C9C6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Americas | A03E-E620-7389 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Berlin | C8AE-0102-5B06 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Columbus | 2C08-0DED-36F3 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Dallas | 29DE-E9FE-7872 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Dammam | 894B-36DF-FDC1 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Delhi | 4289-2AC4-32AE | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in EMEA | 9201-F0D0-15DA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Finland | 4791-064D-3189 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Frankfurt | 18D3-E0E1-C1A1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Hong Kong | A640-62BC-0C6C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Israel | FE03-BB37-AD1F | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Jakarta | 9653-E8D4-C871 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Japan | E3DA-E73C-3FCD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Johannesburg | A903-CE02-AD33 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Las Vegas | 0E8D-9FEF-852D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in London | 1B12-3BA5-80A4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Los Angeles | 2540-FD54-92D3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Madrid | FCE5-6D7D-935F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Melbourne | 4C01-B57D-5057 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Milan | 0B56-1371-9FBF | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Montreal | 13DD-415F-AF29 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Mumbai | 0DAC-F520-B2D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Netherlands | 0450-45CE-C078 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Osaka | CDA5-479A-D53F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Paris | 9A1E-0C13-E40C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Phoenix | E2D3-0481-0A4E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Salt Lake City | 011F-F649-4A0D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Santiago | 0365-2006-3FFE | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Sao Paulo | EC8A-8CC8-A8F0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Seoul | 9F49-AF93-20A7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Singapore | 8B4E-B458-AD51 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Stockholm | C68E-41B3-0610 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Sydney | 2F62-931F-7C45 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Toronto | 5301-3C91-6D0A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Virginia | 809C-1E3B-306E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Warsaw | D6C7-BFE7-CA01 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Core running in Zurich | 4192-5050-2178 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in APAC | FFF7-7A42-F2E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Americas | 5535-6D2D-4B50 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Berlin | EDA5-E252-95C0 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Columbus | 5682-8AD5-97D9 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Dallas | 296B-A47C-3667 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Dammam | 4F32-A552-9B5C | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Delhi | C8D0-536C-DF7C | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in EMEA | 0A3A-4D14-E11B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Finland | F579-1568-AEED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Frankfurt | A57E-8491-5C53 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Hong Kong | 95C6-3CAC-175A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Israel | 019D-ED1E-9BD7 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Jakarta | F50A-B110-CF48 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Japan | 4DE7-0DB1-1ECB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Johannesburg | D455-945C-A274 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Las Vegas | ABD2-309F-B86A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in London | 462E-70CF-C7AF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Los Angeles | 1FEE-CE8E-2D35 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Madrid | 2B20-9526-9061 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Melbourne | 2516-7FC7-97F9 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Milan | BD2C-2B6F-83BC | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Montreal | 5929-5298-664A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Mumbai | E021-0FE4-1AC3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Netherlands | D484-E83B-5FD6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Osaka | 7DD8-7C56-8F10 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Paris | 5D73-8F02-FE5C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Phoenix | B3C2-5A26-804C | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Salt Lake City | 98E9-BA44-DDD2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Santiago | B39E-9089-083F | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Sao Paulo | F92D-0A8D-649F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Seoul | 7609-A4B6-9218 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Singapore | 92EB-71EA-DA74 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Stockholm | 603F-DD08-ED9E | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Sydney | 95C7-D6E0-3BF6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Toronto | 09B1-0975-EC89 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Virginia | D293-6255-369A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Warsaw | 069E-200D-3C4D | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Instance Ram running in Zurich | 5F90-8155-6576 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in APAC | 8E7A-07F0-1E17 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Americas | C155-67FE-81D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Berlin | 87FE-F135-1E02 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Columbus | E3B2-FD88-2BA3 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Dallas | 2CE7-94ED-61ED | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Dammam | E1F6-EC43-CCFD | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Delhi | 8F27-63CD-D3BC | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in EMEA | A3AA-BD60-02DC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Finland | A514-4F67-F601 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Frankfurt | 24C1-1AB1-5729 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Hong Kong | 46E6-5891-4314 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Israel | 2189-AB8C-40CF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Jakarta | 2245-3D8F-76DE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Japan | E7E3-34C4-0CA8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Johannesburg | 9CC1-342B-FCE6 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Las Vegas | 74CB-809C-47C2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in London | ACB9-F01F-EB6E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Los Angeles | B851-66F8-E625 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Madrid | 9894-9914-F103 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Melbourne | 8F96-8B0F-2815 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Milan | 5355-B076-6637 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Montreal | 4AD7-96B5-8D32 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Mumbai | 6A1E-5909-411F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Netherlands | 6346-0F6D-75B4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Osaka | 2B99-9EC4-46E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Paris | 0CCF-01CD-14D0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Phoenix | 04B6-8C51-C18D | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Salt Lake City | 332B-D9F0-D6A3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Santiago | 8471-908E-689A | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Sao Paulo | FBBF-FACF-E7DC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Seoul | A1ED-4BB0-A948 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Singapore | 90CB-D334-261B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Stockholm | A9D6-2DE9-1373 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Sydney | 9BE6-3E92-1AB7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Toronto | 7212-805B-54E7 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Virginia | 8AB3-1655-E5BC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Warsaw | CF56-1BB7-9268 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Core running in Zurich | AE18-AEDF-17C4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in APAC | 4751-A892-816B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Americas | E011-E2D6-130E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Columbus | 467E-A9F4-DA3D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Delhi | 88F4-AF16-A17D | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in EMEA | 721C-DD91-B98B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Finland | 0FFD-03C0-A76D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Frankfurt | C285-992B-8021 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Hong Kong | 52E4-6DC7-4C71 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Jakarta | 3476-4FF7-77E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Japan | 8AAA-6BD7-006E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Las Vegas | 07F9-5556-0D8D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in London | 6416-C0C5-0701 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Los Angeles | E462-8689-C240 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Melbourne | 48A2-A625-DB4A | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Montreal | 1185-6B77-7A6B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Mumbai | 9F81-05FC-5A6F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Netherlands | EE41-AEC8-D2C1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Osaka | F939-510F-E25B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Salt Lake City | 26C2-1F89-2BF6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Santiago | 4F14-7E27-11D6 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Sao Paulo | 7B60-BA3D-AF11 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Seoul | 7C63-87A5-A833 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Singapore | 8958-74BA-D489 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Sydney | EAD6-DBC6-1912 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Toronto | 75FF-2746-76D6 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Virginia | 6C9F-510F-A194 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Warsaw | BC13-07BC-117A | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance RAM running in Zurich | 4E42-68AE-1C0A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Berlin | 64AE-643F-D488 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Dallas | 452A-D71E-D4ED | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Dammam | C644-0C02-67BF | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Israel | B68F-03CD-E7AF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 822B-0FE0-5F2C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Madrid | AE3F-BC25-ACC0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Milan | F57D-5674-8B7F | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Paris | 4269-95E7-B62B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Phoenix | 9E7F-A7A7-A1FB | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | N2D AMD Sole Tenancy Instance Ram running in Stockholm | 8116-4A84-FA45 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Americas | EDA0-3A70-3138 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Belgium | 5CFC-91A5-9B5C | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Berlin | BC3C-1E7B-D8A9 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Columbus | 7AE6-A1F9-277A | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Dallas | 2A1A-92CF-8854 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Dammam | 1E1B-0229-0EE2 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Delhi | 6D10-78F3-0F9F | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Finland | B397-E5AF-025D | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Frankfurt | E21F-ACA9-BD4E | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Hong Kong | 812C-1A90-098D | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Israel | B953-2E6C-3CD5 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Jakarta | 176E-7B2D-55CE | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Johannesburg | DF7B-A9A2-2710 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Las Vegas | 0BFC-D96C-F4D1 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in London | 5A44-6F11-10C3 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Los Angeles | 6E55-E398-4915 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Madrid | A684-6199-E1EB | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Melbourne | 80F5-20BE-E892 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Milan | C0B5-7C55-D939 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Montreal | 953A-B19C-D7EB | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Mumbai | 6AD5-B941-E4E3 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Netherlands | AC33-B5A5-C20F | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Osaka | 5B7D-FEE2-2A0D | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Paris | 0E57-B179-37BA | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Phoenix | 6CB6-E9F5-1557 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Salt Lake City | A5C4-5856-00F7 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Santiago | CAE0-BBF9-E7D4 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Sao Paulo | DD2F-7277-91CB | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Seoul | 4FC9-53F0-3BEB | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Singapore | 1C49-8ADA-54A8 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Stockholm | 77E1-B3F6-07DA | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Sydney | A58A-ACA7-2EAC | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Taiwan | FE50-91A6-991E | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Tokyo | 331A-43CA-10A3 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Toronto | 56B0-B26B-8435 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Virginia | 7DB9-FA3F-C73C | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Warsaw | C420-3942-30F3 | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 80GB GPU running in Zurich | ECFA-CC6D-505B | November 10, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in APAC | DB4C-F9D7-22BB | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Americas | 039F-D0DA-4055 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Berlin | 5FBE-AB9A-4348 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Columbus | DC5F-BC5F-227C | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Dallas | 488E-4CBD-C03F | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Dammam | 8EFD-B595-F660 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Delhi | 1CFD-1845-BBC6 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in EMEA | 50D9-B0E2-1064 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Finland | 6890-9791-F3E4 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Frankfurt | 244D-2D3C-79D9 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Hong Kong | C499-189B-E2AD | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Israel | 414D-2712-0666 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Jakarta | B44D-7962-C093 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Japan | CD56-E5A3-109D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Johannesburg | 6F4F-446B-3D40 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Las Vegas | 2556-84E0-3F53 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in London | D931-12B6-B5E4 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Los Angeles | 0D90-CC9E-5C98 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Madrid | 0AA1-9606-97E3 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Melbourne | ECB2-06FE-3499 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Milan | C381-1441-9F1A | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Montreal | E01D-515F-D68D | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Mumbai | E92A-B86F-50E5 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Netherlands | FAA1-17BD-3A62 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Osaka | AA53-55C2-5F5E | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Paris | 9157-B060-7301 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Phoenix | 1BDB-6B06-0518 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Salt Lake City | 673A-8EAB-1605 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Santiago | B112-8056-4B87 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Sao Paulo | 6CE8-C0A5-E940 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Seoul | D6B0-5421-8F6C | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Singapore | D37C-7DA9-71FA | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Stockholm | 2D4A-B5BA-3AC6 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Sydney | 33FA-EE63-E513 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Virginia | 55CD-B842-ABA8 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Warsaw | D944-D90A-748C | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla A100 GPU running in Zurich | F9AA-5C3E-DD7E | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla K80 GPU running in Phoenix | CCD5-AB33-9CC1 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla K80 GPU running in Stockholm | F80B-3D9E-5D78 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in APAC | 2F01-6004-BE4E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Americas | 7929-334B-6348 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Berlin | D808-F88D-4EB9 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Columbus | 0C7C-4928-2142 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Dallas | F135-3739-68E0 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Dammam | BC32-CEC6-6889 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Delhi | AD32-4326-74CC | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in EMEA | BC3B-5BAC-8EC2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Israel | 9E41-CEC8-4C4C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Jakarta | 807C-B422-49EA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Johannesburg | B87E-401F-15FE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Las Vegas | 8F7D-FD66-412A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Madrid | 0B94-5FED-D396 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Melbourne | 6986-23AE-B1A7 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Milan | 2F2A-BD37-7163 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Netherlands | C6D8-7D97-E282 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Osaka | EA5F-4647-7C91 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Paris | FDC4-AC54-9907 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Phoenix | 185A-A40E-EDC5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Salt Lake City | 044E-8CD0-C9A5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Santiago | C0AD-C0BE-33F6 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Seoul | 003E-D940-4BC0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Stockholm | 6807-7B5F-D325 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Sydney | 39C8-081C-DF5D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Warsaw | 5F68-4141-AB13 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P100 GPU running in Zurich | 34E5-8C3D-5FEE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Americas | A152-C7DF-4872 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Berlin | 2959-5FF9-39BC | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Columbus | 9D4C-6A96-3688 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Dallas | E60A-8961-24B4 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Dammam | 7806-F3B7-834D | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Delhi | 51AE-1484-8A4A | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Israel | 0D62-739D-40FC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Jakarta | 73AB-6EB7-E7C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Johannesburg | 3E61-572B-CB63 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Las Vegas | 1210-C78E-9569 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Los Angeles | 9B0F-5408-AA96 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Madrid | 79A8-9214-784B | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Melbourne | CCED-EFAE-69B8 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Milan | AC16-9DB4-A542 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Montreal | 8A6C-2FC4-90D2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Netherlands | F728-7769-87F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Osaka | 425E-807D-6336 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Paris | A46B-683B-4663 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Phoenix | 493A-5851-FD55 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Salt Lake City | DCDC-A926-A120 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Santiago | 572E-8758-2A88 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Seoul | 07E9-A038-2EDF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Singapore | E9A9-5D7F-DCAD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Stockholm | 0D7A-284B-8350 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Sydney | D758-A272-7887 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Virginia | 7B84-1705-68E2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Warsaw | DBFD-26F6-0BC3 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla P4 GPU running in Zurich | 0C60-5B8F-65BF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in APAC | 8795-7C9F-4FD9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Americas | 88B8-C3ED-03F0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Berlin | 3476-9126-6E83 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Columbus | 81A9-06BC-6E3E | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Dallas | B040-85D2-6B7C | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Dammam | 4A33-560B-929C | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Delhi | C99E-A817-F3BE | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in EMEA | 6FAF-ADE7-FB07 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Frankfurt | 9D8C-EC5C-9714 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Hong Kong | DED3-0A41-A063 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Israel | F54A-065F-435E | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Jakarta | 4FA5-3B69-F7D5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Japan | 01F6-D833-EC61 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Johannesburg | 4E64-C68C-198C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Las Vegas | 2F2B-2B91-EA03 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in London | 9BDF-0244-DB2A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Los Angeles | 8313-8197-C744 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Madrid | FB97-5DAD-C5DC | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Melbourne | 0C36-AFF2-C0F1 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Milan | 3203-7F26-9211 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Montreal | 9A14-2938-353E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Mumbai | 4172-4910-76F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Netherlands | E3F0-571B-0753 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Osaka | 82FA-C194-F7A0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Paris | 3F62-44B1-2596 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Phoenix | B2FB-A134-E005 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Salt Lake City | 7B5F-DED6-5D28 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Santiago | F4CD-E0CD-05FD | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Sao Paulo | 785F-ECAE-DA34 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Seoul | C411-C00C-5370 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Singapore | 589B-0FAB-031A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Stockholm | A0DF-AF58-A415 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Sydney | 1BDD-58A3-A462 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Virginia | 8D8D-649C-0D7F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Warsaw | 63E1-FFD5-0FA7 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla T4 GPU running in Zurich | D32A-6E94-6049 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in APAC | 8D95-C8DB-FC63 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Americas | DC0B-9926-40C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Berlin | D71B-7821-C601 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Columbus | 676F-7CF1-A0BC | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Dallas | F723-B00C-984F | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Dammam | D838-6204-E6F7 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Delhi | 6A8F-97BB-095B | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Israel | 0AC5-C084-1BE4 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Jakarta | 45BF-B232-E095 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Johannesburg | 47AD-5ED1-71DE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Las Vegas | 1A8D-F4F0-7DFD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Madrid | 2EAB-7A86-F27E | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Melbourne | FDC7-5D8E-546D | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Milan | FD5B-093D-2F6D | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Montreal | B0CC-7D0F-CF8C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Netherlands | 0525-CC34-3151 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Osaka | C407-7D46-02CC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Paris | 25B1-0FCE-DD0B | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Phoenix | 2E6B-03DD-F29F | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Salt Lake City | 62C4-2E27-F233 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Santiago | DD37-B7F6-E8CC | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Seoul | BD97-5B65-8B81 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Stockholm | 3CDC-F9B6-FB12 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Warsaw | 630B-D31A-4375 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Nvidia Tesla V100 GPU running in Zurich | 0FC3-E99B-0E22 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Alabama | E481-8B81-9CD9 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Belgium | E1BB-1F26-AEFA | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Berlin | CE5D-05A6-0CF1 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Columbus | E4D3-3D29-ADB6 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Dallas | 72E8-D779-8ADB | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Dammam | D5DC-0863-8266 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Delhi | DB45-8A76-54E5 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Finland | 84A5-32E2-43AA | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Frankfurt | C22D-AC8A-A3F8 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Hong Kong | F819-F391-F518 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Iowa | 785B-24CF-4927 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Israel | 537F-347E-5E08 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Jakarta | A349-77B3-F41D | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Johannesburg | 8692-465A-518D | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in LA | DEA1-8865-5333 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Las Vegas | E82D-0DF7-1502 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in London | A0B0-BC3C-3102 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Madrid | 0F36-547F-FD01 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Melbourne | C3F7-7924-5C87 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Mexico | 83EA-20E8-3DE3 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Milan | A088-3433-7E96 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Montreal | EAF4-406A-AC67 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Mumbai | 9416-1463-A888 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Netherlands | 8C16-5855-FE6E | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in North Virginia | F4C6-C683-1179 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Oregon | BE9C-7816-EE79 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Osaka | 9D69-A7D4-1BBA | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Paris | A7BF-E608-ABC1 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Phoenix | E310-B78C-C352 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Salt Lake City | DCB4-8B97-50F3 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Santiago | 8A19-D6FD-043A | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Sao Paulo | DA6E-C106-CC3C | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Seoul | 88A0-B564-64C5 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Singapore | B4BF-18E0-6CBA | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in South Carolina | 9478-1E13-3FE7 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Stockholm | D258-6250-74A8 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Sydney | DC31-8D63-4B3A | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Taiwan | CF75-30F0-4474 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Tokyo | F50F-DA21-E50F | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Toronto | 8651-4312-6940 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Warsaw | 8216-ECCE-8CFF | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for VM Tier_1 networking performance in Zurich | D620-6DF7-1106 | May 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Alabama | 7543-5E25-4618 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Belgium | 11CB-0AB0-EDA2 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Berlin | 550B-4904-C10F | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Columbus | 7542-50A5-2AD9 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Dallas | CC5F-F394-2BD9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Dammam | 7CCB-2DC2-2E93 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Delhi | 82BC-FAA5-DEE0 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Finland | 0FF3-EE57-4402 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Frankfurt | 1406-8906-2A47 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Hong Kong | 0749-2E54-AE81 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Iowa | 0141-0887-121B | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Israel | EFC5-5901-1B4D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Jakarta | 0701-5E7C-96DC | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Johannesburg | 1599-A2EA-2B54 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in LA | 049D-BD79-CA11 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Las Vegas | 048E-C391-D5B4 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in London | 12FF-8EC8-6959 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Madrid | D2D2-5ACA-D38E | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Melbourne | F325-C5CF-6E90 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Mexico | 89E0-4943-A548 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Milan | C187-2A42-7E96 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Montreal | 0679-BAD1-BA3A | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Mumbai | 0D93-BE26-7BF1 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Netherlands | 1297-1FB8-DFAF | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in North Virginia | 0388-AFDD-BC41 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Oregon | 0276-F5FF-20B7 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Osaka | 0989-733D-FE9C | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Paris | BA56-C352-2429 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Phoenix | D45E-4F71-8B8E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Salt Lake City | 04DA-5FD5-1AD0 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Santiago | EB18-FCCD-0961 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Sao Paulo | 0698-341D-E3A7 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Seoul | 0D13-D3CF-7E11 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Singapore | 0DD5-ABF0-A3D0 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in South Carolina | 01D5-1AF1-FD83 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Stockholm | 8257-9BBF-6D27 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Sydney | 0FEE-F4C7-B278 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Taiwan | 0F56-9CF7-3DB3 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Tokyo | 0881-5CBC-2768 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Toronto | 8797-B511-7512 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Warsaw | B57F-418A-733B | February 20, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 100 Gbps in Zurich | 15D6-AE4D-A43F | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Alabama | 7490-BCD7-88E6 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Belgium | 39E9-42B6-2A9A | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Berlin | 3778-9F70-D31B | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Columbus | 8196-4F9E-ED00 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Dallas | CB07-5CD3-8A69 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Dammam | 9909-93D0-9809 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Delhi | D02B-2EFF-5440 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Finland | 3859-116A-1A54 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Frankfurt | 3AEE-AF87-9C47 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Hong Kong | 33A2-CD70-8193 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Iowa | 2A90-489D-6213 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Israel | F131-5CD3-EC4D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Jakarta | 32F0-43E1-0E87 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Johannesburg | 57A1-6EC5-2A62 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in LA | 313B-1A80-3C02 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Las Vegas | 3102-7863-890C | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in London | 3AE3-CD38-53E1 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Madrid | A7B4-946B-BC9D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Melbourne | D6FF-DB6A-CEF1 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Mexico | 078E-4C71-CA5E | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Milan | 78D1-1F07-C230 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Montreal | 317C-A828-C3DC | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Mumbai | 355D-4C52-23F7 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Netherlands | 3A5C-0B37-4568 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in North Virginia | 2E7E-AF89-B0EB | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Oregon | 2B35-ED6F-C1E6 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Osaka | 33FB-9658-A3E9 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Paris | E232-8C2B-C34F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Phoenix | FB0B-50B7-C1C4 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Salt Lake City | 3143-706D-D1E3 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Santiago | 735C-4C8E-B41C | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Sao Paulo | 31A3-FCBF-8A48 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Seoul | 3509-C211-2F75 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Singapore | 35CC-357E-E28F | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in South Carolina | 2AE4-F045-3343 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Stockholm | 4730-9BE2-AF5D | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Sydney | 3799-8BF0-1319 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Taiwan | 3774-2460-5BF3 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Tokyo | 33F8-C644-BB7C | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Toronto | C242-9422-F3B0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Warsaw | FDC9-DC9B-7E99 | February 20, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 50 Gbps in Zurich | 3B77-9AA1-14E4 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Alabama | 9EA3-91F2-D5F2 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Belgium | 2817-2AA5-3623 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Berlin | 7D3D-6FEC-8C95 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Columbus | B151-71CA-9370 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Dallas | 74C8-3537-7BE2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Dammam | DCD6-2FB9-931A | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Delhi | DF1C-123D-662F | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Finland | 27CC-A46B-040B | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Frankfurt | 298A-90B3-E8ED | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Hong Kong | 20EA-6806-88A0 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Iowa | 178F-2106-76D1 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Israel | A1F4-07E2-57D1 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Jakarta | 1F28-FAB4-69B3 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Johannesburg | 7FE8-7B38-5305 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in LA | 1BA3-FEA6-9935 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Las Vegas | 195D-0D00-112D | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in London | 291D-81E9-13BA | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Madrid | 7931-14C8-4C30 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Melbourne | B959-6AFE-B28C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Mexico | BB36-4550-9C24 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Milan | FA36-27C0-5AED | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Montreal | 1CE1-9033-0BF3 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Mumbai | 258A-E45C-FD8F | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Netherlands | 282D-2A1C-EFDF | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in North Virginia | 1861-0599-86A0 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Oregon | 17F3-BD7C-8BC1 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Osaka | 230F-8710-5F12 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Paris | 81CD-DF8F-9DB5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Phoenix | 7B9B-F546-50E5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Salt Lake City | 1C0D-65C6-5C7D | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Santiago | CBBE-3275-51B8 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Sao Paulo | 1E5A-7DF7-19BD | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Seoul | 2570-E0F8-59BE | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Singapore | 2652-B9A5-EA87 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in South Carolina | 17D0-0D70-1C74 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Stockholm | 8065-807D-47AE | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Sydney | 27CA-C049-F1F0 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Taiwan | 279F-5CFB-0CA2 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Tokyo | 228E-C12D-B213 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Toronto | EC74-6AF3-6A54 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Warsaw | EA16-8EE5-6F53 | February 20, 2021 |
| Compute Engine (6F81-5844-456A) | On-demand fee for total VM network bandwidth up to 75 Gbps in Zurich | 2A27-ABEA-BE00 | January 12, 2021 |
| Compute Engine (6F81-5844-456A) | PD IO Requests | 511D-B8D3-979E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity | 0FE3-CAB9-E7E3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in %!(NOVERB)%!(EXTRA string=Madrid) | 76E1-A0DB-0F9B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Alabama | F082-33C2-E2CC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Berlin | F0B8-3C68-F270 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Columbus | 35EE-438A-F578 | November 19, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Dallas | 1055-0391-7EEC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Dammam | 7916-05F5-B57F | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Delhi | E7A1-8555-5463 | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Finland | 3CF7-D7C4-C23D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Frankfurt | 38EB-8FFB-BAA7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Hong Kong | A18D-2E7B-A3D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Israel | A72E-DFA9-08E7 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Jakarta | 57ED-BC47-D2CD | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Japan | F80E-BEC6-B2DF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Johannesburg | DA42-2123-4782 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Las Vegas | 1541-CBF0-F0D1 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in London | 933D-9C8E-8F1A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Los Angeles | 3CBF-D399-77F9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Melbourne | 57E4-5F01-AC73 | June 20, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Mexico | CFC6-AEDE-DE17 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Milan | F8CB-EFE8-BC0B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Montreal | 399B-1D2C-F2FB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Mumbai | 71CB-F908-13D7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Netherlands | 70E0-08DF-FFFF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Osaka | A43F-3958-6068 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Paris | 3FF4-FF4D-5E9C | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Phoenix | 5CF7-67D3-6B0C | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Salt Lake City | 10BF-0144-69AB | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Santiago | 876A-CFAA-CB73 | September 9, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Sao Paulo | BA37-067F-16FF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Seoul | 4EA5-4AC4-9DA1 | July 29, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Singapore | BB09-D9FE-73FD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Stockholm | 7F4D-B213-86C2 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Sydney | 5A07-33CA-3930 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Toronto | 5DE9-E8EC-04C1 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Virginia | EE8D-A62C-DB40 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Warsaw | 523A-5B2A-EBF0 | March 18, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Balanced PD Capacity in Zurich | 92EA-B621-50A6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity | AC33-821B-43FA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Berlin | 0542-29EA-8C93 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Columbus | 908C-9640-F5BD | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Dallas | 097E-E441-25D8 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Dammam | 191B-C0B3-97F2 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Delhi | A5CA-5004-F2F7 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Finland | 88F5-6FF8-8B0B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Frankfurt | 9FA0-CE24-170B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Hong Kong | F014-62E9-0185 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Israel | 4AAD-F700-3974 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Jakarta | F3C4-5282-C9E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Japan | CF93-C971-8DA8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Johannesburg | 4A9E-5877-B916 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Las Vegas | 6D08-CB34-F7C3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in London | B65A-20D9-AE15 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Los Angeles | 14FF-BB6D-E96F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Madrid | 7756-EAAB-BBD6 | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Melbourne | 8BD4-C274-AE22 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Mexico | 6BE4-4307-E8C7 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Milan | 161C-8608-BAD0 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Montreal | D8FA-CC35-8E90 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Mumbai | 3311-200B-5973 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Netherlands | 9055-56FA-0728 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Osaka | E3CD-5C37-A50F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Paris | EB7F-CA49-E749 | February 6, 2022 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Phoenix | 1E75-0950-83EE | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Salt Lake City | 173F-F443-D208 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Santiago | 7C63-1C76-0056 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Sao Paulo | 9FAE-9C45-7A4D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Seoul | 7D98-C190-0D98 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Singapore | 6EF9-716A-B2AF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Stockholm | 2368-59BA-736B | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Sydney | 43F0-D7DA-75E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Toronto | F947-D8B5-2CD9 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Virginia | A917-E605-0652 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Warsaw | 2F57-9E0E-CB5C | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Regional SSD backed PD Capacity in Zurich | 1EC6-CB54-E0D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity | 3C62-891B-C73C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Berlin | 0A63-CEC3-4786 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Columbus | 7348-F926-828E | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Dallas | 0640-2039-151E | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Dammam | A112-85DD-0C20 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Delhi | 2CA8-051F-8A9E | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Finland | 7F69-8BA2-E71C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Frankfurt | 31D1-FBD8-16DD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Hong Kong | 92AD-0FBB-AC7C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Israel | A2ED-E0D3-E9DF | September 14, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Jakarta | BEB2-8F93-E108 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Japan | 8914-A21F-7C98 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Johannesburg | 6A49-499D-3637 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Las Vegas | 6676-5994-E362 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in London | 5712-0053-D059 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Los Angeles | 878F-E2CC-F899 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Madrid | AC03-269C-7B3F | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Melbourne | A68E-93F3-1697 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Mexico | 84FA-3E1B-C4B5 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Milan | 2A47-3993-F49D | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Montreal | AB22-513F-E199 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Mumbai | 6AA8-A6A7-C242 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Netherlands | 8E50-26E0-D2A3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Osaka | EE4F-E9A2-F8D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Paris | 2E13-145F-DCF7 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Phoenix | 0147-261B-2D11 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Salt Lake City | E39F-3A27-653A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Santiago | 7D15-6B1E-66E0 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Sao Paulo | 9669-9A29-FF5E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Seoul | 2269-4F0C-C04C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Singapore | 55C0-508F-9F7F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Stockholm | B7C7-2311-85E6 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Sydney | EE4C-7786-1B0B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Toronto | 89D7-9706-41E7 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Virginia | D60B-2646-1A2B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Warsaw | 839B-DD1D-C319 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Regional Storage PD Capacity in Zurich | A6C5-05F9-15A1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage | 62AF-A39E-269B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs | E725-3CC5-D4BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Berlin | B567-2F84-A5EB | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Columbus | BB2A-ADC4-1CE7 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Dallas | 5C0D-18AB-BFFF | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Dammam | 9E3E-CEDB-29B5 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Delhi | FE93-436C-9336 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Finland | DA22-3FD3-263D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Frankfurt | 32CD-69B6-F8EE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Hong Kong | 098E-5D71-3E4F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Israel | FF56-6725-25EB | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Jakarta | 83B7-9808-C27B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Japan | 7417-69E6-DF0B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Johannesburg | 64C3-AF0B-D8C1 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Las Vegas | 9FE8-2651-76C8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in London | B67B-2DCF-21FD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Los Angeles | 7A48-277E-AD1A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Madrid | CC5B-D18C-BE5C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Melbourne | A52E-79DC-38B3 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Mexico | DBEF-1F4C-D1E7 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Milan | C0BB-E690-035D | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Montreal | DF06-F3BF-ECF5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Mumbai | 5E37-B87E-96FA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Netherlands | 8D0B-EA58-9E35 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Osaka | A278-3398-C70D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Paris | C53F-F7C0-F2E9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Phoenix | 3241-18CC-10C8 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Salt Lake City | 3233-97D3-222E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Santiago | 8286-C67C-AB6B | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Sao Paulo | A84C-D70F-4BAF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Seoul | 129E-F19F-D852 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Singapore | 9F7C-3C75-F39B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Stockholm | 3E22-5656-C855 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Sydney | D3E7-D583-8ADB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Toronto | D4CC-1D5D-129C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Virginia | 90BB-573D-32B7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Warsaw | 98E9-EFA0-07CD | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage attached to Spot Preemptible VMs in Zurich | D4D6-A260-1324 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Berlin | 91C8-B203-BE6C | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Columbus | 8ED3-158F-74D8 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Dallas | 5AE0-B39A-67F5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Dammam | 6CE3-6622-2DCE | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Delhi | 7F19-C397-10F5 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Finland | 42BD-4C76-86B9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Frankfurt | 0D18-A9AA-6DB3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Hong Kong | 36DD-0D48-1538 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Israel | 8A85-D697-B932 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Jakarta | E4E8-72A1-292F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Japan | ADED-CD91-C56C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Johannesburg | 138B-0046-2B0C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Las Vegas | 3C20-2B95-CA0D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in London | 2CF6-3A15-7BB0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Los Angeles | D77E-1723-8B31 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Madrid | 0DB2-6C00-5A44 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Melbourne | 3091-273A-7294 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Mexico | 0AFF-F793-94F8 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Milan | 0244-44E9-C1CE | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Montreal | 6188-5783-3621 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Mumbai | 5358-4869-64C1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Netherlands | EFD6-4D88-8C94 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Osaka | A092-0DE4-8657 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Paris | 8D1E-DEFB-CA72 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Phoenix | 1994-7A63-0D30 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Salt Lake City | C6F5-905B-AD47 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Santiago | 7C00-0282-DC9F | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Sao Paulo | A8D6-A5F2-1558 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Seoul | 3D6B-D4C7-3AE9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Singapore | F8F1-D370-6212 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Stockholm | BAC6-D3FF-B41C | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Sydney | 5A46-0D37-14AA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Toronto | B7F4-7E22-BB08 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Virginia | 1B8A-BA6B-7FB6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Warsaw | AF8B-3054-316D | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed Local Storage in Zurich | F126-3695-DA84 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity | B188-61DD-52E4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Berlin | E1DD-8C26-9FB1 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Columbus | 0E37-3202-AA60 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Dallas | DBD1-66F6-9AFE | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Dammam | FD9B-C1DF-0EFF | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Delhi | 9005-FE6E-75FC | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Finland | 4C09-1F46-D168 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Frankfurt | 378C-9DAC-0A5A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Hong Kong | 6630-F40F-B38F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Israel | 4089-1AA6-A0CC | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Jakarta | 0554-F9AE-1EC6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Japan | 704E-4991-FEE8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Johannesburg | 695F-24A0-9B21 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Las Vegas | CF9E-3EFB-D09B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in London | 4D98-E205-E7F1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Los Angeles | 0589-AA00-68BD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Madrid | AF44-A7D7-A86B | February 8, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Melbourne | 140F-20DA-4493 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Mexico | B67F-A0BB-5D1C | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Milan | 85A8-4AC6-02EC | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Montreal | BA5B-E860-74C4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Mumbai | FF66-41CB-DE90 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Netherlands | 315D-05CC-A75E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Osaka | 0415-E569-EE65 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Paris | 0BBD-3452-19A9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Phoenix | B4A0-3827-786D | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Salt Lake City | 6A0C-F783-3754 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Santiago | 8286-0347-E4E8 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Sao Paulo | 28F9-6E36-3030 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Seoul | 2C69-A050-09F7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Singapore | C97A-896E-D6F0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Stockholm | D8BB-1B57-00B2 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Sydney | B2B0-B94F-6690 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Toronto | B820-EC1B-EE69 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Virginia | 75B0-B95E-76A8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Warsaw | 8C12-DA07-FA3C | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | SSD backed PD Capacity in Zurich | 6B82-25FC-503C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in APAC | 1195-456B-30CB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Americas | 82AF-89FC-240D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Berlin | DD0C-5778-9EAB | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Columbus | 8B47-1037-41C1 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Dallas | A900-B5F6-7090 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Dammam | 4FFD-09DF-F174 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Delhi | E041-9328-B919 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in EMEA | 0DA7-1812-F2F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Finland | B2A4-8867-D246 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Frankfurt | 7BDC-D342-257A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Hong Kong | 45FF-A00E-2272 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Israel | 62FC-E25A-C284 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Jakarta | 127F-3618-DB61 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Japan | 07E8-C8A3-A331 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Johannesburg | AEB4-2466-CBBE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Las Vegas | A12E-2B48-A58C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in London | 6D07-090C-335C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Los Angeles | 9DCB-8EF5-064E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Madrid | F75E-4DBE-5B8D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Melbourne | A633-AF98-6164 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Mexico | 1B62-3E28-F687 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Milan | AD4A-3B30-7E7B | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Montreal | 86E6-573F-448F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Mumbai | 7F4C-6834-45E0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Netherlands | 8054-75A6-85C3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Osaka | 0341-0ADC-3AA8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Paris | 8B7B-8052-CB3A | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Phoenix | 27B5-DE60-C2ED | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Salt Lake City | E27F-2A30-ACED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Santiago | C7F3-8FCF-6D55 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Sao Paulo | 2A24-2BF1-650C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Seoul | 0623-BE6D-3CEC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Singapore | F8F4-3E2C-A4B2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Stockholm | CB08-4A31-2A67 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Sydney | FBCF-0A11-DCA0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Toronto | 9C63-82F2-4C15 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Virginia | B736-1B84-BD10 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Warsaw | 6CEF-0286-27BE | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Small Instance with 1 VCPU running in Zurich | EAFF-C2C8-0B73 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in APAC | 94A3-E7C0-40C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Americas | 5B9B-3A78-9B7E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Berlin | 674E-9E57-CA1C | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Columbus | 7990-53DC-9A86 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Dallas | E5C9-DB0E-82EE | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Dammam | 86F5-CCD9-A2AC | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Delhi | 03BB-D384-6E02 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in EMEA | 1D7D-A195-292F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Finland | 49F3-90BD-CFC2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Frankfurt | 2E05-4E2F-331E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Hong Kong | 7BB1-5B6A-7B91 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Israel | 3FFE-BDAE-1EEF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Jakarta | 518E-F821-E475 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Japan | 11E2-1250-E9DF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Johannesburg | 8B14-A8F9-9239 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Las Vegas | 78E5-42FC-30D3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in London | D6A9-7E85-4D7A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Los Angeles | CF5D-FF04-4AF8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Madrid | 3C44-C4AD-F604 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Melbourne | 851C-8803-A84F | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Milan | 2EDB-817E-7F94 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Montreal | 03F5-9C25-8429 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Mumbai | 709E-D9A5-1ABF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Netherlands | 7EFD-BE8D-9E97 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Osaka | 2C5E-7FD3-8A92 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Paris | 2628-D72A-AF3A | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Phoenix | 9B89-4BC5-276C | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Salt Lake City | 905C-EE06-904B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Santiago | E642-E94F-4CF2 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Sao Paulo | F7DE-AF3B-9E08 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Seoul | 1E02-469E-1043 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Singapore | 66E8-F5BC-F1A1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Stockholm | D6E9-5FF9-9CB4 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Sydney | 7BC0-A963-76FB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Toronto | 9DDE-C50E-65A0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Virginia | E72B-7EA0-585E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Warsaw | 84ED-DFA2-EC4D | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Core running in Zurich | 0906-EB78-2DF3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in APAC | 46C9-D0A3-7776 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Americas | 6E71-F57E-F646 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Columbus | 6269-C980-3EA4 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Delhi | F715-D5CD-A983 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in EMEA | B9D6-CCA7-B823 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Finland | E72C-D624-7044 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Frankfurt | E702-E5DB-2B53 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Hong Kong | 858A-E374-92E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Jakarta | 0026-A923-AA09 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Japan | DA6A-8915-BD65 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Las Vegas | E75E-6149-8E8E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in London | 3088-FE20-FB9E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Los Angeles | 2787-E4E6-47C7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Melbourne | D434-8186-CEA9 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Montreal | 366C-94AE-77A9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Mumbai | FFCE-ED5F-818E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Netherlands | 17DC-172A-BC1B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Osaka | 42D2-FFFC-CB09 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Salt Lake City | 6C50-D4BA-77E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Santiago | F434-33C6-05F7 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Sao Paulo | 4B1F-E781-AC83 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Seoul | 6C71-07E1-9598 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Singapore | 811F-7613-0D41 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Sydney | B99C-E93C-AB81 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Toronto | 0D56-565D-4D15 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Virginia | C3B9-E891-85ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Warsaw | 1FCB-F3B8-FB43 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance RAM running in Zurich | E3FC-C332-8647 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Berlin | 22CA-EA7E-7AD3 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Dallas | AF99-974A-739F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Dammam | F63F-22C7-70F3 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Israel | 7439-B61B-2319 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Johannesburg | 33DB-3B66-132A | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Madrid | 3DFD-2F55-22E2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Mexico | 7D5F-221E-1A87 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Milan | 2210-DA1B-8A2D | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Paris | 91CE-A3F1-AB4C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Phoenix | 4104-7A93-945B | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Instance Ram running in Stockholm | 3A12-BBD3-6140 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in APAC | 9BA4-69EA-899C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Americas | B27B-84EF-C49C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Berlin | BC06-F361-2307 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Columbus | D0CC-3B9A-9B99 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Dallas | 3783-8692-787D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Dammam | 0262-1E1D-FBA0 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Delhi | 773C-E06C-7A2F | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in EMEA | 63C0-52D3-45CF | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Finland | 9C3D-F6B7-DE5D | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Frankfurt | 3CDF-D0A5-EA0C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Hong Kong | 1A2F-12A1-13CB | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Israel | DBB7-1E9F-AD97 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Jakarta | 3004-6B57-7C01 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Japan | DE7D-99D7-83EE | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Johannesburg | 9A82-A9A2-C89C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Las Vegas | C214-93F8-082C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in London | 2773-F774-7EA2 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Los Angeles | E7E3-2054-ED2C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Madrid | AD6B-BBA4-82F9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Melbourne | 0427-3F6B-DDE0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Milan | 42F6-E777-B36F | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Montreal | 8057-E23B-167A | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Mumbai | A8EC-F360-E0E9 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Netherlands | E3F5-7971-68E4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Osaka | E136-9454-C296 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Paris | 53D7-7328-1A61 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Phoenix | 2D76-5F4B-66E7 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Salt Lake City | 5872-0333-02D4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Santiago | B961-497F-984D | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Sao Paulo | EE0D-CDEB-2BD1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Seoul | 2467-642B-F221 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Singapore | 4D1C-9015-1B79 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Stockholm | F397-1693-A2A0 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Sydney | 4CFF-1564-D757 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Toronto | 2D79-5098-ADD0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Virginia | 47C6-C9E1-0B16 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Warsaw | C390-DB22-5AE2 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Core running in Zurich | 6978-2AB0-97AD | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in APAC | 47DD-9034-97D1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Americas | 7E17-EBF5-EF56 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Columbus | 0045-5AC3-AD6E | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Delhi | A108-04FC-7B42 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in EMEA | 0548-989A-A3A4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Finland | 3C31-7322-35F6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Frankfurt | 2677-2806-5279 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Hong Kong | F7CE-0C5A-5A5B | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Jakarta | BE53-9406-5C6F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Japan | AB91-5BCA-C4C3 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Las Vegas | BD41-6274-A220 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in London | B816-2A2C-E577 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Los Angeles | 61FE-0EE5-53A6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Melbourne | F1FB-6775-0915 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Montreal | C06D-A471-7494 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Mumbai | F8AF-05BF-770F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Netherlands | FA72-B53B-7C8F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Osaka | 26F0-1B5D-A8CF | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Salt Lake City | B042-DD83-3640 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Santiago | DE55-1128-B4FB | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Sao Paulo | 2E06-07E9-1E18 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Seoul | 63B6-FB4D-C196 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Singapore | 803C-F19F-F49D | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Sydney | D05B-2007-58E1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Toronto | E779-686C-AE7F | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Virginia | DC93-F9B4-AA66 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Warsaw | 1197-463B-F663 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance RAM running in Zurich | 6E7C-B990-49E0 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Berlin | FDE0-5FAA-85C1 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Dallas | 5534-C1FB-970D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Dammam | 9A95-780D-62F1 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Israel | 91DD-AF76-0893 | June 15, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Johannesburg | DD22-23F3-4322 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Madrid | 5333-41C0-CFA6 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Milan | C44B-5242-E2A6 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Paris | 256A-181A-365D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Phoenix | 9C38-FB0A-3482 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2 Sole Tenancy Instance Ram running in Stockholm | 133C-5096-7321 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in APAC | A0A3-DFC6-2346 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Alabama | 64DB-B71C-50B1 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Americas | 5D0A-9A49-53E1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Berlin | 0F4C-7714-8643 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Columbus | F31E-CDFB-6F7E | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Dallas | A1AC-111E-36A3 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Dammam | 5601-F8E9-07FE | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Delhi | E24F-6921-C32D | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in EMEA | F7C5-AF6B-DC41 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Finland | CD8E-4A80-5E05 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Frankfurt | DFFE-6B3D-AF61 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Frankfurt West | 6BB6-C171-7574 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Hong Kong | 6262-6286-F1E0 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Israel | 53F5-FA54-D55C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Jakarta | EFFC-190F-C2E3 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Japan | C988-A4AC-E44C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Johannesburg | F776-A177-C7F3 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Las Vegas | 8661-7DD2-D278 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in London | 3644-1F25-4E91 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Los Angeles | F5C6-3BB1-05C6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Madrid | 4361-6C48-53B7 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Melbourne | B531-019E-CE51 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Milan | D701-E1EC-8701 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Montreal | 1883-DFEA-0CAF | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Mumbai | 68D7-5756-D3A0 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Netherlands | A92E-7119-CC37 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Osaka | FD94-BA7A-A88C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Paris | 7769-F411-B74D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Phoenix | EB30-2A9E-E595 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Salt Lake City | F103-8E41-D3E6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Santiago | E035-E6CC-F437 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Sao Paulo | D332-33A1-48A1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Seoul | 8272-21A6-75BE | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Singapore | 062E-55FF-FFBF | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Stockholm | FB7F-8EB2-1705 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Sydney | 36BE-A07A-58DB | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Toronto | 404A-C2CD-F70F | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Virginia | 6090-BD73-00C5 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Warsaw | 428A-1C8F-B009 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Core running in Zurich | 4396-86D9-1988 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in APAC | 4E5A-F312-0C94 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Alabama | CBC8-481E-5F67 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Americas | F514-C51F-FC35 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Columbus | 88DB-1403-5A8C | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Delhi | E365-038E-C864 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in EMEA | C8DA-3BFF-C3C6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Finland | 5D12-BD35-5E85 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Frankfurt | FD97-3C0F-5DDB | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Frankfurt West | 84D9-5D4B-A902 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Hong Kong | B19B-FFCC-A795 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Jakarta | 30B1-9DF9-E31F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Japan | 3FB5-27D8-4A0A | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Las Vegas | 9DC9-C6DF-AD3C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in London | 699F-788F-E349 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Los Angeles | 9750-15B4-12A9 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Melbourne | 5F72-9A3F-921E | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Montreal | 8D16-F2CD-30C7 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Mumbai | 27F7-3926-3BB0 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Netherlands | 69C7-4B14-D45E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Osaka | 88E9-C6DE-700E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Salt Lake City | E85F-D393-3F18 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Santiago | BADB-645A-843A | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Sao Paulo | 94A3-5AD6-7795 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Seoul | 2677-18FE-2CE7 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Singapore | 85BC-66F2-1921 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Sydney | 1E9F-42B4-AAD4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Toronto | 8D7B-D3B0-342F | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Virginia | C1D5-2F2F-37A4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Warsaw | 11D2-BFA9-7C9B | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance RAM running in Zurich | 9F65-0833-DC38 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Berlin | BF6D-724F-305E | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Dallas | 70E2-AA46-5CC0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Dammam | 3D5A-9195-1C77 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Israel | 3BEE-726B-0ED8 | June 15, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 90A3-BE7F-92B6 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Madrid | 122A-BBE5-D7F0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Milan | 0C3A-BA88-3C4C | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Paris | 6CA4-9ACA-24BB | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Phoenix | 9F85-9FBA-3334 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for N2D AMD Sole Tenancy Instance Ram running in Stockholm | 0F8D-4E8C-F524 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in APAC | 04CD-0AE0-317F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Americas | A682-623B-A1A2 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Berlin | 5158-F217-AAA6 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Columbus | 63E2-F46B-8C1F | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Dallas | B7EA-09B7-9CB1 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Dammam | B08A-BF44-EEA4 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Delhi | 0D36-D0D1-665A | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in EMEA | F93F-E8A3-E9E4 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Finland | 3339-2735-6C1B | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Frankfurt | CE35-9642-C8BB | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Hong Kong | 73EB-2C68-BC62 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Israel | CCEE-0DCA-CBEA | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Jakarta | 1CA9-7389-91EA | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Japan | 9E48-7FBE-B9BC | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Johannesburg | E344-29C7-E6F9 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Las Vegas | 05AF-21D6-ADF6 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in London | DDB1-42A3-A20E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Los Angeles | CF37-6E67-26BD | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Madrid | D778-16BD-9FF2 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Melbourne | 63F8-253C-E7A0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Mexico | 3D74-129B-2063 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Milan | BA96-F76E-AC1F | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Montreal | 326D-987B-9586 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Mumbai | 485E-6F4A-A23F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Netherlands | 417F-D56F-9E0E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Osaka | C7E1-7A00-151E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Paris | 4107-050E-AFD4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Phoenix | 736B-5A0B-DA26 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Salt Lake City | 70FA-B9C5-158F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Santiago | B795-6BCF-F78C | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Sao Paulo | 2123-DA8F-329C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Seoul | 8D7F-284E-7FCF | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Singapore | 84A3-CBE9-206E | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Stockholm | E227-5BF1-F3B4 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Sydney | 8E03-6E6E-3B65 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Toronto | 9CBA-D5AD-529B | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Virginia | 63DD-4898-88E5 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Warsaw | 2F56-F590-2771 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Core running in Zurich | A5B3-1440-AB29 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in APAC | 9C19-589B-7BF9 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Americas | 2CCA-3D67-B582 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Columbus | 8AF0-3B5B-22E8 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Delhi | 5DF4-4D83-6278 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in EMEA | 2B3A-689E-5DF3 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Finland | 32BE-CE09-EB94 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Frankfurt | CE9D-572D-263C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Hong Kong | 734F-D45B-50E1 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Jakarta | 8D81-8A51-A398 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Japan | 5BDC-660F-B36B | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Las Vegas | 29F2-5503-6AFD | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in London | CE3E-6CCC-6F52 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Los Angeles | A56D-B2A4-935D | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Melbourne | 412F-9780-2552 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Montreal | CC2C-FF40-CC7F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Mumbai | 79BD-B132-71CA | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Netherlands | AABF-0107-9D98 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Osaka | 6172-E23D-912F | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Salt Lake City | C4AC-FA70-2BFC | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Santiago | B5A8-9C69-A0F4 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Sao Paulo | 6E22-ADDE-570C | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Seoul | C2C0-A375-59F2 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Singapore | 4835-E708-0B90 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Sydney | 2C5F-A378-7211 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Toronto | 7D42-5CE0-6A1C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Virginia | 633E-C1E6-2E12 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Warsaw | 7BA1-11F8-A4AB | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance RAM running in Zurich | A470-7C0E-8BD7 | July 9, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Berlin | 6EC3-8EDC-F8B6 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Dallas | BCEC-0209-9322 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Dammam | 22E6-004A-B62E | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Israel | ED07-1A6C-CD6E | June 15, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Johannesburg | 8A19-F1A1-2FD3 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Madrid | 5C24-0930-2DBC | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Mexico | 5E6B-533D-8981 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Milan | 2278-C90A-5F43 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Paris | 4D73-012C-384D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Phoenix | 39CD-CCDD-335A | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Overcommit Premium for Sole Tenancy Instance Ram running in Stockholm | F036-3CBE-EA32 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in APAC | 0C3B-CF3D-F861 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Americas | EA35-7120-E701 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Berlin | D63F-F37B-AB81 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Columbus | 8CE0-F2A0-6A3B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Dallas | B401-F654-7DB7 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Dammam | 02B1-C5A4-F964 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Delhi | 099A-D303-2196 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in EMEA | 9745-CA03-7EF9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Finland | 04CD-41AB-C4D1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Frankfurt | A20C-D15B-5702 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Hong Kong | 68C2-DDD3-CDD7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Israel | CD77-D9CA-D640 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Jakarta | 431E-A3D9-404A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Japan | 38BA-C96D-1083 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Johannesburg | 98F3-31F7-E336 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Las Vegas | 065C-EF92-4F9B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in London | E729-A855-5D73 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Los Angeles | 5070-7031-CE38 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Madrid | 9896-261E-D181 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Melbourne | 4E62-5AD6-900E | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Mexico | B543-526E-C7EA | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Milan | 6143-1968-B411 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Montreal | E8E9-FD8B-22E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Mumbai | 3CAB-18C6-84E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Netherlands | 529C-CFC8-C3D5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Osaka | ED41-2BD1-E2BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Paris | 5A36-F6E3-46E8 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Phoenix | 3654-986A-9386 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Salt Lake City | 9A9F-6545-2EAF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Santiago | DD84-98C5-0C45 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Sao Paulo | 7ABA-1623-56DC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Seoul | C0FE-995C-45C4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Singapore | B906-2373-C992 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Stockholm | A284-BDC9-0924 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Sydney | D38D-BE8B-622F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Toronto | 49A9-46C5-20F0 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Virginia | 051A-1A60-0023 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Warsaw | CD64-0465-AD1E | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Core running in Zurich | C49A-FF11-020E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in APAC | 7779-B44A-723B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Americas | 5761-5430-297C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Columbus | E437-B97F-BB0D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Delhi | B30F-03AF-AFF2 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in EMEA | C29C-FD34-084C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Finland | EA23-2666-CC17 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Frankfurt | 2382-D211-C9E6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Hong Kong | 45D3-0812-6895 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Jakarta | C541-5227-482E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Japan | 4BDA-3DB1-301D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Las Vegas | D29E-58D9-4D28 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in London | 5279-8779-B590 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Los Angeles | 78D3-D9F3-94BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Melbourne | 296A-EFF1-6A71 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Montreal | A4F9-4BAB-32CD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Mumbai | 5EDA-1230-CC07 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Netherlands | C936-3554-BCA7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Osaka | CDD4-6439-A038 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Salt Lake City | B2D3-2720-5DA6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Santiago | E963-316D-1305 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Sao Paulo | 20F8-51A7-297E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Seoul | 09EF-98D1-DB69 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Singapore | 3046-21CA-3C13 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Sydney | 00A1-6CCF-3DF0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Toronto | AAD0-230F-9715 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Virginia | 04F8-7B39-1826 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Warsaw | 6FF7-16C1-B33C | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance RAM running in Zurich | 7593-8E8D-056E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Berlin | 01F8-ED89-0FFD | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Dallas | 94AE-B348-E880 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Dammam | 4182-01EE-155F | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Israel | F6EA-08E6-5345 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Johannesburg | 0C16-A20C-4552 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Madrid | DAD6-803C-52CC | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Mexico | 3164-C8A7-5D7C | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Milan | 73C7-CD26-D7C8 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Paris | BD2D-AC82-5C10 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Phoenix | E03B-0239-17D5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Compute-optimized Sole Tenancy Instance Ram running in Stockholm | 15FF-6978-80CB | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Americas | 6E91-C887-FE45 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Belgium | C525-ADA9-FB8A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Berlin | 1FC8-22CC-128D | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Columbus | 5E53-F717-84C4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Dallas | 7647-19EB-C92F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Dammam | 8DCC-FF57-358A | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Delhi | 7520-A60B-5E3D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Finland | 2F94-EAA8-C20B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Frankfurt | 64C6-6C44-1D58 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Hong Kong | 182A-9364-0A26 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Israel | C2EC-9A03-6850 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Jakarta | F9C9-B2AD-8453 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Johannesburg | 4926-5349-72C0 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Las Vegas | 9031-2230-C760 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in London | 3CEE-91C8-0C2D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Los Angeles | 17F6-8D36-A21A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Madrid | 7155-E4F9-FB58 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Melbourne | 6FE0-F905-9A76 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Milan | 1F29-0BA5-D5A3 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Montreal | 24FC-3B16-A2BC | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Mumbai | 76E0-0CB7-848A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Netherlands | B506-6FB7-2DCB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Osaka | CDCC-9B44-38C3 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Paris | 75E9-0610-17EA | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Phoenix | 60E6-EBB1-6136 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Salt Lake City | 8695-91D8-8A0F | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Santiago | 41AE-AC27-D9E9 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Sao Paulo | 5841-2B94-5B25 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Seoul | 8273-1E5A-7D81 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Singapore | 9639-B5D8-AD15 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Stockholm | 84F4-A5C4-4487 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Sydney | CDAD-F186-B420 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Taiwan | D26D-518A-3EB7 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Tokyo | 9876-EADC-2ABE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Toronto | A223-F7B5-B93A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Virginia | 6941-8BD7-5B60 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Warsaw | 8343-A6C7-926B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Core running in Zurich | EB39-10EA-EE51 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Americas | 3BB3-5414-089B | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Belgium | 0184-BDB4-70EE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Berlin | B9AD-CA7F-86C1 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Columbus | 8653-3CB2-C866 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Dallas | 675A-7520-7D68 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Dammam | 8074-F157-7F8E | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Delhi | F09E-AD4D-A41E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Finland | 49ED-362B-0968 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Frankfurt | 5427-F77A-5C5A | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Hong Kong | 506A-DBA8-162E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Israel | 3AB7-CCCC-66CE | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Jakarta | AB86-8658-D0B9 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 714A-1906-4019 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Las Vegas | C4CA-6CE6-9A65 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in London | D327-625B-FA27 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Los Angeles | 74C1-812E-B5F7 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Madrid | AD30-D131-6002 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Melbourne | 08DC-A622-7B43 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Milan | 151C-4351-B731 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Montreal | EE55-D1B4-AD05 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Mumbai | 453E-AE32-93BA | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Netherlands | 87C6-ADBE-C29E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Osaka | 92B4-ACAE-CEBE | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Paris | 958D-AEB1-D7A0 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Phoenix | 7A92-196B-F054 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Salt Lake City | 4C79-444F-3BB6 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Santiago | AB4F-EDDE-C3E2 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Sao Paulo | 7216-C445-31B4 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Seoul | CC34-4246-CAB5 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Singapore | 3FF4-B714-B91E | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Stockholm | 26BF-A1CD-F230 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Sydney | F5E8-72D5-69BB | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Taiwan | 53FA-9434-7F5D | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Tokyo | 75E6-1FF1-25F9 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Toronto | FFE8-BAB4-9663 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Virginia | E2CD-298B-2EDC | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Warsaw | 4F97-8CD3-28E8 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for M3 Memory-optimized Sole Tenancy Instance Ram running in Zurich | 334E-B4BC-9B66 | February 27, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in APAC | 086C-A224-C665 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Americas | DE51-4CCA-0D0A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Berlin | CD41-C054-F333 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Columbus | 80E5-9E2F-2683 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Dallas | CE09-39CA-4CB4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Dammam | B743-3D65-2E0D | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Delhi | 227B-B563-B958 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in EMEA | 609C-1872-7073 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Finland | 4596-C3F1-BC11 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Frankfurt | ED4B-8E36-E01E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Hong Kong | 05F2-57D3-81BE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Israel | C1C7-739C-DF00 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Jakarta | C7A9-73E9-1C8D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Japan | 24D3-CCBF-B0DA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Johannesburg | C09D-D7A7-DCDC | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Las Vegas | F03A-A810-E7ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in London | 4F55-C956-C2E2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Los Angeles | 8315-E27B-C0F6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Madrid | 28A2-E44D-0A34 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Melbourne | B010-0CB8-08C3 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Mexico | 86C9-3622-6691 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Milan | DCB9-72B7-AA10 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Montreal | 3268-4B2B-9389 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Mumbai | E9AE-1C5E-737D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Netherlands | C51C-97F9-F5AF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Northern Virginia | 8221-A36C-4B99 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Osaka | C472-5EE0-669F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Paris | EE92-36E6-46DE | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Phoenix | EC06-3968-38F5 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Salt Lake City | 766B-75B9-3303 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Santiago | ACCD-3713-C818 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Sao Paulo | EDEE-DDF5-7BCF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Seoul | EEDD-57A6-DA0C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Singapore | 995E-E433-E650 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Stockholm | 31E4-A81D-BAC5 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Sydney | 7EE4-BCE5-3ABB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Tokyo | 6D8E-71C9-4D5D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Toronto | 1F4F-E06E-FC37 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Virginia | 2769-B1ED-37C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Warsaw | 78EB-D1F9-1BAF | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Core running in Zurich | 7A48-A60F-652F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in APAC | 79BF-1DC6-C84D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Americas | 3EA9-194A-0132 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Columbus | A1A8-E2F1-0C0C | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Delhi | 5A5D-1694-B288 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in EMEA | 590A-DD59-22A7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Finland | 30A8-4D6C-2E69 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Frankfurt | 8749-F6DC-EA74 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Hong Kong | 293C-D785-301E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Jakarta | C814-954B-5810 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Japan | B555-E1BA-7AE2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Las Vegas | 1F80-37AE-4D35 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in London | 25ED-357B-3507 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Los Angeles | F224-171E-7560 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Melbourne | 72B3-BA9B-94D6 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Montreal | 4865-D88B-AB44 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Mumbai | 7F0C-5184-BDC3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Netherlands | ACCD-D00C-40F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Northern Virginia | E458-19AF-8FEA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Osaka | 3E77-0660-4087 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Salt Lake City | 1398-1C3A-2947 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Santiago | 138C-FB27-FC7F | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Sao Paulo | 0340-9737-D60D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Seoul | 613B-DFF7-0397 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Singapore | 30C0-9497-E947 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Sydney | F31F-7CF4-1B9A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Tokyo | 810B-6503-8893 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Toronto | 60B8-760E-F873 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Virginia | 224D-2E7E-5718 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Warsaw | 99B6-9EB9-9833 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance RAM running in Zurich | 33DA-BE5C-F63E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Berlin | E878-2317-87F1 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Dallas | 2ACF-B5CD-2DA5 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Dammam | F0D3-562C-811B | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Israel | 43B0-9D83-AE3C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Johannesburg | 62B4-F0AD-520A | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Madrid | 0B5B-A204-45C1 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Mexico | A543-E770-D550 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Milan | C258-1F31-1123 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Paris | 40BD-77F0-B6FB | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Phoenix | 252E-D0EC-32E0 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Memory-optimized Sole Tenancy Instance Ram running in Stockholm | FA5E-B914-CB22 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in APAC | E1A2-1621-7DE8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Americas | 1735-32CE-8392 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Berlin | 083E-3896-5AB6 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Columbus | 280C-F6D7-D4EF | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Dallas | 8EED-92BA-4A91 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Dammam | EF3D-99EE-8482 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Delhi | 1CF0-4A95-9598 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in EMEA | DC53-E855-1DD7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Finland | 6D85-A8BD-A1F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Frankfurt | A283-B9B0-55E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Hong Kong | 4C5A-9763-3171 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Israel | D015-6D38-A51C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Jakarta | BF9D-3717-B3DB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Japan | A21C-97E8-2832 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Johannesburg | EA0A-26D6-23AE | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Las Vegas | 3B60-2DCE-7B68 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in London | 6429-860D-D771 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Los Angeles | 24EA-F8F4-EC8B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Madrid | F860-25F9-E581 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Melbourne | 9B5F-437B-5E4C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Milan | 7206-3053-FD35 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Montreal | 2FA2-09CB-D11E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Mumbai | 9FC1-F019-2D42 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Netherlands | DC19-251F-ADC2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Osaka | 0B4A-753B-4193 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Paris | EA6A-ED50-A147 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Phoenix | B3FC-768E-F61B | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Salt Lake City | B1D3-55D0-06D8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Santiago | 58DF-BEAB-AE67 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Sao Paulo | 52EB-6CBC-A53C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Seoul | 8678-D3B7-45C7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Singapore | EBDD-448F-9141 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Stockholm | 5360-DF5D-DEBF | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Sydney | 64A2-F742-0E18 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Toronto | AE3C-00C4-EE84 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Virginia | 8B99-4C58-A8E8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Warsaw | BECB-F994-82D4 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Core running in Zurich | 70FA-3E4F-8641 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in APAC | 0FAC-B765-FD27 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Americas | 3695-E721-737D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Columbus | A371-5484-FB1B | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Delhi | E755-D7E7-250C | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in EMEA | 0E4A-33D2-9AD6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Finland | 42D4-F202-16AC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Frankfurt | D635-D829-04E6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Hong Kong | 2877-E7F7-8193 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Jakarta | AB9B-07E9-25A3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Japan | 7C80-8DDE-335F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Las Vegas | 6A06-9CBD-6339 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in London | B8F9-2E2F-92C5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Los Angeles | 27F4-5725-4650 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Melbourne | 3477-6897-034E | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Montreal | E2CE-4934-E4EC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Mumbai | C54E-AFB5-B289 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Netherlands | 3F47-036B-FFD3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Osaka | D979-945A-2082 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Salt Lake City | A07D-81FF-1D3B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Santiago | 70D0-0F6E-EB63 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Sao Paulo | 7716-F5E9-7968 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Seoul | A320-6E00-408E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Singapore | 68D4-26FD-63F3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Sydney | 91FD-8271-23ED | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Toronto | 0B46-E7E8-CAB6 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Virginia | 5D84-7DF9-6ECE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Warsaw | 93BF-3703-B8CD | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance RAM running in Zurich | 1524-8774-D856 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Berlin | E076-8ED3-EADA | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Dallas | 7001-AC71-8B33 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Dammam | 1F76-B0CB-B1B1 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Israel | C7A1-AF03-3FC1 | June 15, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Johannesburg | E734-EF5C-DD75 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Madrid | 6FDC-26B8-7FDE | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Milan | D87F-D3EE-4A86 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Paris | 26A8-A552-ADE0 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Phoenix | 2C87-F601-3867 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2 Sole Tenancy Instance Ram running in Stockholm | CB68-B4D0-2ECC | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in APAC | D778-A15B-CC3B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Americas | 1CE1-29CF-CC9F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Berlin | 8744-E6A6-68CD | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Columbus | 0028-F8D6-A106 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Dallas | 090D-0081-2C2A | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Dammam | 9B6B-78F1-7F05 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Delhi | 7CBD-74D3-36BC | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in EMEA | 7B8C-9012-F4E6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Finland | BEBD-9801-2CA4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Frankfurt | B680-F3E7-C3D9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Hong Kong | 394D-A0BF-454E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Israel | A66C-4909-B13F | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Jakarta | DA0F-48B1-75E1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Japan | 66BD-24A9-791A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Johannesburg | CFBF-EA17-0485 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Las Vegas | 856C-7E5E-02DF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in London | 9F9E-A372-AA4B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Los Angeles | A524-A3AF-56FC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Madrid | 39BF-633D-53D4 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Melbourne | CDE6-8E31-E459 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Milan | 4EE5-FAB3-1F43 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Montreal | A6B1-F99E-E1BA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Mumbai | 657B-2434-9D82 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Netherlands | DF3A-3B43-4883 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Osaka | 5512-367E-1081 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Paris | BB8E-B042-0E88 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Phoenix | 57BD-C977-892E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Salt Lake City | 140D-4F20-022D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Santiago | 9ECB-419A-35A0 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Sao Paulo | 5172-8AEC-8319 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Seoul | 1ADD-B382-CF69 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Singapore | F18B-270C-17CE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Stockholm | 30D5-4976-500F | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Sydney | 4F4F-9D12-AD4F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Toronto | 96DE-B115-CD8B | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Virginia | C398-DF26-CF06 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Warsaw | 6DB8-34C5-C48F | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Core running in Zurich | DE51-09B5-76A4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in APAC | 653F-91E8-7737 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Americas | 1C63-070B-F9A0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Columbus | 2D72-46C4-F0E9 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Delhi | 9747-7A4C-82EF | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in EMEA | E0BE-1BDB-1657 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Finland | 0D05-9F24-5FAB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Frankfurt | BF05-AEA2-4D67 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Hong Kong | FEF2-13B1-0E67 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Jakarta | FD52-0E4F-FD8D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Japan | 84A4-1617-003C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Las Vegas | E7E7-ED1C-F0C7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in London | 0C46-7A36-9455 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Los Angeles | F729-0904-0977 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Melbourne | 4AAA-0803-C231 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Montreal | EEFF-9376-AABD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Mumbai | FE32-AFFE-B815 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Netherlands | 15C2-6C8B-F2AD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Osaka | 2315-7ABA-77EC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Salt Lake City | 955D-23FB-7896 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Santiago | FF91-60BA-236E | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Sao Paulo | 4C9F-4A07-025C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Seoul | 4195-A50E-08DC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Singapore | 95A3-5989-C880 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Sydney | 61C8-E9B0-BD4A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Toronto | 88DA-3EEB-EF9C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Virginia | 2786-EBAD-17F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Warsaw | 0A50-408B-AEDA | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance RAM running in Zurich | AC5E-4C2C-7BEC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Berlin | 9E81-96D5-FFAB | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Dallas | 8457-A46B-B500 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Dammam | 2144-E752-ED9E | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Israel | 521F-A13C-4E8E | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Johannesburg | 5183-92C5-0667 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Madrid | E824-E769-9485 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Milan | 5D83-2607-1ECD | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Paris | 4FAD-3D3D-CD91 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Phoenix | 3F83-1567-0478 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for N2D AMD Sole Tenancy Instance Ram running in Stockholm | 7021-1FF8-0FC3 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in APAC | 6C8A-078A-E638 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Americas | 9894-9B93-3D34 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Berlin | 4198-EE04-F092 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Columbus | 925E-F35A-7373 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Dallas | 7EDB-2964-A402 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Dammam | F916-5CFF-0608 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Delhi | 4AB5-0984-2A46 | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in EMEA | B0FD-E8D7-8E63 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Finland | 61D3-211F-B7B7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Frankfurt | F2CC-B6E9-C85C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Hong Kong | 45D8-7D67-6EF0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Israel | C584-0EE8-EF6D | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Jakarta | FF49-6406-7BEA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Japan | 491D-D573-70EA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Johannesburg | 477A-52C3-5F58 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Las Vegas | 3928-9BB4-3244 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in London | 339E-49F3-9EF8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Los Angeles | 6B12-3724-C5EA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Madrid | EEAE-56BD-1E71 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Melbourne | A421-8B16-F22C | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Mexico | DE31-57EF-6DEE | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Milan | 1AF8-1C6D-A9B3 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Montreal | A6F2-484A-CE7D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Mumbai | EBD3-14AB-65E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Netherlands | 923F-3BC9-C76D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Osaka | E906-E8C3-07E2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Paris | A677-042A-D252 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Phoenix | CCDD-E6A4-4F6E | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Salt Lake City | D33D-495F-E8B8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Santiago | FA1B-6F78-9CE4 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Sao Paulo | 8802-17EC-0FAE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Seoul | 9EB6-F9AF-55CE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Singapore | 89D7-5956-2416 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Stockholm | 9D70-7A45-F892 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Sydney | CDAE-5881-4570 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Toronto | 4352-BA69-6E3E | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Virginia | A7A8-5D78-6AC9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Warsaw | B5F0-83FB-E0E2 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Core running in Zurich | 0133-361C-2DCD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in APAC | 13E9-5FC2-6FC0 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Americas | 9D07-8FA0-BB39 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Columbus | CFC7-F372-01B9 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Delhi | F76E-3CFC-B58E | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in EMEA | 58D2-E4A3-C0BB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Finland | CF78-2AC3-AC26 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Frankfurt | 8042-34F8-504C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Hong Kong | F7D9-58FD-DB17 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Jakarta | D340-9E10-5B63 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Japan | E1AA-2F72-8E3A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Las Vegas | 7667-D086-EC39 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in London | BA04-B325-F040 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Los Angeles | A24F-A9D9-8203 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Melbourne | 403B-DC17-6883 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Montreal | C357-3828-D04B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Mumbai | 3CEE-F885-8DF7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Netherlands | 9146-22F1-0A09 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Osaka | 3011-D101-D810 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Salt Lake City | 6B78-72AC-8E9F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Santiago | BE3F-791E-9469 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Sao Paulo | 7861-F324-E54C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Seoul | 4353-6697-0B2E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Singapore | 3298-8D0C-36FE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Sydney | CA87-BBEC-A502 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Toronto | F8DE-7933-7F92 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Virginia | 9174-81EE-425B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Warsaw | D588-CBB9-3114 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance RAM running in Zurich | E6B8-C1C9-70A9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Berlin | BB8D-3E91-91A7 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Dallas | D6B0-BBD0-05AB | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Dammam | 4A2D-CC18-9DF8 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Israel | B8B1-3904-F40B | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Johannesburg | D2F6-502A-F98C | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Madrid | F018-F465-B86C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Mexico | 18C9-D43A-9318 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Milan | B527-C96E-95AE | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Paris | 78A6-DA8C-536C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Phoenix | D044-B783-D5E2 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Sole Tenancy Premium for Sole Tenancy Instance Ram running in Stockholm | 2527-F549-5F29 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Americas | 775F-7AA0-C8CC | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Belgium | 12D4-5E90-7E75 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Columbus | C54D-1928-BA9D | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Dallas | D0B6-B3C5-8E04 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Dammam | C8D8-076A-1058 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Frankfurt | 5099-9D79-47E3 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in London | 4640-6BCF-E1D8 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Mexico | 8B0C-2352-AE45 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Mumbai | 2254-E902-5704 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Netherlands | 3FFF-4E30-D702 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Paris | FA0B-B8EC-D937 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Salt Lake City | 09DD-3986-4361 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Sao Paulo | D6CB-898D-2BF7 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Seoul | DCB5-8D75-6B5F | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Singapore | 54C5-41D7-BD14 | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Sydney | 6FC4-97F5-27FD | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Tokyo | DC53-1238-E86C | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Toronto | D267-B362-A8EE | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Spot Preemptible N4 Custom Extended Instance Ram running in Virginia | F49D-7A5E-EC1F | June 25, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity | D973-5D65-BAB2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Berlin | 83E4-C062-FDEC | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Columbus | E763-1A59-7698 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Dallas | 7EA3-FF02-75C9 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Dammam | 1F1F-0EF5-15BE | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Delhi | 80E2-7FF9-979E | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Finland | CEF4-0773-7924 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Frankfurt | 7A7B-EA46-2897 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Hong Kong | 28D0-437A-CEAD | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Israel | A084-03C1-A923 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Jakarta | D619-8E03-F681 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Japan | 9977-2BC5-386A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Johannesburg | EEFE-F863-E07A | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Las Vegas | 9CB9-1019-8019 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in London | BF1A-6647-009D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Los Angeles | BF8D-1C96-EE1C | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Madrid | E45C-6460-E782 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Melbourne | B749-AAF2-5AC4 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Mexico | AA8E-A72E-B5D7 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Milan | D279-B8D7-090F | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Montreal | 92E5-B76E-D04B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Mumbai | 320C-7688-1A62 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Netherlands | AE8C-46C3-4994 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Osaka | 5A6A-4A16-F865 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Paris | E083-93C6-55CD | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Phoenix | A9A2-174F-91A0 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Salt Lake City | F993-B67E-E316 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Santiago | 9917-39D5-DB38 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Sao Paulo | DF49-E005-E705 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Seoul | 0306-B164-A7B7 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Singapore | 0572-568A-4FC4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Stockholm | 9F0A-51AB-9A36 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Sydney | 5334-92F9-3E7F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Toronto | 95EE-349E-CA35 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Virginia | 8AF1-1146-E7DA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Warsaw | 5881-96B1-93E3 | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Capacity in Zurich | 17A8-D0A4-D7E5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot | 817F-F5A3-514E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Asia | 6E69-DD68-8DCA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Berlin | 0AA2-FFEC-B45A | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Columbus | 83D5-5AB3-DF24 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Dallas | FBDA-ACD3-929F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Dammam | 0429-3D5C-ED01 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Delhi | 246B-6075-A49D | May 3, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in European Union | 9ECE-16D9-A2B4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Finland | 05B0-97EA-A0F8 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Frankfurt | 4AE8-2AF4-172B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Hong Kong | B620-43EA-5E66 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Israel | 1B77-1B44-DF15 | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Jakarta | 759C-6103-1C8E | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Japan | 8C30-3296-3468 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Johannesburg | EC86-922F-4ED8 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Las Vegas | A8C3-C764-4F04 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in London | 8BEB-BAC4-F049 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Los Angeles | 512A-60FF-8B5F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Madrid | 87FD-6AB0-6C13 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Melbourne | 23DA-1FDB-DE82 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Mexico | BB5E-B308-D867 | September 7, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Milan | 2422-D94B-65DD | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Montreal | 7690-2BAE-F7CF | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Mumbai | A0EA-3B8B-0794 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Netherlands | 839E-6EA7-03C6 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Osaka | 3891-E0EE-181D | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Paris | BC69-AD58-A416 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Phoenix | D478-DA53-58D9 | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Salt Lake City | A446-8A55-B235 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Santiago | 27BD-7BB7-9E5E | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Sao Paulo | EA77-B0EB-7259 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Seoul | 81F5-D06C-3601 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Singapore | EC5A-D05B-E188 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Stockholm | C1F4-9D0E-8AEE | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Sydney | C8DC-D162-2E92 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Toronto | ECB5-7135-2661 | May 11, 2021 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in US | 34CF-7D88-5D40 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Virginia | 3FB1-991D-37F5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Warsaw | 0B3A-5493-BBAA | November 22, 2020 |
| Compute Engine (6F81-5844-456A) | Storage PD Snapshot in Zurich | 98E1-6F63-493A | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Core running in Americas | 7F42-2C35-6872 | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Core running in Netherlands | 5825-9018-A945 | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Core running in Singapore | 21FA-D397-3735 | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Ram running in Americas | C5C1-548B-71FE | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Ram running in Netherlands | 7B47-C603-1F9F | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2A Arm Instance Ram running in Singapore | 761E-277E-41F6 | July 12, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in APAC | B70B-A9A7-97BC | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Americas | EFE6-E23C-19CB | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Berlin | 8E3C-2C90-A02C | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Columbus | 4901-ECCD-AB7D | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Dallas | 5A44-D30D-8BBE | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Dammam | 5187-99E7-9541 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Delhi | 5037-833F-4A14 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in EMEA | 985B-2944-7653 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Finland | 862D-0790-70DA | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Frankfurt | B260-618D-1521 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Hong Kong | 39FB-2179-5CCB | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Israel | 8721-6706-E58C | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Jakarta | 53E2-8463-9290 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Japan | 8F0F-B4CF-6A97 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Johannesburg | 6AC7-5DA4-3E28 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Las Vegas | 973D-DFDC-9D41 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in London | 7BBB-DC8B-734D | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Los Angeles | 9CCD-29C1-67C2 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Madrid | 86BA-809D-BFB3 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Melbourne | 470A-4F75-9DEF | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Milan | A02F-3B54-183E | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Montreal | 0C02-6911-ECD5 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Mumbai | 7B25-FFC2-42EE | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Netherlands | 5FC8-B122-E95E | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Osaka | CC69-8FF0-F871 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Paris | D9CA-61B5-6E5C | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Phoenix | 94EC-6653-61EC | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Salt Lake City | C254-9CFC-EA47 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Santiago | 0477-DE99-B0FA | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Sao Paulo | E3E7-30A1-1760 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Seoul | 37D7-7917-D77E | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Singapore | 9E37-EAF4-1576 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Stockholm | DC60-FC89-400F | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Sydney | 9E73-269C-A4C5 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Toronto | 07D8-AB8A-B2AE | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Virginia | 01C8-F6AC-8232 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Warsaw | 939B-CAD6-F771 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Core running in Zurich | BBC5-6580-4535 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in APAC | 73AA-471D-8CE5 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Americas | FB05-036A-8982 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Berlin | 709F-7D36-5646 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Columbus | 4D80-A46A-3A08 | December 3, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Dallas | 7776-77BF-DAC8 | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Dammam | 2A48-8A3B-CF22 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Delhi | 32D9-9377-E451 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in EMEA | 0FAA-E6E0-A064 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Finland | A064-499E-A036 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Frankfurt | E639-283C-5F35 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Hong Kong | 031F-428F-EDCF | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Israel | DF84-9EE6-B6CF | August 17, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Jakarta | 52F9-32F5-97B2 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Japan | 96DD-EC64-2418 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Johannesburg | E827-970B-40FC | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Las Vegas | 2EF7-138A-094B | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in London | 3820-932A-0095 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Los Angeles | 4FFE-8CDB-F9DB | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Madrid | 705C-082E-B55F | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Melbourne | 02DE-83D6-EA67 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Milan | F6B6-9866-5955 | January 7, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Montreal | 4728-5219-2EB2 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Mumbai | 229C-8FDA-854F | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Netherlands | 5BD9-71BC-76F5 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Osaka | 9B87-74F7-39D6 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Paris | D8DB-8259-C73D | January 30, 2022 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Phoenix | 7914-47E9-106F | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Salt Lake City | 22CC-8206-6A3A | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Santiago | 3420-0CE5-7383 | August 22, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Sao Paulo | FC42-910D-9BFA | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Seoul | CAF0-D0F9-E367 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Singapore | 4756-01E4-0F32 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Stockholm | BAE9-2A56-EC79 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Sydney | 7BFA-6743-1916 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Toronto | 2E52-7F18-522F | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Virginia | D5BA-C08E-1DDC | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Warsaw | BD8D-6329-AF14 | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | T2D AMD Instance Ram running in Zurich | 58AE-BA44-8FED | June 27, 2021 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in APAC | 27EC-7D5B-D560 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Berlin | 1E16-2D73-CEC9 | May 18, 2023 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Dammam | D5B2-417C-9516 | June 9, 2023 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in EMEA | D50B-484D-C2A2 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Finland | AA05-BDC6-DDCC | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Frankfurt | ABDD-344E-71E9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Hong Kong | 0D39-41F7-43FA | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Jakarta | 2AF1-EA01-97C9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Japan | 4708-EFB4-843F | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Johannesburg | B0D1-AA0B-61B7 | August 1, 2023 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Las Vegas | F54F-02DC-69C1 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in London | 6A78-392A-2ED9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Los Angeles | C0A3-044D-42C3 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Montreal | C17A-4E45-D73B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Mumbai | 4100-5920-9EFE | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Netherlands | 70A8-0DE2-8AC9 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Osaka | 9459-A3F2-FEB5 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Phoenix | A482-CA5E-6C5F | November 1, 2023 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Salt Lake City | F4D1-A42E-E088 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Sao Paulo | 99D3-6231-28EB | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Seoul | EEF8-9BFD-3D04 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Singapore | 3FDA-0EE2-A644 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Stockholm | EA27-FD7A-DCF5 | May 24, 2024 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Sydney | 0DDB-8A00-937B | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Virginia | 4BA4-98E0-FCD4 | June 17, 2020 |
| Compute Engine (6F81-5844-456A) | VM state: suspended RAM in Zurich | 364E-B6DE-BD8A | June 17, 2020 |