@EA_Illium here you go. Done on chromebook/linux
1st result
traceroute easo.ea.com
traceroute to easo.ea.com (159.153.64.173), 30 hops max, 60 byte packets
1 100.115.92.193 (100.115.92.193) 0.111 ms 0.042 ms 0.938 ms
2 100.115.92.25 (100.115.92.25) 0.399 ms 0.598 ms 0.316 ms
3 fritz.box (192.168.178.1) 4.306 ms 4.056 ms 5.461 ms
4 65.7.69.111.static.snap.net.nz (111.69.7.65) 16.791 ms 16.572 ms 16.480 ms
5 * * *
6 TWODEGREES-svc063403-ic344202.c.telia.net (62.115.175.227) 147.769 ms 140.843 ms 140.196 ms
7 las-b24-link.telia.net (62.115.175.226) 142.007 ms 145.185 ms 139.850 ms
8 * * *
9 * * *
10 4.79.23.202 (4.79.23.202) 207.813 ms 205.309 ms 205.051 ms
11 159.153.92.10 (159.153.92.10) 202.596 ms 200.770 ms 199.811 ms
2nd result
$ traceroute easo.ea.com
traceroute to easo.ea.com (159.153.64.173), 30 hops max, 60 byte packets
1 100.115.92.193 (100.115.92.193) 0.029 ms 0.017 ms 0.017 ms
2 100.115.92.25 (100.115.92.25) 0.239 ms 0.130 ms 0.386 ms
3 fritz.box (192.168.178.1) 11.608 ms 10.044 ms 9.890 ms
4 65.7.69.111.static.snap.net.nz (111.69.7.65) 16.158 ms 16.038 ms 15.949 ms
5 * * *
6 TWODEGREES-svc063403-ic344202.c.telia.net (62.115.175.227) 141.649 ms 140.128 ms 139.732 ms
7 las-b24-link.telia.net (62.115.175.226) 175.710 ms 175.620 ms 175.513 ms
8 * * *
9 * * *
10 4.79.23.202 (4.79.23.202) 205.124 ms 204.593 ms 204.511 ms
11 159.153.92.10 (159.153.92.10) 200.952 ms 199.478 ms 200.783 ms
EA Staff (Retired)@The_Bro2021 It looks like the last serval hopes to our servers start getting higher ping times:
6 TWODEGREES-svc063403-ic344202.c.telia.net (62.115.175.227) 141.649 ms 140.128 ms 139.732 ms
7 las-b24-link.telia.net (62.115.175.226) 175.710 ms 175.620 ms 175.513 ms
8 * * *
9 * * *
10 4.79.23.202 (4.79.23.202) 205.124 ms 204.593 ms 204.511 ms
11 159.153.92.10 (159.153.92.10) 200.952 ms 199.478 ms 200.783 ms
They both seem consistent at the same location in tests 1 and 2 starting at the location: "TWODEGREES-svc063403-ic344202.c.telia.net", can you run a pathping to check for any packet loss? Also to confirm you were able to go through all the steps above?
Hi @EA_Illium , Any chance you know how to do this on linux terminal? I keep getting the following error.
~$ traceroute -S -q 30 easo.ea.com
Bad option `-S' (argc 1)
Yes, tried all of the steps above.
Cheers
EA Staff (Retired)@The_Bro2021 For a path ping you will want to use the 'mtr' command ( you can add options but I would just let it run without, you can find more details here)
Command: (should look like this)
mtr easo.ea.com (enter)
If the above does not work try this from the desktop " Ctrl +Alt+t and in the command prompt enter $ mtr followed by the IP address"
Command:
tracerouter easo.ea.com (enter)
For a traceroute it should be the same as you ran it when you first uploaded, I'm not familiar with how the additional command like -s work my guess is it needs additional input for that to function.
If you could run the mtr (pathping) and attached we can further check into this.
[CM - added additional info]
Community Manager
