Start with traffic geography
Before choosing a server network profile, map where users, applications and dependencies live. A Georgian audience, European API provider, remote database replica and international backup destination create different traffic patterns. Estimate both inbound and outbound demand. The most useful question is not "what port speed do I have?" but "which traffic must cross which network boundary, and for how long?"
Separate local and international capacity
ServerGeorgia deliberately presents local and international capacity as separate numbers. The standard dedicated profile is 1 Gbps local Georgia connectivity and 50 Mbps international connectivity with unmetered traffic. This avoids treating a 1 Gbps local port as a promise of 1 Gbps to every destination outside Georgia. Custom international capacity should be raised in the quote if the standard profile is insufficient.
Convert data movement into sustained Mbps
Backups, replication, media delivery and large software packages are easier to plan when converted to sustained throughput. For example, moving large datasets every night can consume most of a 50 Mbps international link for hours even if web traffic is light. Estimate transfer size, available time window and frequency. Short speed-test peaks are less important than the throughput the workload must sustain.
Consider latency and throughput separately
Latency affects interactive applications, database round trips and control-plane traffic, while bandwidth determines how much data can move over time. A workload can have acceptable latency but insufficient throughput, or the opposite. If a specific external service is critical, identify its geography and test route behavior after deployment rather than assuming every international destination performs the same way.
Reserve bandwidth for backups and operations
Do not size the link only for end-user traffic. OS updates, monitoring, log export, backup traffic, replication and administrative access also consume capacity. If backup windows are flexible, schedule them away from peak production traffic. If they are not flexible, include the expected sustained backup throughput in the initial network requirement.
Put network requirements in the quote
State target regions, expected sustained Mbps, required IPv4 quantity and any management-network requirement before ordering. This gives the infrastructure team an opportunity to confirm whether the standard profile fits or a custom network option is needed. Network planning done before deployment is usually cheaper and less disruptive than changing assumptions after users are already on the system.