Losing games due to disconnecting, without even playing a snap

Hi there, @KxNgDeLaNo.

Thanks for reaching out to us. I'll try to help find out what's going on. First, are you on a wired or wireless connection? Also, what system are you playing on?

I have the same issue... frequently.  Here are some details:

1. Console: PS4
2. Wired Connection
3. Network: DMZ was not enabled (but I just enabled it for PS4)
4. This has been happening ever since Superstar KO was upgraded to the new version where you keep going until you lose (rather than become undefeated champions).
5. Ever since I received the update on Nobember 20, 2020, it's affecting online h2h as well.
6. Traceroute to easo.ea.com resulted in a LOT of route failure. See below:

I cancelled after hop 11:

$ traceroute easo.ea.com # from my Mac
traceroute to easo.ea.com (159.153.64.173), 64 hops max, 52 byte packets
1 10.0.0.1 (10.0.0.1) 3.965 ms 2.454 ms 2.220 ms
2 96.120.60.89 (96.120.60.89) 9.517 ms 9.598 ms 9.957 ms
3 ae-258-1342-rur202.troutdale.or.bverton.comcast.net (162.151.214.137) 13.014 ms 9.425 ms 9.268 ms
4 ae-56-ar01.troutdale.or.bverton.comcast.net (68.87.222.249) 10.360 ms 18.667 ms 14.704 ms
5 ae-2.bar2.portland1.level3.net (4.68.62.201) 13.335 ms 9.406 ms 9.553 ms
6 * * *
7 4.79.23.202 (4.79.23.202) 95.836 ms 94.630 ms 94.214 ms
8 159.153.92.10 (159.153.92.10) 91.977 ms 99.261 ms 90.654 ms
9 * * *
10 * * *
11 * * *

@kasl33 

Can you also run a Pathping? I assume you don't want a Windows PC you could use instead?

Have you tried using alternate DNS servers? If not, try the steps here. If you don't see a difference, try the Google DNS servers. Those are: Primary alt number 8.8.8.8 - Secondary alt number 8.8.4.4. Let me know if this makes a difference or not.

Here's what I would guess is about the equivalent of PathPing. I'm on a Mac, and everything else I work with is on Linux.

I first ran Nmap to see what ports are lisetning at easo.ea.com. I see ports 80 and 443. I tested against 443 since I imagine EA knows better than to run servers over port 80 other than redirection listeners. 

$ sudo tcptraceroute easo.ea.com 443
Selected device en0, address 10.0.0.83, port 56730 for outgoing packets
Tracing the path to easo.ea.com (159.153.64.173) on TCP port 443 (https), 30 hops max
 1  10.0.0.1  2.874 ms  2.324 ms  2.227 ms
 2  96.120.60.89  10.145 ms  10.755 ms  10.566 ms
 3  ae-258-1342-rur202.troutdale.or.bverton.comcast.net (162.151.214.137)  10.256 ms  9.328 ms  9.945 ms
 4  ae-56-ar01.troutdale.or.bverton.comcast.net (68.87.222.249)  9.556 ms  9.287 ms  15.822 ms
 5  ae-2.bar2.portland1.level3.net (4.68.62.201)  10.421 ms  11.833 ms  9.900 ms
 6  * * *
 7  4.79.23.202  93.821 ms  93.787 ms  95.466 ms
 8  159.153.92.10  91.018 ms  90.117 ms  91.946 ms
 9  159.153.92.78  89.147 ms  90.374 ms  89.985 ms
10  da2.gos.ea.com (159.153.64.173) [open]  93.121 ms  89.724 ms  89.858 ms

I have already tried DNS server changes as well. I use 1.1.1.1 and 1.0.0.1 usually, but also tried Google's 8.8.8.8 and 8.8.4.4. Same result.

This issue started when Superstar KO was changed to be ongoing rather than 5 games. It got even worse after the big 2 GB update last week.

I haven't played since I made this post -- I gave up since my stats are important to me, and the connectvity issues have ruined them. Any chance my stats can be fixed - remove all wins or losses where there was no score?

@kasl33 

It looks like hop 6 dropped. That could be causing this issue. Can you run the test one more time? I'd like to see if you still get similar results.

I still get the same result. This is also the same result I had last week.

@kasl33 

That would most likely be the issue then. It's happening before you reach our servers so it's not on our end. Opening the ports for Madden may help with this. You can find the ports here.

My PS4 is in the DMZ now. I don't believe it was last time I played online, so I'll update you and let you know how it goes next time I get a chance to play.

@kasl33 

Sounds good. Let me know what happens. Thanks!

Sorry for the delay in my response. I haven't been able to play much lately and have been pretty busy. In general, Superstar KO is playable again... until I get to the 4th game. If I make it that far, there's always some sort of issue that results in disconnection. Here is what I have seen so far this week since the last update for Superstar KO:

1. Win 3 games, you're done  and cannot proceed becuase the game kicks you back to the main Madden menu (not the Superstar KO menu)
2. If an opponent disconnects, you're done, and the game kicks you back to the main Madden menu (not the Superstar KO menu)
3. In between matches, on the "Match Found" screen, it hangs for a long time sometimes with nothing else on the screen - no images - just the words "Match Found" and a football icon at the bottom that does not move. Eventually, the game might start, but if the opponent leaves, then my progress ends, and I get kicked back to the main Madden menu (not the Superstar KO menu)
4. In above scenarios 2 and 3, I often find myself in a situation where the game says, "Your oppenent left the match" (or whatever it says like that), then it processes to see what happen, and even if I was winning 6-0, it says my game is over and I lost, then it kicks me to the main Madden menu (not the Superstar KO menu)

At this point, Superstar KO is only useful for practice at this point since it's more fun than actual practice mode. Please let me know when this network glitchiness gets fixed and I'll try again.