Troubleshooting latency/packet loss
## UnderstandingHigh latency (commonly called **ping**) and packet loss
can make your applications feel slow or unstable. Latency is the delaytime measuredit in millisecondstakes for data to travel from your clientdevice to the server and back. High latency (sometimes called ping) results in slow response times, whileback; packet loss occurs when some packets are dropped entirely during transmission. Both issues can cause rubberbanding,rubber‑banding, timeouts and poor user experience.
### **Diagnosing latency and& packet loss
-
* **Use ping/MTR/traceroute**tools – Thelike `ping` command measures round‑trip time;, `traceroute` or the combined tool `mtr` showto measure round‑trip time and see each hop along the path to theyour server. High latency or packet loss on the first hop indicates a local or ISP issue, while problems mid‑path or near the destination may be outside your control.
- * **Test from multiple locations/networks** – Compare results from different networks (e.g.,for example, your home connection vs a mobile data vs home connection) to isolate whether the problem islies on your local network.
network or somewhere else.
- ###Monitor your server’s CPU and memory usage. A busy server can introduce delays if it is overloaded.- Check the network interface statistics on your server (`ifconfig` or `ip -s link`) to see if there are errors or dropped packets.
**Common causes of high latency
*- **Physical distance*distance:* –* The farther your deviceusers isare from the server, the longer packets take to travel. HostingChoosing closera server location close to your usersaudience or using a content‑delivery network (CDN) reduces physical distance【494653167984759†L223-L241】.
*distance.
- **Network congestion:** Heavy web pages / network congestion** – Websites withpages, large images and multiple third‑party scripts increase load times,times. Congested networks or busy routers and congestedswitches networkscan add delay【494653167984759†L253-L258】.
*delay.
- **Transmission medium*medium:** –Wired WirelessEthernet connectionsgenerally usually have higher latency than wired Ethernet; fiber tends to havehas lower latency and less interference than copper【494653167984759†L260-L266】.
Wi‑Fi. *Using a wired connection, upgrading to fibre or replacing old cables can help.
- **End‑userHardware andor hardwaresoftware issues*on the client side:* –* Latency can be caused by the client device running out of CPU/memory or by faulty cables, routers, switches or firewalls【494653167984759†L268-L279】.
network
interface ###cards. Ensure your local equipment is in good working order.
**Causes of packet loss
-
Common**Faulty sources of dropped packets include a faulty Ethernet porthardware or
cable,cabling:** issuesDamaged withcables, thefailing switches or network interface
cardcards (NIC),can outdateddrop routerpackets firmware,before they reach the destination.- **Congested links:** When a network link is saturated, routers and switches may drop excess packets. This is common during peak usage hours.- **Wireless interference:** Wi‑Fi networks are susceptible to interference from other devices and obstacles. Switching to a wired connection can reduce packet loss.- **Misconfigured firewalls or
networksecurity congestion【276561159420333†L156-L162】.appliances:** PacketAggressive filtering rules, QoS policies or DDoS mitigation can inadvertently drop legitimate traffic.- **Upstream provider issues:** Issues with your ISP or upstream carriers can cause packet loss
outside your control. Performing tests from different networks helps identify such cases.
**Mitigation tips**
- Choose a server location close to your users to reduce latency and use a CDN to serve static content from edge locations.
- Optimise your website or application: compress images, enable HTTP/2, cache assets and minimise third‑party scripts to reduce page load times.
- Use wired connections wherever possible and upgrade networking hardware to handle the required throughput.
- Monitor your network and server health regularly, and address resource bottlenecks (CPU, RAM, disk I/O) that can occurcontribute evento onlatency.
- high‑speedIf connections【276561159420333†L148-L155】.
indicate ###the Quickproblem fixeslies foroutside your network, contact your ISP or IllusionCloud support with traceroute outputs and timestamps so they can investigate with upstream providers.
By diagnosing the root cause and following these mitigation steps, you can reduce latency, prevent packet loss and latency
a *smooth **Minimizeexperience local congestion** – Close bandwidth‑heavy applications and pause downloads or updates【276561159420333†L170-L175】.
* **Power cyclefor your router** – Rebooting clears router memory and can resolve transient issues【276561159420333†L177-L179】.
* **Check cables and ports** – Swap to a different Ethernet port on your router and try a new cable; worn cables and bad ports often cause packet loss【276561159420333†L180-L184】.
* **Use wired connections** – Switch from Wi‑Fi to a wired Ethernet connection to eliminate wireless interference【276561159420333†L186-L188】.
* **Update firmware and enable QoS** – Log into your router’s admin interface to install firmware updates and enable Quality of Service (QoS) to prioritize real‑time traffic【276561159420333†L196-L224】.
* **Upgrade hardware** – Older routers and network cards may struggle under load; upgrading to modern equipment (e.g., Wi‑Fi 6) can reduce packet loss【276561159420333†L233-L244】.
users.
### Improving latency and packet loss in the data centre
If tests show the problem is near the server or across the internet, you may need to:
* Choose a server closer to your audience or use a content‑delivery network to reduce the distance packets travel【494653167984759†L223-L241】.
* Work with your ISP to investigate congested peering links.
* Ensure your server is not overloaded; high CPU or I/O on the server can delay responses.
* Contact IllusionCloud support with your MTR or traceroute results and timestamp; they can check upstream providers for routing issues.
### When to contact support
If troubleshooting doesn’t resolve the issue and packet loss persists outside your local network, gather the following before opening a ticket:
1. Ping and traceroute results to the affected server, captured at different times.
2. Details about your connection type (wired/wireless), modem/router model and firmware version.
3. Whether the issue persists on other networks or devices.
Provide this information in your support request so network engineers can pinpoint the cause more effectively.
