Skip to main content
Check network status first. If the whole server is unreachable, start with Cannot Connect. If only a hostname fails, test the IP directly to separate DNS from connectivity.

Find where the problem is

An application or firewall can ignore ping while still allowing normal traffic, so ping alone doesn’t prove an outage.

Check bandwidth

Open the server’s “Overview” and look at the Bandwidth card. Hover over the figure for details and the reset date. If bandwidth pooling is on, also check “Bandwidth Pooling” for that team’s city. Plan allowances reset monthly. Purchased bandwidth blocks carry over until spent. A depleted pool can throttle every server in it. See Bandwidth and Pooling.

Collect packet-loss evidence

Run MTR from the affected computer toward the server. If you can reach the server, also run one from it toward the affected network, since routes can differ by direction.
Run WinMTR, enter the server IP in Host and click Start. Let it run for several minutes, then click Copy Text to clipboard or Export TEXT and paste the result into your ticket.
Loss at one middle hop isn’t necessarily loss of your traffic. Routers often rate-limit replies to probes while forwarding normally. Check whether the loss continues to later hops and the destination. Destinations can limit probes too, so include the symptom you actually see. Send the full report, not just the worst-looking hop.

Test throughput

Test against a nearby destination first. A distant or busy speed-test server measures the whole path, not just your VPS port. If you use Speedtest, use the official CLI, try more than one destination and note the time. One low result doesn’t show a fault. A shared port isn’t dedicated bandwidth. Results depend on source, destination, route and load, and a faster result yesterday doesn’t guarantee the same today. See Network Information and your plan details.

What to send support

Include:
  • The affected server and IP
  • The destination IP and port
  • The start time and timezone
  • The direction of traffic, and whether other networks work
  • MTR text, speed-test destination and results, and any exact application error
If it started after an IP change, a network configuration edit or a location move, say so. Don’t keep changing IPs while we investigate a routing fault.