مرکز آموزش

Understanding the ALYPOD network and datacenters پرینت

  • datacenters, network, infrastructure, latency
  • 0

Overview

ALYPOD Cloud runs Pods in multiple datacenter locations. Choosing the right location keeps latency low for your users and can reduce cost. This article explains how our network is organised and how to pick a location.

Network at a glance

  • Each datacenter has redundant upstream carriers and redundant core switching, so a single link or device failure does not take your Pod offline.
  • Traffic between Pods in the same datacenter can use the private network and does not traverse the public internet.
  • DDoS mitigation runs at the network edge, in front of your Pod (see the DDoS protection overview article).
  • Pods get public IPv4 and IPv6 connectivity, plus private networking where available.

Choosing a location

Pick the location closest to your users or to the services you depend on:

  • Lower round-trip time means faster page loads and snappier SSH.
  • If you serve a global audience, place Pods in more than one location and put a CDN or DNS-based load balancing in front.
  • Keep tightly coupled Pods (app plus database) in the same location so they can use the private network.

You can see available locations and estimated latency when creating a Pod in the ALYPOD Console.

Measuring latency

From your workstation or another Pod, measure round-trip time:

bash ping -c 5 <pod-ip> traceroute <pod-ip>

Compare results between candidate locations before you commit. For long-term measurements, mtr shows both latency and packet loss per hop.

Moving between locations

Pods are tied to a location. To move, take a snapshot or back up your data, create a new Pod in the target location, restore the data, and update DNS. Private networks are per-location and must be recreated.

Troubleshooting

  • Problem: High latency to a Pod. Solution: Confirm the location you selected and test with mtr; the delay may be in your own ISP's path.
  • Problem: Pods in different locations cannot use a private network. Solution: Private networking is limited to a single location; use encrypted tunnels over the public internet for cross-location traffic.

Related articles

  • [Private networking between Pods]
  • [Testing connectivity with ping, traceroute and mtr]

آیا این پاسخ به شما کمک کرد؟

« برگشت