Network issues

[Arktoza]

Hello there,
as you can guess i got some connection issus in the evening at around 6-10pm. It was all fine untill they changed the server location. I am from germany and i am playing on Moogle. Its not on my side i think since everything else is working fine (youtube,steam,etc). Is there something i can do or do we all just have to wait?

[Risvertasashi]

Run WinMTR pointed at Moogle during the times that you have issues. Paste the results here and it might give us a better picture of where to start.

[Arktoza]

So i checked it with the program and this is what happened.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Speedport.ip - 1 | 1234 | 1226 | 1 | 5 | 209 | 2 |
| 217.0.119.26 - 1 | 1238 | 1231 | 18 | 24 | 404 | 18 |
| 217.0.77.34 - 1 | 1227 | 1217 | 18 | 25 | 407 | 21 |
| f-ed5-i.F.DE.NET.DTAG.DE - 1 | 1227 | 1217 | 20 | 27 | 412 | 23 |
| ffm-b12-link.telia.net - 1 | 1234 | 1226 | 20 | 26 | 412 | 22 |
| ffm-bb1-link.telia.net - 1 | 1223 | 1212 | 21 | 41 | 410 | 34 |
| ffm-b10-link.telia.net - 1 | 1231 | 1222 | 21 | 27 | 411 | 24 |
| kddi-ic-301630-ffm-b10.c.telia.net - 1 | 1238 | 1231 | 21 | 28 | 413 | 22 |
| 195.82.60.29 - 1 | 1223 | 1212 | 21 | 27 | 413 | 21 |
| 195.82.61.14 - 1 | 1223 | 1212 | 21 | 27 | 412 | 23 |
| 195.82.50.234 - 1 | 1235 | 1227 | 21 | 27 | 412 | 21 |
| 195.82.50.55 - 1 | 1226 | 1216 | 21 | 27 | 412 | 23 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

The problems mostly happened in trials or dungeons and this is from just playing normal in the overworld.

Edit: The game kicked me out while walking around

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Speedport.ip - 2 | 2007 | 1985 | 1 | 5 | 209 | 2 |
| 217.0.119.26 - 1 | 2014 | 1994 | 18 | 26 | 1098 | 19 |
| 217.0.77.34 - 2 | 2003 | 1980 | 18 | 26 | 640 | 19 |
| f-ed5-i.F.DE.NET.DTAG.DE - 2 | 2011 | 1990 | 20 | 28 | 860 | 23 |
| ffm-b12-link.telia.net - 1 | 2015 | 1995 | 20 | 28 | 895 | 23 |
| ffm-bb1-link.telia.net - 2 | 2003 | 1980 | 21 | 41 | 642 | 21 |
| ffm-b10-link.telia.net - 2 | 1999 | 1975 | 21 | 29 | 1087 | 23 |
| kddi-ic-301630-ffm-b10.c.telia.net - 1 | 2015 | 1995 | 20 | 30 | 986 | 20 |
| 195.82.60.29 - 2 | 1999 | 1975 | 21 | 27 | 413 | 26 |
| 195.82.61.14 - 2 | 1995 | 1970 | 21 | 29 | 1091 | 22 |
| 195.82.50.234 - 1 | 2015 | 1995 | 21 | 28 | 1078 | 22 |
| 195.82.50.55 - 1 | 2014 | 1994 | 21 | 28 | 1008 | 21 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Risvertasashi]

Edit:

Ok, you've got some routing issues.

First do what Worldofneil suggests. If you're sure it's not your own router:

In the US, we have similar problems with a backbone provider known as Level3. The usual suggestion (which worked for me personally) is to get a VPN that will allow you to route around the bad nodes. Some VPNs marketed towards gamers are WTFast, Battleping, Pingzapper, and probably many more a quick Google would turn up. Some have free trials you can test with.

Unfortunately, 217.0.119.26 probably belongs to your ISP so it might not necessarily help in your case. You can call your ISP and complain (In the US this gets nowhere but maybe Germany is better?). Keep this WinMTR data handy as it will help their engineers diagnose the problem. But first do rule out your own home router (maybe gather some winMTR data plugged into the modem directly?).

[worldofneil]

