TL;DR Getting constant weasels during solo campaign but never during pvp or strikes. Tested it multiple times. This is reproducable. Could play pvp for hours without any problems. How can this be? Read on for the specifics. This is going to be a long post, bear with me. Before you give me your standard copy and paste answer, bungie, that you tend to do on almost every single post do us all a favor and actually take your time to read this first because copying a standard answer over and over again is not fair to your customers who spent their hard earned money on your product. Especially to customers who don't insult you and/or have already tried a few steps to solve their connection problems. So I am expecting real answers to the questions and there will be some. Might have come to the wrong place but lets's see. I even marked the questions.. Weasel error only in solo activities. Never encountered any error in crucible pvp or strikes. I could play crucible all day long without a single error or lag. PVP works perfectly for me. Never had problems in tower or farm as well. Sad thing is I am not that much into pvp. This is strange to me considering what other players with better connections seem to be experiencing during crucible matches. I never did Trials of the 9 or the Raid though as I am quite the casual player. That is at least what I could observe during the past weeks. My personal experience. Maybe someone more educated in networking could explain to me if that sort of observation makes any sense or if it is just coincidence. Lookin' at you here, bungie. I'm on ps4 (not pro) and after changing from wifi to wired and setting up my ps4 as an exposed host in my network I eliminated every single error code except for WEASEL. I have no lag in the game whatsoever, just the weasel error outta nowhere which sends me to the title screen. Imagine a weasel giving someone an RKO but I am getting off-topic here. I would at least prefer a try to reconnect me instead of kicking me to the title screen. This is especially annoying in adventure side quests where for some reason your progression is not saved. Unlike the campaign where you can resume from the last check point in case of a dc. Why don't we have checkpoints in adventures after disconnects like the campaign does since the side quests can be quite long? (QUESTION) For me it only happens in the campaign or in quests where I am solo. Even after beating the game it kicked me with the weasel. I was afraid that it would cut the ending for me but I could start exactly from where I left: between the fight and the ending cutscene. That was funny and scary at the same time. I don't need that. I got a rather outdated 16k dsl connection with 12mbit downstream and 750kbit upstream for years. These are quite the normal values for this type of connection. Now here's the catch: Destiny is supposed to require 1mbit down and 1mbit up at times. Not more than that. Is this true? (QUESTION) I wonder if more upstream speed would help my problem or can the much faster downstream speed compensate for the slower upstream? (QUESTION) I know it is not fast by any of today's standards but needless to say it worked and works with any other game including destiny 1 flawlessly. I know they have peer to peer structure instead of dedicated servers which is a shame to be honest. I can play overwatch on pc with ~15ms ping all day long without any dc's or lagging for example. Absolutely stable. But these are dedicated servers, I guess. Which is funny, bungie and blizzard are both somehow affiliated with Activison yet blizzard always had much better customer support also in different languages. Think about that bungie ant take it serious: Better servers and better support. What I did so far to eliminate every code in the book except for weasel (maybe this is helpful to others): -switched to lan connection -set the ps4 as „exposed host“ in my router settings (before that I tried UpnP and port forwarding but the dmz function „exposed host“ works much better for me since I was receiving more different and frequent error codes with UpnP or port forwarding. Note: I did not try UpnP AND port forwarding at the same time because it is supposed to get in conflict with each other) -changed dns servers to google's 8.8.8.8 and 8.8.4.4 -tried various mtu settings on ps4 -determined my ideal mtu setting via ping command on my pc which is 1492 (1464+28) -prioritized the ps4 in my router settings -always disable wifi on my router altogether when playing destiny -even disabled the teredo filter in the router -disabled the possibility to be invited into clans via the website (don't have the compagnion app) -what I have not done yet is to check my modem's upstream power level. I don't know how. I'd probably need to convince my provider to do this for me. I have a dsl modem connected to a fritzbox (a common router in germany) 4020 which is a simple wlan router and not a modem itself unlike other models of that company. If I monitor my fritzbox afterwards it always says that my entire internet connection was cut for the duration of exactly 10 seconds after the weasel error occured. I'm pretty sure the weasel cuts my internet connection off and not the other way around because this message my fritzbox shows ONLY occurs after the weasel error has happened. This has been reported in destiny 1 before but I could never believe a game could do this. Also I am not disconnected from the playstation network. Still if I check my router later it always says there was a PPP Timeout (PPPoE-Error) the moment the weasel error occured...strange. Now here is the important part that at first glance makes no sense to me at all: I could play with my hunter who finished the story campaign the complete past week from October 9th to October 15th without a single error. Flawlessly. And I mean like 7 hours straight each day. I know I had much time at hand that week. If it would be my internet speed how could it run perfectly fine for an entire week? (QUESTION) Wouldn't make sense otherwise. I was confident and happy that the occasional weasel error was solved. As soon as I started my second char however, campaign of course, it is weasel all over again. It mostly starts after 2 hours playing solo campaign and from then on (if I login again and do not quit the game) much more frequently which is annoying. This might sound stupid and I am not educated in networking but since it is peer-to-peer: could the presence of other players help my connection like they are hosting the game and I am profiting in this moment from their stable connections?? Like a parasite?;) Which is why I encounter this weasel error during the campaign and not in other activities? (SERIOUS QUESTION!) What I don't understand though: when you are doing public events and stuff there is much more going on because of other players and enemies at the same time. In the campaign it's only a.i. Shouldn't it be easier to handle for the connection? (ANOTHER QUESTION) I wonder how my connection would perform if I'd do the campaign with someone together. On a personal note and I don't mean to be cynical here: I am looking forward to the pc launch via battlenet next week as I am sure many of the pc community that bungie has invited are going to experience all sorts of error codes which could cause a rather big shitstorm. This way bungie might be forced to invest a little bit more into their server architecture than copy and paste answers to make the game more stable for players with mediocre connections who can play any other always on game with ease. You don't f*** with pc players after all. Looking forward to your answers, bungie! And anyone else's of course! Maybe I will post this on reddit too if necessary reaching out for the community who often times provides better answers. PS: here's another link for reference: https://www.bungie.net/de/Forums/Post/109267121?sort=0&page=0