Locations: countries, regions, availability zones, pools, and data center addresses
With Servercore's products and services, you can create an infrastructure that meets all requirements for fault tolerance and security.
Servercore infrastructure is located in various locations.
A location is the physical placement of your infrastructure within Servercore's infrastructure, which includes:
Choosing a location affects how you manage availability, fault tolerance, and load balancing in your infrastructure.
Currently, you can choose from 4 countries to host your infrastructure in Servercore, which are divided into 6 regions, 11 availability zones, and 24 pools.
You can check the availability of Servercore products and services in different locations in the availability matrices.
Country
A country (example: Russia) consists of one or more regions located within the same state.
In most cases, geographical division by country does not affect anything, and the primary division of infrastructure occurs at the region level. In some specific cases, there are limitations for regions in different countries:
- when using a Global Router, you cannot configure network connectivity for products placed in different countries. You can configure connectivity for products and services only between different regions within the same country;
- for S3, each country uses different domains, and TLS (SSL) certificates are bound to a country—a certificate only works for buckets hosted in the region of the certificate's country.
Region
A region (example: St. Petersburg) consists of several availability zones with Servercore and partner data centers located within a major city's metropolitan area.
Data centers within a single region are usually located relatively close to each other—within tens of kilometers. They are connected by a fiber-optic communication line with data redundancy, and minimal signal latency is ensured between data centers within a region.
Data centers in different regions, conversely, can be located hundreds or even thousands of kilometers apart. Each region is completely isolated from the others: independent connection to power lines, autonomous power and cooling sources, and dedicated communication channels. This enables geographical distribution of infrastructure and ensures its fault tolerance.
Servercore provides connectivity between regions via redundant, high-performance communication channels.
To host your application, we recommend choosing a region closest to your users as your primary location. You can place your resources in different regions — then the infrastructure will be able to survive possible service provider failures, such as Internet outages at the border level, natural disasters, and emergencies.
You can view the list of regions in the Servercore Infrastructure table.
Availability zone
An availability zone (example: Availability zone 1 in Moscow) is one or more data centers within a single region. Availability zones within a single region can be located at varying distances from each other — from several meters to tens of kilometers. Each data center in an availability zone is equipped with autonomous power and cooling sources and its own redundant communication channel with ultra-low latency.
Servercore reserves all critical system elements within an availability zone: power supply, cooling, and network infrastructure. Each availability zone is provided with 24/7 physical security and monitoring. Equipment maintenance operations are not performed simultaneously in multiple availability zones within the same region.
We recommend that you reserve critical parts of your infrastructure in multiple availability zones. There is no single point of failure for availability zones—only a single point of failure for the entire region. This will protect your system in the event of a failure in one of the zones, such as a data center power outage, fire, or natural disaster.
You can view the list of availability zones in the Servercore Infrastructure table.
Pool
Multiple pools are located in each data center and, consequently, in each availability zone. Each pool is isolated from hardware and software failures in other pools.
Network connectivity within a single-zone or multi-zone pool is provided via L2 connection. To configure connectivity between pools, you can use the Servercore Global Router.
For cloud infrastructure, pools are additionally divided into pool segments (example: ru-2a, ru-2b). Segments provide additional fault tolerance — infrastructure for different segments is placed in different racks within the same pool. The fault domain for a segment for servers and storage systems is an individual rack. Network infrastructure functions at the pool or availability zone level.
You can view the list of pools and segments in the Servercore Infrastructure table.
Single-zone pool
A single-zone pool (example: ru-9, SPB-4) — part of the infrastructure in one of the data centers of an availability zone.
Segments of single-zone pools are located in different racks within the same data center of an availability zone.
Placing infrastructure in multiple pools protects against network hardware and software failures (for example, network equipment failure or power circuit failure), and reduces the risk of data loss and service downtime. The single point of failure for single-zone pools is failures in the availability zone.
Multi-zone pool
A multi-zone pool (example: ru-6) — part of the infrastructure in several data centers of different availability zones.
Segments of a multi-zone pool are located in several data centers in different availability zones.
Placing infrastructure in a multi-zone pool:
- protects against the effects of natural disasters and fires in data centers;
- protects against network hardware and software failures (for example, network equipment failure or power circuit failure);
- reduces the risk of data loss and service downtime.
A single point of failure for a multi-zone pool consists of failures in all availability zones where the pool segments are located.
Increase fault tolerance
You can increase infrastructure fault tolerance at the following levels:
- hosts;
- racks or pool segments;
- pools;
- availability zones;
- or regions.
For example, to increase fault tolerance for cloud servers at the host level, you can place cloud servers on different hosts in a placement group. To increase fault tolerance at the rack and pool segment level, you can move a dedicated server to a different rack, and for a cloud server, move it to a different pool segment. For fault tolerance at the availability zone level, you can place servers in different availability zones and, for cloud servers, use segments of the ru-6 multi-zone pool.
Servercore Infrastructure
Uzbekistan
Kazakhstan
Kenya
Russia
Tashkent