Locations: countries, regions, availability zones, pools, and data center addresses
With Servercore's products and services, you can create an infrastructure that meets all fault tolerance and security requirements.
Servercore infrastructure is hosted in different 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 for hosting 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 Product availability by location guide.
Country
Country (example: Uzbekistan ) is one or more regions located within a single country.
In most cases, division into countries does not affect anything, and the primary separation of infrastructure occurs at the region level. In certain cases, there are restrictions for regions in different countries:
- when using a global router, network connectivity cannot be configured between products hosted in different countries. You can configure connectivity between products and services only between different regions within the same country;
- in S3, different domains are used for each country, and TLS (SSL) certificates are bound to the country — a certificate works only for buckets located in a region of the certificate's country.
Region
Region (example: Tashkent ) is several availability zones with Servercore data centers and partner data centers located within the metropolitan area of a major city.
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; minimal signal latency is ensured between data centers within the region.
Data centers in different regions, by contrast, can be located hundreds or even thousands of kilometers apart. Each region is completely isolated from others: independent power line connections, autonomous power supply and cooling sources, and dedicated communication channels. This helps ensure geographic distribution of infrastructure and its fault tolerance.
Servercore provides connectivity between regions through redundant high-speed communication channels.
To host your application, we recommend choosing the region closest to your users as your primary location. You can place resources in different regions — this way, your infrastructure will be able to survive potential provider failures, such as internet outages at the border level, natural disasters, or emergencies, with minimal downtime.
You can view the list of regions in the Servercore infrastructure table.
Availability zone
Availability zone (example: Availability zone 1 in Tashkent ) is one or more data centers within a single region. Availability zones within a single region can be located at different distances from each other — from a few meters to tens of kilometers. Each data center in an availability zone is equipped with independent power and cooling sources and its own redundant ultra-low latency communication channel.
Servercore reserves all critical system elements in an availability zone: power supply, cooling, and network infrastructure. Each availability zone is provided with 24/7 physical security and monitoring. Equipment maintenance is 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. Availability zones do not have a single point of failure, except for a failure of the entire region. This will protect your system in the event of a failure in one of the zones, such as a power outage in a data center, fire, or natural disasters.
You can view the list of availability zones in the Servercore infrastructure table.
Pool
In each data center and, consequently, in each availability zone, there are several pools. Each pool is isolated from hardware and software failures in other pools.
Network connectivity within a single-zone pool or multi-zone pool is provided via an L2 connection. To set up connectivity between pools, you can use the Servercore global router.
For cloud infrastructure, pools are additionally divided into pool segments (example: uz-1, uz-2 ). Segments provide additional fault tolerance — infrastructure of different segments is housed in different racks within a single pool. The segment fault domain for servers and storage systems is an individual rack. Network infrastructure operates at the pool or availability zone level.
You can view the list of pools and segments in the Servercore infrastructure table.
Single-zone pool
Single-zone pool (example: uz-1, TAS-1 ) is part of the infrastructure in one of the data centers of an availability zone.
Single-zone pool segments 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 likelihood of data loss and service downtime. The single point of failure for single-availability zone pools is a failure in the availability zone.
Multi-zone pool
Multi-zone pool (example: ru-6, uz-1) is part of the infrastructure across multiple data centers in different availability zones.
Multi-zone pool segments are located in several data centers across different availability zones.
Hosting infrastructure in a multi-zone pool:
- protects against the impact 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 likelihood of data loss and service downtime.
A single point of failure for a multi-zone pool is represented by failures in all availability zones where pool segments are located.
Improve fault tolerance
You can improve infrastructure fault tolerance at the level of:
- hosts;
- racks or pool segments;
- pools;
- availability zones;
- or regions.
For example, to increase cloud server fault tolerance 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 another rack, and a cloud server to another pool segment. For fault tolerance at the availability zone level, you can place servers across different availability zones, as well as use ru-6 multi-zone pool segments for cloud servers.
Servercore infrastructure
Uzbekistan
Kazakhstan
Kenya
Russia
Tashkent