Google Cloud Regions and zones

Google Cloud Platform services are available in locations across North America, South America, Europe, Asia, and Australia and are divided into regions and zones.
Region
Regions are collections of zones. Zones have high-bandwidth, low-latency network connections to other zones in the same region. In order to deploy fault-tolerant applications that have high availability, Google recommends deploying applications across multiple zones and multiple regions. This helps protect against unexpected failures of components, up to and including a single zone or region.
Zone
A zone is an isolated location within a region. The fully-qualified name for a zone is made up of -. For example, the fully-qualified name for zone a in region us-central1 is us-central1-a.
Depending on how widely you want to distribute your resources, create instances across multiple zones in multiple regions for redundancy.
Multi-regional resources
The following services have one or more multi-regional deployment areas in addition to any regional deployment areas:
Storage:
Google Cloud Datastore
Google Cloud Storage
Google Cloud Spanner
Big Data:
Google BigQuery
Other
Google Cloud KMS
Container Registry
Application deployment considerations
To build highly available services and applications that can withstand zones becoming unavailable
Use either:
Regional resources, such as App Engine applications, or managed multi-regional resources, such as Cloud Storage or Cloud Datastore.
Zonal resources, such as Compute Engine virtual machines, but manage your own compute and storage redundancy across zones or across regions.
To build disaster recovery capable applications that can withstand the extended loss of entire regions
For data, use one or more of the following strategies:
Use managed, multi-regional storage services such as Cloud Storage, Cloud Datastore, or Cloud Spanner.
Use zonal or regional resources, but snapshot data to a multi-regional resource such as Cloud Storage or Cloud Datastore.
Use zonal or regional resources, but manage your own data replication to one or more other regions.
For compute, use the following strategy:
Use zonal or regional resources, such as Compute Engine or App Engine, but manually or automatically bring up your application in another region (on regional failure) referring to copies of your primary data if the data is not already in a managed, multi-regional resource.