# WebSocket connection stability concerns

**URL:** <https://forum.heroiclabs.com/t/websocket-connection-stability-concerns/3452>\
**Category:** Runtime Framework\
**Tags:** server-framework\
**Created:** [January 26, 2023, 2:21pm UTC](https://forum.heroiclabs.com/t/websocket-connection-stability-concerns/3452 "2023-01-26T14:21:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CoolGame](https://avatars.discourse-cdn.com/v4/letter/c/cc9497/32.png) [@CoolGame](https://forum.heroiclabs.com/u/CoolGame)\
**Post date:** [January 26, 2023, 2:21pm UTC](https://forum.heroiclabs.com/t/websocket-connection-stability-concerns/3452/1 "2023-01-26T14:21:00Z")

</div>

Hi, I have a few questions about WebSocket:

I can see that Nakama “cleans up” the matchmaking state, the session and status related to the user session if WebSocket connection gets interrupted.  
I can see that a client can reconnect to a match without a problem.

In your experience is it common for a WebSocker connection to get interrupted?

If a matchmaking takes lets say 10 minutes, it’s a very high chance of WebSocket disconnect, is it not? In that case if I would want to don’t drop a user from matchmaking when a socket disconnect happen, what would I do?

If I Nakama used not just WebSocket, but let’s say [Socket.io](http://Socket.io), wouldn’t it provide a more reliable connection in case of connection interruptions?

Thank you.