My friends and I got this error message last night on Destiny 2. “Attention: Unable to find a match for your fireteam, please try again. If the problem persists, it may mean there is a problem with your networking setup. For more info please visit help.bungie.net and search for: newt.” The Fireteam Leader had loaded Artifact’s Edge, Arcadian Valley (Landing Zone) on Nessus and we could not load this area on two occasions. As a result, they set me as the fireteam leader and I tested if it was something on their end or at my house but we received the same error message a third time. Next, I left the fireteam and loaded the Tower because I wanted to see if there was an issue on our end or somewhere else but it loaded without any problems. Then, after visiting the Tower, we rejoined in orbit and were successful on launching Nessus afterward. In addition, I thought of an idea the next time all three or four of us play Destiny 2. The following was recommended to our fireteam and I noticed in our co-stream that we were using the in-game method for joining each other, which should technically work. However, I suggested maybe we should try the Xbox Live method and use the "invite party to game" instead. This is how we often connected on Destiny 1, and usually, we did not have glitches when joining this way. Player one and two are on the same local network with a fiber optic Internet connection and both consoles (Xbox One and Xbox One S) are using an Ethernet cable instead of wireless together with downloading the recent game and system updates. Player three (me) is also on a fiber optic network but instead of the 100 Mbps package, I have the 1,000 Mbps (1 Gigabit) service with the same provider, EPB Fiber Optics from Chattanooga. Additionally, I am hardwired as well and I regularly perform maintenance on my setup including resetting my AC1900 router and Xbox One, but our ISP did not have any outages last night and/or service upgrades to their network overall.