Understanding high availability for projects

IBM Cloud® projects is a general availability (GA) service that is offered in multiple regions: Dallas, Washington, Toronto, Sao Paulo, Frankfurt, Tokyo, Sydney, Osaka, and London. Each location has three different data centers for redundancy. The data for each location is kept in the three data centers near that location. If all of the data centers in a location fail, the IBM Cloud Projects service for that location becomes unavailable.

See ensure zero downtime to learn more about the disaster recovery standards. You can also find information about IBM Cloud Service Level Objectives.

Responsibilities

For more information about high availability and disaster recovery and your responsibilities when you use projects, see Understanding your responsibilities when using projects.

What level of availability do I need?

You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that is correct for you depends on several factors, such as your business requirements, the service level agreements (SLAs) that you have with your customers, and the resources that you want to expend.

What level of availability does IBM Cloud offer?

The level of availability that you set up for your cluster impacts your coverage under the IBM Cloud high availability service level agreement terms.

Service level objectives (SLOs) describe the design points that the IBM Cloud services are engineered to meet. Projects are designed to achieve the following availability target.

Table 1. SLO for projects
Availability target	Target Value
Availability %	99.999%

The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs. For a summary of all SLOs, see IBM Cloud service level objectives.

Locations

For more information about service availability within regions and data centers, see Service and infrastructure availability by location.