Symptom guide
It disconnects, or everything arrives late
Playing from Australia means most game servers are a long way away, and some of what people try to fix is simply the distance. This page separates the part of the problem that is fixed by physics from the part that sits on your side of the connection, because only one of them responds to anything you do.
Quick answer
If the picture stays smooth but your actions register late, the problem is the network rather than the machine. Establish whether it is constant or intermittent: constant delay is usually distance to the server and is not something you can remove, while intermittent delay, dropouts and sudden jumps are usually local — wireless interference, another device saturating the connection, or equipment that needs restarting. Bandwidth is rarely the cause of either.
Three measurements that get confused with one another
Almost every unproductive conversation about game networking comes from treating these as one thing. They are independent, and a connection can be excellent on one and poor on another.
- Latency
- How long a single message takes to reach the server and come back. This is what determines whether a game feels responsive. It is governed mostly by distance and by the number of network hops along the way.
- Bandwidth
- How much data the connection can carry at once. This determines how quickly a large file downloads. Games in play use remarkably little of it, which is why a fast connection does not guarantee a responsive game, and why upgrading a plan often changes nothing.
- Packet loss and jitter
- Whether messages arrive at all, and whether they arrive at an even rate. This is the cause of the effect where a character appears to snap back to where it was a moment earlier. Loss and jitter produce the worst experience of the three and are the least visible in any speed test.
The practical consequence is that a speed test showing a fast connection is not evidence that the connection is fine for gaming. It measures bandwidth, which is the one of the three least likely to be responsible.
What distance actually costs, and why no setting removes it
A message to a server on another continent travels the distance and back before anything happens on screen. That round trip is bounded by how fast a signal moves through cable, and no configuration on your machine shortens it. For a player in Australia connecting to servers hosted in Europe or North America, this baseline is simply present.
What this means in practice is that a game which offers a choice of server region is worth checking first, because selecting a nearer region is the only change that addresses the baseline at all. Where a game offers no such choice, the baseline is a fixed feature of playing that title from here, and effort is better spent on the intermittent problems, which are fixable.
Matching the symptom to the layer
| What you see | Usually indicates | Can you change it? |
|---|---|---|
| Constant delay between action and response | Distance to the server region | Only by choosing a nearer region, if the game allows it |
| Characters snapping back to earlier positions | Packet loss or jitter | Often yes — usually wireless or local equipment |
| Brief freezes, then the game catches up | Another device saturating the connection | Yes, by finding what else is transferring |
| Disconnection at roughly the same time each day | Scheduled activity on the network, or a service window | Sometimes, once identified |
| Everything fine, then poor for everyone at once | The game's servers or a route beyond your provider | No — this is a report, not a repair |
Checks on your side, in a sensible order
- Find out whether anything else is using the connection. A household member streaming video, a console downloading an update in standby, or a cloud backup running on schedule will all produce intermittent game problems while looking perfectly innocent.
- Test on a wired connection if one is available. This is diagnostic rather than a recommendation. If the problem disappears, it is wireless, and the next steps are about wireless. If it persists, wireless is ruled out and you have saved yourself a long detour.
- Restart the network equipment properly. Powered down, left off for a minute, then back on. This clears a category of fault that no amount of reconfiguring will.
- Check whether the game offers a server region setting, and whether it is set to somewhere sensible. Automatic selection is not always right and is not always re-evaluated after it has chosen.
- Test at a different time of day. A problem that only appears in the evening is describing congestion somewhere, and that is useful information for the provider even though it is not a fix.
Wireless, which is the usual answer
When an intermittent problem turns out to be local, wireless is the most common single explanation. It is a shared medium in a crowded space, and it degrades in ways a cable does not. Distance from the access point matters, and so do walls, and so do neighbouring networks on the same channel — in an apartment building there may be many.
Two practical points are worth more than most advice on this topic. The first is that a wireless connection can show full signal strength and still be losing packets, because signal strength measures how loud the transmission is, not how cleanly it arrives. The second is that a device sitting midway between two access points in a mesh network may keep switching between them, and each switch is a brief interruption.
What you cannot fix, and where to take it
Some problems live between your provider and the game's servers, on infrastructure neither you nor the game operator controls. The signature is that everything else works normally while one game behaves badly, or that the problem starts and stops at times unrelated to anything in your household.
There are two useful reports to make. Your internet provider can investigate the path from your connection outwards, and a record of when the problem occurs is what makes that investigation possible. The game's own support channel can investigate the path at its end, and will usually ask for the same record. Making both reports with the same notes is more effective than making either one from memory.
On tools that promise lower latency
Products marketed as lag reducers, route optimisers or gaming networks work by sending your traffic through an intermediate server. That can shorten a poorly chosen route, and it can equally lengthen a good one, since the traffic now makes two journeys instead of one. Treat any claim of a guaranteed improvement with caution: the outcome depends on your connection, the game's servers and the route between them, none of which the seller knows in advance. Under the Australian Consumer Law, claims made to consumers must not be misleading, and the Australian Competition and Consumer Commission publishes guidance on what businesses may and may not claim.
Keeping a record that is worth something
- The date and time of each occurrence, including the time zone, since support teams are frequently elsewhere.
- Whether the problem was present on a wired connection as well as a wireless one.
- Whether other devices in the household were affected at the same moment.
- Which server region the game was set to, if it offers the choice.
Four lines of that sort resolve more support cases than a long description written afterwards from memory.