xXGEIGERXx_

I experienced  this on day 1 of launch of bo6 in every single game, I have stopped playing and waiting for the next update to fix these issues which would be likey season 1 update unlikely they will release a hot fix for this before then.
To everyone with this issue, there is nothing wrong with your set-up or anything you can do about it. It's the game, not your Internet or netdumar fault.
The game is broken, some people are just lucky to be on the advantage end of the gun fight they know this and they are abusing it. Reason why I taken a break from bo6 until it's fixed.

look at this guys this is me just in the game not even playing it shows every dedi avaible at that time all around the world  and the info ports it uses
 if i restart the game it wil show another loa again as it refreshes erveey timeyou restart the game
Protocol       source                              destination                       packets
IPV4 TCP 192.168.1.115:56043  185.34.106.33:3074    442.35 KB (1326 Pk
TCP 192.168.1.115:55194    185.34.106.33:3074     223.50 KB (364 Pkts.)
TCP 192.168.1.115:51856   40.67.254.36:443     7.48 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   95-179-204-207.choopa.net:42440       2.44 KB (36 Pkts.)
IPV4  UDP  192.168.1.115:3074  95.141.40.237:32990      1.32 KB (26 Pkts.)
IPV4  UDP  192.168.1.115:3074  6bb6e6b5.setaptr.net:33440      1.21 KB (24 Pkts.)
IPV4  UDP  192.168.1.115:3074   172.83.41.231:40140      1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    149.248.40.235:44030  1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    45.63.73.85.vultr.com:31360      1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    108.61.237.132.choopa.net:39710     1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    173.199.113.18.vultr.com:32930        1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    24.105.53.84:30020           1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    148.72.168.254:34800     1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074    d0270.colocat.ru:33000  1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074   151.106.62.202:31410     1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074   6bb6e9dd.setaptr.net:44740     1.21 KB (24 Pkts.)
IPV4 UDP   192.168.1.115:3074   173.199.114.99.reliableservers.com:44420    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    24.105.52.22:35700      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    185.225.209.247:34620   1.21 KB (24 Pkts.
IPV4 UDP  192.168.1.115:3074    149.28.184.240.vultr.com:34350   1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   108.61.111.235.vultr.com:33190    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   107.152.106.130:32350       1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   45.63.118.23:34910         1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   197-80-200-19.jhb.mweb.co.za:43080      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   177.54.157.188:44070      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    45.76.73.125.vultr.com:30230      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    24.105.17.142:44070    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    37.244.43.218:32530    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    173.199.67.132.choopa.net:43030     1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    45.63.102.90.vultr.com:42780      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    66.42.47.229.vultr.com:41130     1.21 KB (24 Pkts.)
 IPV4 UDP 192.168.1.115:3074   104.200.145.121:37980       1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   108.61.97.117.choopa.net:39680    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   142.54.238.29:30600     1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   104-156-240-56.choopa.net:34920    1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   45.63.47.54:40170     1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074   108.61.232.70.choopa.net:33220     1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    24.105.54.231:32160      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    155-138-178-39.choopa.net:39090      1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    103.198.33.18:34430        1.21 KB (24 Pkts.)
IPV4 UDP  192.168.1.115:3074    88.150.230.52:33660      1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074    43.251.181.170:35710    1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074    142.91.15.28:31440        1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074     ec2-157-175-91-112.me-south-1.compute.amazonaws.com:30020      1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074     95.177.169.42:30020        1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074     177.54.157.68:39250        1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074     107.6.100.202:38240       1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074     ec2-54-169-147-163.ap-southeast-1.compute.amazonaws.com:30020      1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074    192.170.153.186:44100       1.10 KB (22 Pkts.)
IPV4 UDP  192.168.1.115:3074    185.34.107.128:3074        683 B (16 Pkts.)
IPV4 TCP   192.168.1.115:52383     65.55.252.93:443         152 B (3 Pkts.)

You wouldn’t be blaming hitdetection for your loss if you were that good at the game
 
These traffic prio rules only function under the condition that your line is congested. Then it works because you get a buildup of packets in the sending que and it can put game traffic in front of the que. If no congestion occurs then each packet is send inmediately and the rule does nothing. Running QoS requires packet inspection and that does add latency, this is the trade-off for running QoS on your system. So therefore in situations with symmetrical connections with very few devices I would always recommend turning off QoS totally as this gives you the cleanest path for traffic. Ie I have 600/40 connection in one house where that connection services the whole home, there I have QoS on because it’s easy to congest a 40mbit upload line. In my other house I have 2x 600/600 WAN and the connection that is used for gaming doesn’t use QoS at all since I never congest it with just 1 PS4 and 1PC.
 
As for DumaOS classified games vs manual rules. You could argue that other UDP traffic will try to get in front of your gaming traffic (DumaOS classified games simply prioritizes UDP 1024-65535) but in reality this is not noticeable unless you are running something special that generates a huge UDP stream. And here again, it would require the line to be congested in the first place. Also you could add the device as game console and then it simply prioritizes UDP traffic to that device.
 
The only reason I use a manual rule is so that my bandwidth is not restricted when the game is running idle in the menu.

There is really no magic traffic prioritization rule. You will find many topics about it, people have spend countless hours with wireshark etc but none have the magic answer.
 

You have test 4 Routers?
Have you a bad routing / peering from your isp?
You can see it on Pingplotter i think.
You can see the Server IP in the R3 and can run ping plotter.
 
And the bad Gameplay is a lot of from Cheater an no recoil scripts.
The Ping or Paketloss and Hit detection is very strange, sometimes.

You can test your side of Gameplay and dont forget. A Lot auf Cheater... 😔

just wanted to add to this post. i have an R2 but i am in the Netduma RF2 Early access Forum where i have basically the beta version of duma os 4 ( not completey duma os 4 just have smartqos/favorites and stats for nerd. i have 500/500 fiber, i port forwarded my ports, use 1.1.1.1 in my router and 8.8.8.8 in my ps5 ( i do this cause for some weird reason i get better ping to 8.8.8.8. with 1.1.1.1 in my router dns setting than if i used 8.8.8.8..), ps5 ip static and upnp off. so the only setting i used was the bandwith allocation on the ports he shared and the hitreg has been amzing and on various pings to. im on a ps5 vs pc kids in rank on 20,44,70,88 ping and its been consistently great. 

From my tests, others can chime in, it didn't work.  I had to narrow the ports down.  That's when I begin to start to see a difference.  If it works for you go for it.   But for me, I always notice I was behind my teammates and it still took longer for my TTK. Not sure why that is.  Also, setting Anti buffer bloat to never helped me immensely!
Funny too because even though activision tells you set open all those ports the only port that UpnP recognize is 3074 (for others it's 3075).  I never saw those other ports open up.  But opening them up via port forwarding did nothing either (at least for me). And, I'm talking going back to BO4.
 
 

This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable.   It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers.  The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. 
The information provided to you is not a final on the research presented so far.  Furthermore, testing is ongoing.  It take this community as a whole to help gather more data/input to determine what works and what doesn't.  Please keep that in mind when reading this thread.  Thanks
Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread:
1. Reboot modem.  Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st).
2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip.  If private more then likely you have double nat.  In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to).  Afterwards you may need to reboot your modem then your router again in order for it to take effect. 
3. For your XR router make sure you Disable DumaOS Classified Games.
4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify.
5. Delete all existing rules if you haven't added these before.
6. Set Anti-Buffer Bloat settings to both 100 and set it to never.  (for me even on "Never" I'm still capped to ABB slider for up/down).  Test this to see if you notice any improvement.  If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players.  No more .5 seconds behind other players.
7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number).  Make sure that port corresponds with your console and not some other device.  It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so.  I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 
8. Adjust Bandwidth Allocation as needed.
9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp.
Source 3074-3075  -> Destination 3100-3500
Source 3100 - 3500 -> Destination 3074 - 3075 This is not needed for the actual game itself (it seems). You are prioritizing data about your stats more so then anything else. I've noticed at the end of the round that my rank up wouldn't animate (filling up the circle).  It would be instantaneous.  Albeit I was also prioritizing 2000-7000 udp as well.  This was/is unnecessary. Thanks @blackfirehawk for the tip.
Source 3074-3075 -> Destination 30000-45000
Source 30000-45000 -> Destination 3074-3075
Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules.  And make sure that the port for your console shows up in Upnp.  If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding.  
Thanks to @kinel, @GHOST-1-EC and others for the research.
 
 
Example (Best k/d yet for me):

 

 
Disclaimer:
This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience.  If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you.  These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc.
 
EDIT 12/21/19:

It appears that after a few updates things get borked with Modern Warfare (and BO4).  I found out that in order to get better fluidity in my movement I had to reinstall the game after about 2-3 updates.  The ranges above does indeed work 3074-3075 30000-45000 (in 5000-8000 increments). And for me, keeping ABB to never using 75% of my download speed (lowering it more with bandwidth allocation) seems to really bring the game up to par. 
I've found nothing else that would allow me to be ahead of everyone else in movement, etc so far.  If anything else comes up I would update.

https://www.waveform.com/tools/bufferbloat   This is the best and more accurate way of testing bufferbloat as DSL reports is a bit defunked unless you live in the U.S.