Materia server repeated lost connection

[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.

[Shibi]

And just in case a SE community rep does read this,

My further testing is also showing 20% packet loss ( timestamp 2022-06-06T22:34:18+1000 ) at the SE/NTT router 202.68.69.101 in addition to the above.

So, it's possible there are two faults at play here. The busy Telstra router in Kent Street which SE can't deal with, but also a problem in the game's datacentre. I also see the 202.68.69.101 packet loss problem from my ABB side, but it's not enough to kick me off on it's own - it does explain the lag spikes though!

Hopefully a community rep reads this and can please pull the strings to have the NTT/SE NOC look at AEST/AWST peak-time packet loss on SE's 202.68.69.101 IP

Thank you SE.

[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.

[Jayvenpup]

And just in case a SE community rep does read this,

My further testing is also showing 20% packet loss ( timestamp 2022-06-06T22:34:18+1000 ) at the SE/NTT router 202.68.69.101 in addition to the above.

So, it's possible there are two faults at play here. The busy Telstra router in Kent Street which SE can't deal with, but also a problem in the game's datacentre. I also see the 202.68.69.101 packet loss problem from my ABB side, but it's not enough to kick me off on it's own - it does explain the lag spikes though!

Hopefully a community rep reads this and can please pull the strings to have the NTT/SE NOC look at AEST/AWST peak-time packet loss on SE's 202.68.69.101 IP

Thank you SE.

I double checked to see if our issue was 'ken' as well but is more vague but still the same node before and after 'ken'

[Skattered]

i bought a brand new router and cables. still happening. in fact i cant get even get through the login area. keep getting 2002. This disconnections happen to alot of us, and its all from Materia server. there must be something wrong here.

[AffGnome]

Still ongoing for me too - contacted isp and they have tried changing my routing twice now through different nodes - and still investigating but they are unsure what’s causing it at this point barring something on FFs side

[LordGiggles]

Well that's something at least, my ISP just told me that it must be an issue with my router lol, they clearly don't handle going off script well.

Would def be worth running MTR (winMTR most likely) if yours is actually looking into it already, might just be able to tell them where the issue is, assuming it's the same problem.

[Shibi]

I double checked to see if our issue was 'ken' as well but is more vague but still the same node before and after 'ken'

Those Telstra Sydney nodes are not ideal, and although I don't get DC'ed I am still personally seeing packet loss on 202.68.69.101 (that belongs to SE/NTT).

I think we need to keep gathering evidence. The more people who can do a tracert during a failure, or keep an MTR running and post those results (blurring out IPs on the first three steps) will help everyone. It will show patterns that we can hopefully then approach SE with, or Telstra with (which is painful sometimes), or whatever we need to do.

The problem is widespread enough that it's not imagined, and there is preliminary fault-finding to show it's not local to us too.

[AffGnome]

Absolutely, I’ll start running Winmtr when I’m playing the game and targeting the DC provided in the post by Yoshi about packet loss - I’ll also update here if my ISP come back with a resolution

[AffGnome]

This is what i got during the last disconnect i do have it set to 153.254.80.65 - but resource monitor connects me to 153.254.80.75? which one should i be using?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| - 0 | 1930 | 1930 | 0 | 0 | 14 | 0 |
| ge-0-5.sydgsbng3.wireline.com.au - 1 | 1927 | 1926 | 6 | 6 | 14 | 6 |
| po64-1-40.sydgsbdr0.wireline.com.au - 1 | 1927 | 1926 | 7 | 8 | 109 | 8 |
| atm11-0-0-61.sb3.optus.net.au - 1 | 1923 | 1921 | 7 | 8 | 43 | 8 |
| No response from host - 100 | 388 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 388 | 0 | 0 | 0 | 0 | 0 |
| 124.19.61.3 - 1 | 1864 | 1847 | 8 | 10 | 30 | 10 |
| 220.101.73.98 - 2 | 1850 | 1830 | 8 | 9 | 39 | 9 |
| ae-28.r20.sydnau02.au.bb.gin.ntt.net - 1 | 1901 | 1894 | 8 | 12 | 143 | 9 |
| ae-1.r21.sydnau03.au.bb.gin.ntt.net - 1 | 1901 | 1894 | 8 | 12 | 112 | 9 |
| 199.245.24.25 - 1 | 1905 | 1899 | 8 | 9 | 58 | 10 |
| 153.254.80.65 - 1 | 1898 | 1890 | 8 | 9 | 48 | 10 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


UPDATE: ISP is now attempting to assign me a static IP - not in place yet but captured below when another disconnect happened



|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|
| po64-1-40.sydgsbdr0.wireline.com.au - 0 | 10 | 10 | 9 | 10 | 12 | 11 |
| atm11-0-0-61.sb3.optus.net.au - 0 | 10 | 10 | 10 | 11 | 14 | 11 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 59.154.142.40 - 0 | 10 | 10 | 12 | 13 | 14 | 14 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|