Assuming Speedport.ip is your own router (which it very likely is as that's the first hop) I would recommend rebooting that and seeing if it fixes things. I only mention that because although the average is ~5ms which is respectable (still higher than I'd expect, but meh) on both of them it has a "worst" ping of 209ms which is insanely high for something on your own local network.

The rest of the route seems to have a decent average too, but a high "worst" (so a spike), but you need to remove the initial spike in your own hardware first as that could be skewing the rest of the results.

Also if you have a second computer in the house, try the route tracing on that and see if you get that occasional spike on your own router (might be just related to individual computer rather than the router itself)

[Arktoza]

Well it is really since the server location changed it kicked me out yesterday in Castrum Meridianium and Praetorium. Today during Ifrit and Garuda (hard) and in sunken temple of quarn. Before the change i never had any issues so im just guessing that it has something to do with the server. But i can scan it tomorrow during a trial.

I rebooted the router yesterday and today so i dont think its because of it.

i traced it with the cmd as well

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Edgar>ping 195.82.50.55

Ping wird ausgeführt für 195.82.50.55 mit 32 Bytes Daten:
Antwort von 195.82.50.55: Bytes=32 Zeit=32ms TTL=53
Antwort von 195.82.50.55: Bytes=32 Zeit=21ms TTL=53
Antwort von 195.82.50.55: Bytes=32 Zeit=21ms TTL=53
Antwort von 195.82.50.55: Bytes=32 Zeit=29ms TTL=53

Ping-Statistik für 195.82.50.55:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 21ms, Maximum = 32ms, Mittelwert = 25ms

C:\Users\Edgar>tracert 195.82.50.55

Routenverfolgung zu 195.82.50.55 über maximal 30 Hops

1 3 ms 2 ms 2 ms Speedport.ip [192.168.2.1]
2 21 ms 21 ms 20 ms 217.0.119.26
3 18 ms 20 ms 19 ms 217.0.77.34
4 25 ms 25 ms 21 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.34]
5 25 ms 22 ms 22 ms ffm-b12-link.telia.net [213.248.103.169]
6 119 ms 22 ms 23 ms ffm-bb1-link.telia.net [62.115.140.18]
7 57 ms 34 ms 23 ms ffm-b10-link.telia.net [62.115.137.223]
8 25 ms 25 ms 22 ms kddi-ic-301630-ffm-b10.c.telia.net [62.115.32.110]
9 22 ms 158 ms 22 ms 195.82.60.29
10 23 ms 21 ms 23 ms 195.82.61.14
11 31 ms 26 ms 23 ms 195.82.50.234
12 36 ms 27 ms 27 ms 195.82.50.55

Ablaufverfolgung beendet.

C:\Users\Edgar>

[Risvertasashi]

Well it is really since the server location changed it kicked me out yesterday in Castrum Meridianium and Praetorium. Today during Ifrit and Garuda (hard) and in sunken temple of quarn. Before the change i never had any issues so im just guessing that it has something to do with the server. But i can scan it tomorrow during a trial.

Unfortunately, these days, it's more often that intermediary nodes have issues than the endpoint. Chances are SE's servers are operating perfectly; but changing the geographic location does change your path to the servers. It's not really anything Square can fix (Other than offering more locations, like this recent EU addition).

I almost can't play at peak hours if I don't use a VPN because level 3 is so bad. At least your packetloss there is only 1-2% and pings only go up to 1k or so.

But really, do what worldofneil says. Home routers are notoriously fickle. If you rule that out, at least when you make a complaint you'll be taken more seriously (First thing an ISP will do when you call them is ask if you have a router...)

Also if you have a second computer in the house, try the route tracing on that and see if you get that occasional spike on your own router (might be just related to individual computer rather than the router itself)

I think he means use WinMTR. tracert is not a good tool because it only looks at stuff "in the moment." Your issue is erratic so something that can take a longer term look is essential to try pinning this down.

[Raist]

Latency is spiking to 4x or higher then the norm at some hops along the way. Looks like peering through telia in general was not ready for the sudden increase in traffic. It may eventually clean up depending on how route announcements are managed, but you should be able to forward your data to your ISP's Tier3 support for a proper investigation. Sometimes they may be referred to as Engineering. You need that higher level of support for this...not the lower level help desk teams that look at localized issues. The problem is upstream and management by higher level support.