[u]My issue was with Xbox Live 360, but if you're issues are the same it's easily possible this could be your network issue as well for PS3/PS4/Xbox One[/u] [b]Do you have these Symptoms?[/b] [i]Disconnecting constantly under error code Caterpillar, occasionally Canary or the other "Networking Error" codes Being kicked from the Destiny server with no error code and disconnected from Xbox Live at the same time ALL of your other games/streaming services connect and run properly, but not Destiny[/i] If so, your problem could actually your Router, regardless of how you've set up for Open Nat/Port Forwarding etc. ------ So I'd been playing Destiny with a flawless connection for several months, and then moved in with my buddy about a month ago. We'd both be playing at the same time, no lag no connection issues. Cox Communications had given him an Ubee Router to use when they started his service, but he had continued using his old one until we moved all our stuff (and the router) into the garage. This caused his girlfriend to have an extremely low wireless signal on her Wii which was on the complete opposite end of the house. We ended up switching his old router to the Ubee router that Cox had given him to see if it fixed the problem. She was able to connect. Hurray! This is when we started having problems (Which we didn't realize was being caused by the router until weeks later). All our other games worked fine, no dropped connections for the most part. But when you launched Destiny; BAM. Caterpillar. Caterpillar. Kicked from XBL with no Error Code. Caterpillar. Canary. Caterpillar. Jesus, it was a nightmare. We called cox customer support to no avail, checked our connection/download/upload speeds/packet loss. NOTHING WAS WRONG. We kept trying everything, hard resets on the router and xbox, reinstalling the game, unplugging things thinking it was a bandwith issue, port forwarding, NOTHING made a difference. We were lucky to complete a single game out of five during Iron Banner, and pray it was a victorious match (Funny part is I hit rank 5 in Iron Banner before we fixed it. I must have waded waste deep through almost 50 or more disconnects to get there). And any time we tried to launch a match together, one of us would get a caterpillar code as soon as the matchmaking launched from orbit before the map even loaded. For weeks we thought (as most people still do) that the problem was on Bungie's side and that they were just telling us it was on our side. I became legitimately startled every time the Xbox notification sound went off (Message, Friend Online, Disconnect). So my buddy comes out into the garage the other day as I'm halfway through an Iron Banner match and says he found out what was wrong (Right before I got a Caterpillar code and was booted from the match). [b]The problem was the Ubee Router[/b] that Cox had given him and that we had switched to a little over a week and a half ago (right around the time our disconnect problems began). He had found a post somewhere online about someone who was in the exact same boat as us. Had a good connection, played for hours. He switched to the Ubee Router and "[i]Bam. Caterpillar code left and right[/i]". [b]It turns out that even though we had ourselves set up for Open NAT and Port Forwarding and all the junk in the Troubleshooting Guide on the website that several if not all of these Ubee Routers have built in predisposition to strict/moderate NAT. You can not change this.[/b] So even though we had jumped through all the hoops and set up Open NAT Destiny kept telling us we were under strict/moderate NAT and we hadn't been able to figure out why. [i]Cox gives these Ubee routers to customers all the time. If you have Cox, you might be using an Ubee Router unless you purchased your own.[/i] We switched it back to the Router we'd been using before and neither of us have had a single connection issue running Destiny for days now. Your best bet is to try out any other Routers that aren't Ubee you might have laying around, or get in contact with a friend who isn't having connection issues and find out what router they use and pick up one of those. I'll have my friend link me to the original post/page to the guy who first figured this out and I'll post it here later. [i]If you were still having these exact problems but don't have an Ubee router, check and read up to see if your router has a built in predisposition for Strict/Moderate NAT. I'm sure there are other routers designed that way as well and this is most likely your problem.[/i] Hope this helps some of you. Cheers, Gaurdian. Please post and let others know if it does.