Matchmaking issue returned - Players unable to join public sessions (Server Connection Error #5)

[CCKLEX]

Summary

The matchmaking issue that was previously reported has returned since yesterday. (06-20-2026)

Players are once again unable to consistently join public sessions and are frequently placed into separate sessions or receive a “SERVER CONNECTION ERROR (#5)” while attempting to join the island.

Several players have already reported this to me and shared screenshots of the error. This issue significantly affects the ability for players to join and play together.

The problem appears to be very similar to the previously reported matchmaking issue that the team was already investigating.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Matchmaking

Steps to Reproduce

1. Open Fortnite.
2. Search for the island ( Map code 5049-6507-5084) and start public matchmaking.
3. Attempt to join the island.
4. Some players receive “SERVER CONNECTION ERROR (#5)” or are unable to join the existing public session.
5. Other players are placed into separate sessions instead of joining the active one.

Expected Result

Players should successfully connect to the existing public session and be able to play together without any connection or matchmaking issues.

Observed Result

Players are unable to reliably join the island. Some receive “SERVER CONNECTION ERROR (#5)”, while others are placed into separate empty sessions instead of the existing public session.

Platform(s)

all

Island Code

5049-6507-5084

Upload an image

Additional Notes

This issue appears to be a regression of the previously reported matchmaking problem that was already acknowledged by the team.

Previous report:

Matchmaking issue – players always placed into separate sessions instead of the same lobby

Summary In the last ~2 weeks, players who join my Fortnite Creative island are almost always placed in completely separate sessions instead of getting into the same lobby. The island supports up to 50 players with public matchmaking, but most players start the matches alone because new sessions are constantly being created instead of filling existing ones. This problem occurs in multiple regions. I have also received messages from players asking why they are always alone in the matches, which …

The matchmaking behavior showed signs of improvement for a short period, but since yesterday the problem has returned and is once again preventing players from joining public sessions reliably.

Multiple players have contacted me and shared the same experience, with some now also receiving “SERVER CONNECTION ERROR (#5)” while attempting to join the island. From my observations, the issue appears to occur predominantly on EU servers.

Because players cannot reliably join the same public session, many of them eventually stop trying after multiple failed attempts. This makes it increasingly difficult for the community to play together as intended and has a significant negative impact on the player experience.

I have attached a screenshot provided by one of my players showing the server connection error.

[CCKLEX]

@Flak
Could you please check that​, I had already lost so many players in March because of the matchmaking issues and then because of the DDoS attacks. Now it had recovered a bit and now the old problem with the matchmaking is coming back again.

[fnordsword]

I’m not sure if our issues are related but as of today at least one of my islands is getting split lobbies in public games where the player’s are in the lobby trying to join at the same time but are placed solo into separate games. Haven’t seen the error message yet in any case.

[fnordsword]

To follow up, public matchmaking is functioning as intended as of today on my island.

[CCKLEX]

It worked briefly yesterday (maybe for 2 hours), but now the problem remains unchanged. Can you check it? How is it today… My players still have the problem. Some get the message “Connection lost”, some get nothing and join a new lobby alone.

[fnordsword]

I just tested briefly and it appears to still be working on my end. However, I did change my team arrangement to dynamic from split evenly as I was trying to diagnose the issue on my own originally. That is still in place and I’m not sure if that has something to do with it.

[Bug-Reporter]

FORT-1120587 has been ‘Closed’. This issue won’t be fixed—please see examples of why this may be the case.