When we get issues with our gameplay or internet connection the first thing customer service asks is usually regarding our home network.
It can be annoying if we have been through the tests several times previously.
I find it helps to know what I am talking about and if they sense this they are less likely to go through the grind which can be a real chore.
A free tool that I use from time to time on the laptop is Pingplotter.
This can help spot issues on the home networks and potential issues further down the connection to where you are connecting to.
On this graph, I tested on WiFi to be able to replicate Packet loss on the router. By changing the polling period from 2.5 seconds to .5 seconds.
On wired ethernet, the ICMP (ping) packet loss did not materialize.
This is a perfect example of why playing over ethernet is generally better.
If you can’t test wired then try a few different poll intervals.
Your WiFi may react the same as mine did on .5 second intervals.
If you are getting packet loss on the router with a polling interval of 2.5 seconds then you have an issue on your network.
Hop 1 is usually the home router or a device in a form of bridge mode. Hop 2 can be the actual router if you have a bridge mode setup.
You should know your home setup, but if you don’t, use the tool and put in any IP address and see what shows up.
If the 1st two hops start with 192.168.xxx.xxx.
Routers and modems tend to start with 192.168.xxx.xxx but not always.
Some devices use 10.xxx.xxx.xxx for example.
Once you know your home network you can determine which device or not have issues.
Referring back to the graph…
The 1st hop is my router. The next is the start of the ISP network.
The “next” hop spiking can be an issue caused by your home network which doesn’t show up till the 1st ISP hop. But also the second hop can be caused by a problem anywhere from after the router to the 1st ISP network node.
I sometimes get a bit of play on the second hop when it is very windy where I live.
This could be due to more people staying at home during bad weather, using more bandwidth in the area. And/or it could be local cabling being exposed to the elements causing i
Searching for issues further downstream is hit and miss.
Because of the way ISP and tier networks run their systems, it doesn’t always mean there is an issue if you see spikes or some packet loss.
Unfortunately, the only way to be more sure there is an issue downstream is to check the route to game server locations regularly.
Over time you will get to know your connection and the signs when it will normally play worse for FIFA.
If you get good gameplay and no spiking etc but get spiking and some packet loss when you get bad gameplay, the networks transporting the packets are likely being transparent and you have clearer evidence where the issue.
The problem is some networks don’t handle ICMP and hide the info.
I never view it as a good sign when networks hide info. I suggest they have something to hide.
My graph shows all the hops. A good sign.
But this one hides through the Orange network and the Amazon Web Services network.
Pingplotter has a free trial and after that it is still free to use for basic testing which is good enough for us.
I am using the free version.
You can go to the website from here , https://www.pingplotter.com/, and download the relevant version.