Something may be interfering with timely, orderly delivery of data packets. Could be a more localized issue, or something your ISP's Tier3 support would need to investigate. Bungie has a network troubleshooting guide that covers the core generic network stuff. But there are some extra caveats to consider as well. Basic rundown: bind your console's IP in your router's DHCP and configure your console with a static IP. When doing this, point it to an actual DNS server and not the router. Can try your ISP's, Google (8.8.8.8 and 8.8.4.4), or look up the closest OpenDNS addresses. Playstations need highly responsive DNS...they do weird things if it is inconsistent. Can also try manually setting MTU to 1400...Auto may set it too high and cause some weird fragmentation issues. Make sure UPnP is enabled on both the console AND the router. Some routers may not manage UPnP gracefully with a console. Updating the router's firmware may resolve it. If not, you may have no choice but run a manual forwarding scheme. ***Do NOT run both a manual forward setup AND UPnP at the same time...may cause conflicts (the same reason you bind the IP in DHCP before setting a static address).*** If you have a service needing a manual port forward rule (doesn't have a UPnP option), or you suspect UPnP is not working right, then disable UPnP on both devices and set manual rules according to the Bungie guide. Run the console's network test after changing any of it's network settings. Sometimes good to do it periodically too if things are behaving strangely...can sometimes prod the network layers back in order when it has a brain fart. One such situation is if UPnP isn't opening ports properly. PS3's had this happen a lot at one time, and one workaround was running the test, as it inited the interraces again without a full reboot. Some extra router specific things: Disable the Hardware or NAT acceleration feature. This feature can destabilize port forwarding when enabled. Disable IPv6 support in the router. Game uses IPv4 only, and with some ISP's having this enabled can have a weird effect on console DNS queries. Some basic maintenance type issues to consider: If you usually do rest/standby mode, need to periodically do a full power down of the system for a while. Can speed up the process by doing a power down, unplugging power, and press/hold power for a few seconds, then plug it up and boot again. Along the same lines, it is also a good idea to periodically power cycle the modem and router as well. Can do the whole set at the same time. Power it all down, let the modem boot up fully, then the router, then the console. If the router boots too soon after modem start up to synch properly, it may take a router reboot for it to grab the config properly from the modem again. The reason for it is two fold. Stale cached data can cause issues, and rebooting the network hardware also gives a chance to pull new config data from the ISP. Might get a better channel bonding, possibly homed to a new DNS server or even a new bandwidth profile could boost throughput a bit--never know when you might get a free bump to the effective bandwidth caps. Make sure all network related cables have clean and snug connections. Good to periodically disconnect/reconnect them...it can knock off some oxidation that may be increasing resistance and degrading signal quality. Coaxial cables should be just a hair more than finger tight...no more than 1/8 turn if using a tool. Also gives you a chance to make sure network/coax cables have good insulation/and shielding, they aren't bunched/kinked or coiled up. Want them to run in a continuously forward path as best you can, and also try to avoid having them run too close to other power/signal cables, motorised, or other electronic devices that may emit any kind of RF interference (wireless devices, audio/video equipment, fluorescent lighting, PC case, etc.). Stray noise induction can cause all manner of weirdness from out of nowhere.