Network speeds on PC vs Xbox One

Have you tried setting up port forwarding?

Also, how is the Xbox one connecting? Have you tried a wired connection?

I haven't tried messing with port forwarding only because uPnP is enabled. Also have open NAT. 

I am connected through Ethernet cable already. The weird thing is I was receiving my full speeds as of about 3 weeks ago. It's all of the sudden not running at full potential. 

TakeFlight23 said:
Also have open NAT. 

What do you mean you have open NAT? As per a XBL test or do you mean you have the gateway bridged? UPnP works, but it can be taxing on the routers performance. Sometimes port forwarding can produce better results, but I think in this case, your right.

TakeFlight23 said:
It's all of the sudden not running at full potential. 

Sounds like a issue with the Xbox test then. I have heard the way the test works doesn't work well with DOCSIS 3.0 devices. Shouldn't effect actual performance though, just the test. Are you having any actual problems with playing games? If so, what?

Also, have you tried doing a speed test using the Internet Explorer App and trying a speedtest that uses HTML5 and not Flash like this one: http://speedof.me/ or http://www.dslreports.com/speedtest

Per Xbox one test I have open NAT. I have ran test on the Internet explorer app not per website you listed but one not using flash. Getting around the same speeds on there. I also get packet loss up to 20% at times. I play a lot of sports games and the speeds are noticeable. Some games are unbareable to even play. 

TakeFlight23 said:
not per website you listed but one not using flash

Try one of the ones I gave. The Internet Explorer App is ** IMO, and doesn't handle flash, or any plugin for that matter, well. 

Something else you can try is to use Google DNS (8.8.8.8 and 8.8.4.4) as static DNS on the Xbox One. See here for more info.

Last, maybe try a tracert to XBL from your PC? I don't know what server your using, I couldn't find a list of XBL server IP's anywhere on their support site, but a tracert to Xboxlive.com might be a place to start. See here for a link how to run a tracert on your PC. Here is mine for comparsion;

Tracing route to xboxlive.com [134.170.29.210]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 7 ms 9 ms 10.2.48.1
3 8 ms 11 ms 8 ms ip98-190-161-114.ri.ri.cox.net [98.190.161.114]
4 11 ms 8 ms 9 ms ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
5 15 ms 15 ms 14 ms nyrkbprj02-ae3.0.rd.ny.cox.net [68.1.5.161]
6 14 ms 16 ms 15 ms ip70-167-150-253.at.at.cox.net [70.167.150.253]
7 17 ms 15 ms 16 ms ae0-0.nyc-96cbe-1b.ntwk.msn.net [207.46.38.113]
8 29 ms 27 ms 27 ms 104.44.8.118
9 26 ms 26 ms 27 ms be-4-0.ibr02.was05.network.microsoft.com [104.44
.4.28]
10 37 ms 36 ms 40 ms be-3-0.ibr02.bn1.network.microsoft.com [104.44.4
.27]
11 38 ms 58 ms 55 ms ae73-0.bn1-96c-2a.ntwk.msn.net [104.44.8.17]
12 * * * Request timed out.
13 * * * Request timed out.

I have my DNS set as those listed. I will run a tracert on my PC. Do I post my results here?

Here were the results:

traceroute: Warning: xboxlive.com has multiple addresses; using 134.170.29.82

traceroute to xboxlive.com (134.170.29.82), 64 hops max, 72 byte packets

 1  192.168.0.1 (192.168.0.1)  0.426 ms  0.214 ms  0.160 ms

 2  * * *

 3  24.248.104.54 (24.248.104.54)  8.372 ms  7.209 ms  8.120 ms

 4  172.24.149.162 (172.24.149.162)  8.342 ms  6.866 ms  8.008 ms

 5  70.169.88.16 (70.169.88.16)  8.392 ms  7.062 ms  8.351 ms

 6  dalsbprj01-ae1.0.rd.dl.cox.net (68.1.2.109)  38.403 ms  34.508 ms  40.124 ms

 7  ae16-0.dal-96cbe-1a.ntwk.msn.net (207.46.41.22)  18.211 ms  17.119 ms  18.726 ms

 8  104.44.8.128 (104.44.8.128)  54.517 ms  47.707 ms  48.354 ms

 9  be-5-0.ibr03.atb.network.microsoft.com (104.44.4.13)  52.617 ms  54.381 ms  54.953 ms

10  be-2-0.ibr02.atb.network.microsoft.com (104.44.4.40)  48.822 ms  47.412 ms  52.907 ms

11  be-3-0.ibr01.bn1.network.microsoft.com (104.44.4.49)  54.303 ms  53.139 ms  53.893 ms

12  ae63-0.bn1-96c-2a.ntwk.msn.net (104.44.8.5)  48.864 ms  51.992 ms  47.019 ms

Your results are a little higher then mine, but I don't think the data is showing us much. It could just be your physically farther away from where that server is. Also, it's unlikly your connecting to Xboxlive.com when your gaming, but rather a server somewhere off the domain. Kind of like trying to tracert to cox.net if your having a problem with email to pop.cox.net. Similar domain, but completely different thing. Can you try asking Xbox for a list of IPs for their game servers? Or maybe try finding out what some of the game servers are for the games your having problems with?

Sorry I'm not much help, just running out of ideas. I think it's possible XBL in your area is just congested. Do you have any friends in the area that play? Are they having similar problems?

I have found this to use on the Xbox forums: xeas.gtm.xboxlive.com

Here are the results: 

