The 1480 MTU might trip up some oddball anti-ddos tactics we've seen tossed out as short term tactics. 1472 is a common cut-off point we have seen in the past when it rears it's ugly head. I've found 1400,to be a more consistent value to use with my ISP. 1500 works and is the default, but with larger upstream threads it tends to cause a lot of spikes/pauses in the stream. Paring it down to 1400 seems to keep it more "flat-lined". Might be with a try. You will notice a slight drop in throughput from the extra overhead, but so long as you aren't below a 15/1 plan it shouldn't be a severe negative impact.

Thank u for ur info...... When u r saying the 1480 MTU R u referencing the MTU setting that the xb1 out put from netwrk test .... Or me changin the router MTU to 1480 From "Auto" Not tryin to grille u here... but would the xb1 output a 1480 MTU If it isnt optimal

I set mine in the console itself. The Windows systems tweak the send/receive parameters on the fly, so clamping down at the router can do weird things there. Running 1400 knocks about .5mb/s on my average download and about .1Mb/s on the average upstream for the console but the graphs remain more consistent. When I leave to auto it is much more jagged. (My router can track and graph throughput). The console speed test is also much more consistent...on auto it often returns <512k for the upstream test... Which is weird. Made the change years ago on the advice of a tier3 tech when the PS3 kept loosing connection to PSN. Spotted bad fragmentation. Dropped it to 1400 to test it and it fixed that issue. Used it in the PS4 as well...whenever I set it higher I start getting weird stability issues, dropping it back always smooths it out again.

Thank u again U are much more versed than i on this subject..... Im not sure i can set MTU directly on XB1 Afk atm What stirred this about was the great inconsistencies within destiny itself ( with player to player connection etc ) As well as the obvious owner network optimization Have everything ( to the best of my knowledge which isnt saying much / google etc ) Set up the best it can be ( short of buying top tier equipment ) But seem to notice a day to day difference in playing n general Ex: good days character actions seem very fast Running - jumping - maneuvering in general - reaction times - great precision hit markers Everything just " SEEMs " faster and more accurate Off days seem slower along with what some might call ghost bullets After new router incorporated into the system..... Seems like there are more ghost bullet scenarios Like 1v1 close range 5 pistol shots with tight grouping First n second register Third and forth do not Fourth is back to registering Im aware of the many variables here ISP - destiny itself - xbox live - home network Etc Just trying to figure it out abit I know it could be nothing on my end

Not familiar with the Xbox lines...have enough Microsoft products in my life as is. On the PlayStation's you get the MTU option when you do a custom network configuration... Basically you manually enter the network settings. If you are currently letting it automatically configure the settings you will need to do a few things first before switching it up: [B]Edit:[/b][i]There are sites like setuprouter.com that have free guides for a lot of routers that may help you get through this if you need guidance with this stuff. Can look in the alphabetical list there or google your make/model and probably find guides for it[/I] Bind your current address in the router's DHCP tables. You want to do this so the router doesn't give that address to something else later and cause a conflict. Some routers have streamlined it really well, others you may have to look for the DHCP settings under the LAN section. On mine, there is a button on the home page when I first log in that gives me a network map (list) of all connected devices. Each one has an icon beside it--clicking the icon locks/unlocks the address (on some routers it will actually be an animated lock). Some routers will do this on a pop-up panel if you double-click the device in that list. Others require you to do it more manually in the DHCP config page itself. Once you have confirmed that address is locked for your console, pull up the network status page on the console. Make note of all the settings: IP address, subnet mask, gateway, DNS server. Use those values to go through the console's custom/manual network setup pages. Note that if the DNS options were pointing to your router (will likely be the gateway address), you may have some stability issues occasionally with XBL/PSN. May want to look at the internet or WAN status page in the router to get your ISP's DNS or try using Google or OpenDNS addresses. Google's public DNS addresses are 8.8.8.8 and 8.8.4.4. OpenDNS can have different addresses for different regions...can google for "OpenDNS addresses" to look them up. Last but not least, double check that both the router and your console have UPnP support enabled (may or may not see the option when you manually set the console network settings--enable if you do, and don't use a Proxy Server unless you actually are). Oh yeah... Your router may also have a setting for a NAT or Hardware Acceleration feature listed in the LAN/Switch Control sections. If you see it you should turn it off as it can cause issues with UPnP and such. Plus it is really only a useful feature if you have near Gigabit or higher bandwidth. As always, after making changes to your network settings, always a good idea to run the console's network test to init the interface so it latches to the new changes/services.

From Happy Killmore to me: [quote]Thanks for this, and for making it to begin with. I realized that I was using Google's DNS, probably because my provider's DNS was down at one point. After switching off of Google's things have been much better.[/quote]

Glad it wound up being something "simple" So many stupid little things on the checklist to go through now....and it just keeps growing and growing. Just found out today that our city/county service buildings are still using the T-Band group to send their video feeds to the cable head end for rebroadcast on our local government channel (council meetings and such). Crazy little channels below channel 2 at 7-49MHz, and guess what else is also in that spectrum? Our upstream channels share part of that spectrum from 19.4-37.0 MHz. My modem loves bonding to one channel that is on 37MHz, which is also channel T-12. Just so happens that same channel is the one with all the noise that was periodically knocking people offline. Got a fix in place that stopped the modem reboots, but it is still noisy as sin so we still see a lot of errors periodically. So NOW I've got to lean on TWC to get someone to flush that out as a possible source for the noise that has been knackering us up down here. Such a pain in the proverbial arse sometimes......