More information:
CODE: LEAF/NET
First some context as to what these errors mean:
Back at launch we had a few different things that would display an overly generic timeout error, and the problem was that it could mean 4 different things (only one of which was a true timeout). So we added 4 different error strings and put random words in each one so that we could differentiate them both at the customer support level and also on our error tracking backends.
In our 1.2 patch, users started getting this more often. The consistent report is that it happens after an extended time on the Kings Canyon load screen just after a match starts.
The vast majority of players reporting the error are getting code:leaf. This means the backend created a match, our servers successfully talked to one another, we sent users there, and the player never got an answer from that new server.
We then gathered enough data to prove that servers don't think clients are timing out, but clients think servers are timing out. That was a strange finding. We also verified that we aren’t launching matches that are partially full - so code:leaf seems to hit every single player on that match server, not just some players.
So we’ve been investigating a lot of situations that could be causing this and working our way through theories to see what it could be and steadily eliminating possibilities. In addition to the work ongoing on our end, we’ve also been working with Multiplay and data teams to gather more telemetry.
We’ll keep you all updated on progress as we continue to work on this.
Source
Status