traceroute to xeas.gtm.xboxlive.com (65.55.42.54), 64 hops max, 72 byte packets

 1  192.168.0.1 (192.168.0.1)  0.445 ms  0.185 ms  0.171 ms

 2  * * *

 3  72.210.24.44 (72.210.24.44)  7.126 ms  6.807 ms  8.183 ms

 4  70.169.88.16 (70.169.88.16)  8.828 ms  9.135 ms  7.553 ms

 5  dalsbprj01-ae1.0.rd.dl.cox.net (68.1.2.109)  33.461 ms  32.035 ms  30.042 ms

 6  ae16-0.dal-96cbe-1a.ntwk.msn.net (207.46.41.22)  18.073 ms  17.771 ms  19.018 ms

 7  104.44.8.124 (104.44.8.124)  85.187 ms  86.748 ms  85.241 ms

 8  be-4-0.ibr02.dm2.network.microsoft.com (104.44.4.11)  86.745 ms  84.826 ms  86.188 ms

 9  be-2-0.ibr01.dm3.network.microsoft.com (104.44.4.84)  89.141 ms  87.018 ms  85.174 ms

10  be-4-0.ibr02.den07.network.microsoft.com (104.44.4.97)  86.668 ms  85.985 ms  86.325 ms

11  be-1-0.ibr01.den07.network.microsoft.com (104.44.4.58)  86.393 ms  85.914 ms  87.673 ms

12  be-3-0.ibr01.cys01.network.microsoft.com (104.44.4.112)  86.812 ms  88.606 ms  86.057 ms

13  be-1-0.ibr02.cys01.network.microsoft.com (104.44.4.98)  87.576 ms  85.150 ms  86.385 ms

14  be-3-0.ibr01.co2.network.microsoft.com (104.44.4.122)  85.344 ms  87.154 ms  84.245 ms

15  ae73-0.co2-96c-1a.ntwk.msn.net (104.44.8.245)  83.582 ms  85.428 ms  84.289 ms

Also I do have friends in the area who play, I believe a few that also have Cox as ISP have similar issues. A few friends have Eatel and don't have similar issues. (Eatel is a provider in the local area)

The biggest difference in latency I see (in your tracert) is between hop 6 and 7, which looks to be on Microsoft's network. Could you get one of your friends (one on Cox and one off if possible) to do the same tracert? It's possible hop 6 and 7 are just far away, so the latency jump is normal. Its getting to the server in less then 84ms, which is decent, so it doesn't look obvious. 

Or, now that you have data, call Microsoft and ask them if that is normal for their network? I assume XEAS is for Xbox East server. Are you on the east coast? Here is my tracert so the same server. 24 hops...Its bouncing around more then a hockey puck.  Looks like a Xbox problem to me.

Tracing route to xeas.gtm.xboxlive.com [65.55.42.54]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 7 ms 7 ms 9 ms 10.2.48.1
3 8 ms 7 ms 10 ms ip98-190-161-114.ri.ri.cox.net [98.190.161.114]
4 11 ms 10 ms 26 ms ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
5 19 ms 15 ms 26 ms nyrkbprj02-ae3.0.rd.ny.cox.net [68.1.5.161]
6 14 ms 18 ms 16 ms ip70-167-150-253.at.at.cox.net [70.167.150.253]
7 104 ms 107 ms 106 ms 104.44.8.112
8 107 ms 104 ms 107 ms be-3-0.ibr01.was02.network.microsoft.com [104.44
.4.34]
9 107 ms 105 ms 104 ms be-4-0.ibr03.ch1.network.microsoft.com [104.44.4
.33]
10 104 ms 104 ms 106 ms be-2-0.ibr02.ch1.network.microsoft.com [104.44.4
.56]
11 104 ms 102 ms 105 ms be-5-0.ibr01.dm2.network.microsoft.com [104.44.4
.76]
12 107 ms 114 ms 104 ms be-3-0.ibr01.dm3.network.microsoft.com [104.44.4
.74]
13 106 ms 113 ms 105 ms be-4-0.ibr02.den07.network.microsoft.com [104.44
.4.97]
14 107 ms 104 ms 105 ms be-1-0.ibr01.den07.network.microsoft.com [104.44
.4.58]
15 107 ms 102 ms 105 ms be-3-0.ibr01.cys01.network.microsoft.com [104.44
.4.112]
16 109 ms 115 ms 106 ms be-1-0.ibr02.cys01.network.microsoft.com [104.44
.4.98]
17 105 ms 104 ms 103 ms be-3-0.ibr01.co2.network.microsoft.com [104.44.4
.122]
18 103 ms 110 ms 104 ms ae74-0.co2-96c-1b.ntwk.msn.net [104.44.8.239]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 103 ms 103 ms 108 ms 25.255.8.190
23 103 ms 103 ms 107 ms 25.255.8.195
24 103 ms 103 ms 103 ms 65.55.42.54
Trace complete.

I notice the big jump from 6 to 7. I may have to contact Microsoft to see if that is normal. I am located in Louisiana so not exactly the east coast. Very well could be Xbox causing the issue, being that only weeks ago I would receive my normal 120/10 speeds on the console. I really appreciate the help!

No problem.  Not saying for sure it is a Xbox problem, because latency doesn't tell you everything. My tracert is worst then yours, with 100+ms jump, but I am not having any problems.I don't play Xbox that much though, and probably not the same games you do. Thats why tracert from your friends who aren't having a problem would be more revealing. If there latency is the same or worst, then it might not anything to do with latency. Throughput (speed) can effect lag and even once you get to the servers, if the servers themselves are backed up, that can effect it even more. Then you have dedicated servers Vs P2P. I can understand asking gamer friends for technical data can be pretty strange though. 

So much of it is out of your control, or even out of control of Cox and Xbox. You can only look at your data and improve it as much as possible and hope for the best. Keep us updated? Good luck.