Raz0118 Posted February 1, 2016 Share Posted February 1, 2016 I cannot get Netduma to report ping less then about 45 ms in game (BO3 on XB1). When I run internet diagnostic it returns with "OK" ping and shows an average of 41 ms. Now I can run other ping tests and get much lower rates. Using http://www.dslreports.com/tools/pingtestfor example, I am able to get pings as low as 7 ms in Texas and I live in New Mexico. I have to go as far as New York (1,800 miles away) to get to 43 ms. This leads me to believe that there is some problem here but I cannot figure out what might be the cause. Any help would be greatly appreciated. For the record, yes I am hard wired. Link to comment Share on other sites More sharing options...
Zennon Posted February 1, 2016 Share Posted February 1, 2016 The Netduma pings 8.8.8.8 which is your nearest Google server, DSL reports must have a server closer to you. Link to comment Share on other sites More sharing options...
Raz0118 Posted February 1, 2016 Author Share Posted February 1, 2016 @Zennon The problem isn't as simple as that. I get pings at 43 for New York and 30 ms for California. That spans the country there... The problem is I cannot get pings less then 45 ms in game (as reported by the Netduma). In fact it seems EVERY game I get into is 45 ms. I can have the in game ping state that I am at that same ping or up over 100 ms (and playing very laggy) and yet my Netduma reports that I have 45 ms ping. I don't know why it does that but it seems to be inaccurate in that regard. If it is using that number when it decides my lobby then it will not be picking my lobbies correctly and that is really what I have an issue with. Also, it doesn't seem to be reporting the correct host information. http://imgur.com/tRTX6Wa This shows that I am connected to a dedicated server in Washington but when I run trace it stops in Kansas and then continues on to Washington. I can select the marker that it stops at and this shows me that it is indeed a peer connection. This is not going to help my connections if the router cannot even determine which connection is the host connection. Link to comment Share on other sites More sharing options...
Zennon Posted February 1, 2016 Share Posted February 1, 2016 The trace route information is not accurate from the Netduma. The sticking ping issue I would turn off the Netduma for 5 mins then return and retest. Link to comment Share on other sites More sharing options...
dominican_3niz Posted February 1, 2016 Share Posted February 1, 2016 <a href="http://www.dslreports.com/speedtest/2856784"> <img src="http://www.dslreports.com/speedtest/2856784.png"></a> Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 1, 2016 Administrators Share Posted February 1, 2016 It seems like you have a big radius, if you lower it to ~1000km with strict on and PA at 0. You'll get much closer games and as such should be able to achieve under 45ms Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.