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 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 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 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 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 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 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 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 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 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 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 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 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) | 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Iowa | 2B4F-981A-703B | 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 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 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 Iowa | D493-0B62-1972 | 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 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 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 Iowa | C325-0593-DAE5 | 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 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 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 Iowa | ED78-1B46-DA17 | 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 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 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 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 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 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 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 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 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 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 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 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) | 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 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 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 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 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 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 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 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 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 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 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 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) | 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 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 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 |