Networking details I found out with Wireshark. Possibly an issue with handling packets out of order.
When I started playing Warzone one of the first things I noticed were the server issues. The servers were laggy and people were skipping around. I quickly found out about the internal statistics in the options and to my surprise the UI showed packet loss values of over 100%.
This of course is not possible and I wanted to investigate what is the real packet loss value. The game does not allow you to run Wireshark (or pcap) on the same computer. I guess that is kind of a security measurement. I routed the traffic through another computer and run the network analysis in there. I ended up writing a small parser for the game data that counts the real packet loss values of the last 1000 packets .
So here are some details that I have picked up:
1. First of all, the servers do send packets to the client (tick rate) at about 21 hz intervals. My guess is that their simulation step is exactly 48 ms long. 2. The servers (or at least their public IP addresses) are all over the place and hosted by multiple different companies. I have seen Blizzard, Amazon, Google cloud, Host Europe GmbH, UK2.net and multiple other IP addresses of the servers. (In Europe) 3. Some hosts work just fine even during the high traffic and some servers do not work at all. 4. Even if there is no packet loss sometimes the game does not run well. Maybe the servers do not have enough CPU power to calculate all simulations. I have no proof of the cause of course, but the packet loss can be 0 and the game is not really playable. 5. Sometimes the data packets are split into two and sent at the same step. This is not inherently wrong even though the internet seems to think so. Would you rather not have this data at all?
There seems to be an issue with the split packets with some hosts. The game really does not seem to like when the packets arrive out of order. Sometimes if the packet is split into two the smaller packet arrives 0-0.5 ms before the full size (1250 bytes) packet. The game does show weird packet loss percentages at this case.
This is an example from yesterday, the Server IP is owned by Choopa LLC. The sequence number is from their proprietary internal packet frame. Also the data length is from their frame and is a bit smaller than the UDP payload. It might be that they can handle this situation (by having a buffer of 1 for example) but I doubt that based on the bad gaming experience.
Server IP Timestamp (delta ms) seqno data payload 173.199.67.5 1587583123,038 ( 48,4), seq: 8631, len: 438, Calc:( 584 elements): average delta: 47,779 ms (20,930 hz) 173.199.67.5 1587583123,038 ( 0,4), seq: 8630, len: 1250. 173.199.67.5 1587583123,086 ( 48,0), seq: 8633, len: 228, Calc:( 584 elements): average delta: 47,784 ms (20,928 hz) 173.199.67.5 1587583123,086 ( 0,5), seq: 8632, len: 1250.
TLDR: The servers are most likely rented from 100 different places, some work better than others. There might be an interesting networking issue with the split packet handling.