Materia server repeated lost connection

[LordGiggles]

Well, can't be 100% certain, but going off mtr the issue seems to be pretty focused on one step in particular.

Normal play the reports more or less look like this



But when the game is frozen up in the period right before it entirely kicks me back to menu, or out of the game if I'm trying to log in, it looks like this.



Like has been said a few times now, seems to be an issue with ntt, I assume (or a link between them and telstra?).

I was in a frontline match when this occurred, though I doubt it matters, and it's happened in a heap of different contexts anyway. Happened at around 8:10pm AEST today, so 2022-06-06.

[Shibi]

...

Yay! That's exactly what is needed. (and why MTR is good as it just runs in the background until the fail happens). So, thank you

If I MTR the following step from my ABB connection (which doesn't fail with disconnects, as it normally doesn't go through Telstra) I can replicate some of the issue, and certainly a point that is quite congested in Telstra's network.



although the following ntt1874239.lnk.telstra.net link is also bad, it's the -ken- link that is problematic to me..

I wonder, if anyone who is seeing this problem is not passing through the Telstra network? This can be seen with a simple tracert at any time, look for that .ken.edge903 line.

Edit: and this ken-edge903.sydney.telstra.net device likely lines up with Jayvenpup tracert a few posts above too, where it's showing the * timeouts.

[Jayvenpup]

Well, can't be 100% certain, but going off mtr the issue seems to be pretty focused on one step in particular.

Normal play the reports more or less look like this



But when the game is frozen up in the period right before it entirely kicks me back to menu, or out of the game if I'm trying to log in, it looks like this.



Like has been said a few times now, seems to be an issue with ntt, I assume (or a link between them and telstra?).

I was in a frontline match when this occurred, though I doubt it matters, and it's happened in a heap of different contexts anyway. Happened at around 8:10pm AEST today, so 2022-06-06.

This was exactly what I was about to reply with too actually. I had MTR running when the crashed occured just a few minutes ago and the times I used Traceroute, it showed up as the 11th node was timing out. Using MTR, it shows it as exactly that spot too. I've sent this through as a report as well as posting here.

Also, I expected to see packet loss happening before it crashed but it didn't. My wife said "I think it is about to crash" and MTR didn't show anything above 1% but after it crashed, I restarted MTR and it gave the below result.