diff --git a/content/r2/learning/regions.md b/content/r2/learning/regions.md index 539c8804ae9ecc0dbf61230d68f2c3f22fd73936..3bc0ca9d2f01ae3d4dcb4a8f7b12e6f3d578c4cc 100644 --- a/content/r2/learning/regions.md +++ b/content/r2/learning/regions.md @@ -5,8 +5,8 @@ pcx-content-type: reference ## Regions in R2 -R2 is designed from the ground up to be global - unlike other object storage services, there is no need to select a specific region to store data in. +R2 is designed from the ground up to be regionless - unlike other object storage services, there is no need to select a specific region to store data in. -During the open beta period, R2 stores data in a small number of points of presence in North America. Data is stored in a single region and replicated within that region for high availability. Over time, we plan on adding additional data centers. As these data centers come online, R2 will automatically place a single copy of your files in the data center that is closest to your user's requests. +During the open beta period, R2 stores data in a small number of points of presence in North America. When a bucket is created, it is placed in the region closest to where the bucket was created. Each object is stored in a single region, and is replicated within that region for high availability. Over time, we plan on adding additional data centers. As these data centers come online, R2 will automatically place a single copy of your files in the data center that is closest to your user's requests. In the future, we plan to allow developers to specify a number of copies of data that R2 should keep and automatically distribute across data centers for lower latency access.