Stay organized with collections
Save and categorize content based on your preferences.
Parallelstore instances live in zones within regions. A region is a specific
geographical location where you can run your resources. Each region is
subdivided into several zones. For example, the us-central1 region in the
central United States has zones us-central1-a, us-central1-b,
us-central1-c, and us-central1-f. For more information, see
Geography and regions.
Some Google Cloud APIs, including the Parallelstore API,
use the concept of locations, which can represent either
regions or zones.
For Parallelstore instances, locations map to zones.
To decrease network latency, we recommend creating a Parallelstore
instance in a region and zone that is close to where you plan to use it. For
example, if you plan to access the instance from Asia, then you should create it
in one of the asia-east1 zones. Similarly, you get the best performance by
mounting Parallelstore instances on clients in the same region.
Supported regions and zones
Parallelstore is available in the following regions and zones.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Supported locations\n\nParallelstore instances live in zones within regions. A region is a specific\ngeographical location where you can run your resources. Each region is\nsubdivided into several zones. For example, the `us-central1` region in the\ncentral United States has zones `us-central1-a`, `us-central1-b`,\n`us-central1-c`, and `us-central1-f`. For more information, see\n[Geography and regions](/docs/geography-and-regions).\n\nSome Google Cloud APIs, including the Parallelstore API,\nuse the concept of locations, which can represent either\n[regions or zones](/storage/docs/locations#key-concepts).\nFor Parallelstore instances, locations map to zones.\n\nTo decrease network latency, we recommend creating a Parallelstore\ninstance in a region and zone that is close to where you plan to use it. For\nexample, if you plan to access the instance from Asia, then you should create it\nin one of the `asia-east1` zones. Similarly, you get the best performance by\nmounting Parallelstore instances on clients in the same region.\n\nSupported regions and zones\n---------------------------\n\nParallelstore is available in the following regions and zones."]]