An update from me to help those with a similar issue as mine. So last night Nov 2, I spoke with EA support again and this time they told me a factory reset was not necessary since have completed other troubleshooting steps for two days. I was told to download and perform a UO tracer report and send it to tech support. I did this and it showed no connection issue or packet loss. EA support then called me back and told me they were having more server issues. I needed to login to my xbox using another gamertag and see if it would connect to BF1 multiplayer. I told them I didn't have one and they said if I didn't perform this step they would not help me anymore. (I know triple negative) So I called Xbox (btw they have been outstanding to work with) and spent two hours on the phone with a tech support, created a new gametag, hard reset my xbox, and did all their troubleshooting steps. The new created gamertag connected to BF1 multiplayer with no issue, but sadly when I used my gamertag it gave me the multiplayer matchmaking failed error again. Of course my gamertag will work with BF4 and world of tanks. So I called EA support again told them that a new gamertag will work on the same xbox and they told me it was an xbox issue with my gamertag! I told them again everything was fine until the server outage on Oct. 29 and other games work. So the EA tech then tells me to perform a UO tracer again and then they can proceed troubleshooting. Are you kidding me?! How many times must I go through this?
Update Nov 4 - talked to EA support last night. Sent another UO trace report to them. Reiterated to them that I was able to connect to BF1 multiplayer through my xbox using another gamertag. EA tech support then acknowledged that the problem was an issue on their end with my account (even though BF4 works). They then told me to wait and I would receive an email when the issue was resolved by their tech. This was after 9 pm central time last night. It is now 10:39 am and I still have not received an email. I also checked my connection at 5:05 am this morning before work and I still have the same issue. 6 days and counting with this issue................
