Netduma Fraser

It's not necessarily the ping that is the issue but your routing to the server can be unstable, I still believe it is a game side issue though given your connection in matchmaking is fine

They will have a better connection then, you can't beat the distance if that's your closest server

@Mostwest thank you for the suggestions! There is a limited amount we can do via the software but we're doing what we can We kind of already have the functionality for that but I don't know if there are plans currently to make this active For our customer base I think this is a bit overkill and would drive up the price quite a lot and exclude a lot of our customers as there are very few who have over 1Gbps Could you expand on what you mean exactly? You can make custom rules to prioritize ports currently

No improvement whatsoever in the results? Was this with Congestion Control set to Always? It's unlikely, as I mentioned previously, if your matchmaking games are fine then it doesn't look like an issue on your end and more likely something on the game side

Did you do the Congestion Control method I mentioned above?

There are broad percentages you haven't tried, you should go in 10% invertals, then when you get some good results go 5% either side of that number and doing that you can fine tune it. DHCP is fine, it doesn't make a difference. Don't deny the peers, they're probably servers, it is a server based game, also don't use the Geo-Filter for private games.

What percentages for Congestion Control have you tried?

Those are quite good results, you'll need to keep experimenting with the Congestion Control percentages to see which give the best results.

There is no export/import feature for the entire router but it has been suggested, as well as the LEDs on/off, they're on our roadmap so we plan to implement them in the future.

With share excess off yes that is how it would work

Some people say that they find it helps with lag compensation, it's worth a try if that's something you feel you're struggling with, otherwise no need

All 3 features can be used at once if you wish to, if you're wanting to throttle specifically and the TP rule is prioritizing then disable that. You don't really need to change BA just for gaming, it uses very little bandwidth and giving it more won't make it use it. As long as it has ~1Mbps then you're good!

Congestion Control is the easiest way to limit it, if you have Traffic Prioritization running then this will supersede Congestion Control/BA so might be what you're experiencing there

Yes that's right, keep us posted!

Everyone has a different connection, what works/doesn't work won't necessarily apply to others, even in the same area using the same internet provider. There is no way to make changes for just one game type. Can you provide a screenshot of your QoS page please?

No, there is no networking reason on your side that it would work for one but not the other so it's likely due to the server they're using for private matches unfortunately

Disable QoS fully from the menu on Congestion Control, does that make any difference?

Are people from other countries in the private matches?

Hey, welcome to the forum! In a private game with opponents you can't control the server you connect to, if you're playing EU or US for example you could get put on a server quite far from you. You can still use the Geo-Filter to identify and ping the server in a private game, then compare that with the ping to the server you get when using normal matchmaking.

I would assume that's because it's a beast of a router hardware wise and so for the R2 for example you may need to throttle more aggresively than the 700 to achieve the same performance

Sei davvero il benvenuto, è fantastico sentirlo, grazie per l'aggiornamento!

The next firmware isn't too far off, I haven't had a chance to test whether this particular issue is fixed but I'll pass it onto the team to check.

Best to let Netgear figure it out I think, you've done really well to prove that there is no set way to reproduce it, well done on getting it working as well!

It's weird given in reset 2 & 3 that you started in the same way and one caused it to break and the other didn't, which would lead me to believe there isn't necessarily one way to always reproduce it

Once the 500 is done we can then proceed with the 700 and hopefully shouldn't be too long after