How to check latency to Cloud2Y locations

Quick answer: Run ping or mtr from where your users are to a server (or test IP) in the Cloud2Y location you are considering — Kyiv, Lviv, Amsterdam or Singapore. Latency is mostly physics: distance sets the floor, so the best region is almost always the one closest to your audience.

Overview

Latency (round-trip time, RTT) is how long a packet takes to travel to the server and back. It affects everything interactive: page loads, APIs, SSH, game servers. Unlike bandwidth, you cannot buy your way out of distance — 20 000 km of fibre has a hard minimum RTT, which is why location choice matters more than plan size for responsiveness.

Before you start

• A target IP in the region — your existing Cloud2Y server, or test IPs for each location (ask support for the current list).
• Access to a machine located where your users actually are (your PC, an office box, or a probe service).

Step-by-step guide

1. Simple ping (Windows, macOS, Linux):

   ping -c 10 TARGET_IP      # Linux/macOS
   ping -n 10 TARGET_IP      # Windows

   Look at the average and the spread (jitter).
2. Path view with MTR:

   sudo apt install -y mtr-tiny
   mtr -rwbc 50 TARGET_IP

   Shows per-hop latency so you can see where the distance is added (see how to read MTR).
3. Compare regions — repeat against a test IP in each candidate location and pick the lowest RTT from your audience's viewpoint, not your own.

Rough expectations

As a sanity check: same city is usually a few ms; within Europe tens of ms; Europe ↔ Singapore well over a hundred ms. If your numbers are wildly above that for the distance, investigate packet loss or routing.

Common issues

• Testing from the wrong place: your latency from home is irrelevant if your users are elsewhere.
• One bad sample: a single high ping is noise — look at averages over dozens of packets.
• ICMP deprioritized: some routers answer pings slowly while forwarding traffic fine; MTR's final hop is what counts.

When to contact support

If latency to a location suddenly jumps far above its usual level and stays there, report it with MTR outputs from before/after if you have them.

Frequently asked questions

What latency should I expect?

It scales with distance: a few ms in the same city, tens of ms within Europe, well over a hundred ms between Europe and Singapore.

Can I test latency before ordering?

Yes — ask support for current test IPs per location, or use a Looking Glass, and ping them from where your users are.

Can a bigger plan reduce latency?

No. Latency is determined by physical distance and routing, not by plan size — the only reliable way to lower it is choosing a location closer to your users.

Related articles

• How to choose the best server location
• How to check traceroute / MTR
• How to troubleshoot packet loss
• Cloud2Y service locations: Ukraine, Europe, Singapore

Ready to get started? Order a VPS at Cloud2Y →