Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Why is the Maximum SLA Credit for Compute Engine and Load Balancing 100%, While Bare Metal Solution

I have a question regarding the difference in SLA credit percentages between Compute Engine (including Load Balancing) and Bare Metal Solution.

According to the SLA documentation:

  • Compute Engine and Load Balancing provide a maximum SLA credit of 100%.
  • Bare Metal Solution, on the other hand, has a maximum SLA credit of 50%.

Since both services run critical workloads, I would like to understand why there is such a significant difference in the SLA credit percentages.

Is it due to differences in infrastructure responsibility, network dependencies, or other factors? Could you clarify the reasoning behind this distinction?

1 2 547
2 REPLIES 2

Hi @sumin1,

Welcome to Google Cloud Community!

Google Cloud's Service Level Agreements (SLAs) for Compute Engine, Load Balancing, and Bare Metal Solution services define the maximum financial credits available to customers in the event of service unavailability. These credits vary based on the service and the extent of the downtime experienced.

The following are the Service Level Agreements for the following Google Cloud Platform services.

Compute Engine and Load Balancing:

  • For Compute Engine instances deployed across multiple zones and for Load Balancing services, the SLA provides financial credits based on the Monthly Uptime Percentage.
  • The maximum financial credit issued by Google for all Downtime Periods in a single billing month will not exceed the amount due for the respective Covered Services in the regions that did not meet the Service Level Objective (SLO) for that month.
  • Responsibility: Google is responsible for the availability, maintenance, and performance of its services, including the underlying hardware and hypervisor. However, the uptime of your application depends on how it is configured and deployed. The 99.99% SLA is only applicable if instances are set up in a highly available, multi-zone configuration.
  • Compute Engine availability is influenced by network connectivity, with Google managing the internal network while external access depends on the internet and user configurations. External Load Balancers follow a more complex network path but leverage Google's robust global infrastructure, whereas Internal Load Balancers operate solely within Google's internal network, minimizing external dependencies.

Bare Metal Solution:

  • The Bare Metal Solution SLA defines enterprise-grade commitments for hardware uptime and interconnect availability. Specific details regarding the maximum financial credits are outlined in the Bare Metal Solution SLA document. 
  • The maximum financial credit issued by Google for any and all Downtime Periods that occur in a single billing month will not exceed 50% of the amount due by Customer for the Covered Server for the applicable month. These credits will be applied as a monetary credit toward future service usage and will be processed within 60 days of the request. 
  • Responsibility: While Google manages the physical hardware, networking, and data center facilities, and customers are responsible for the software stack, including the operating system, applications, and data management. With Bare Metal Solution, customers have significant control, but since multi-zone configurations are not available, its uptime target aligns with that of single-zone Compute Engine instances.
  • Bare Metal Solution relies on network connectivity, and any network dependencies can affect its availability.

In summary, the difference in maximum SLA credits reflects the varying levels of control and responsibility between Google and the customer. Fully managed services like Compute Engine and Load Balancing offer higher SLA credits since Google handles end-to-end management, allowing for greater compensation in case of failures. In contrast, Bare Metal Solution involves shared responsibilities, where both Google and the customer contribute to the service’s performance, resulting in a lower maximum credit that accounts for this partnership.

Note: Always refer to the official and most up-to-date Google Cloud SLAs for the precise terms and conditions. You can find these on the Google Cloud website in the legal section. Search for "Google Cloud Platform Service Level Agreements"

If you have any more concerns or questions, you may reach out to Google Cloud Support for further assistance. 

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

By the way, I noticed that third parties like AWS seem to offer credits covering up to 100% of the customer's maximum payment, even for bare metal solutions/instances. On the other hand, Google seems to take a more conservative approach. Could you share some insights on why that might be?