diff --git a/Enabling-WebSocket-notifications.md b/Enabling-WebSocket-notifications.md
index 02c4fda..a72139c 100644
--- a/Enabling-WebSocket-notifications.md
+++ b/Enabling-WebSocket-notifications.md
@@ -15,6 +15,7 @@ If you do use a reverse proxy like nginx or Apache HTTPd, then you need to make
 
 The old `WEBSOCKET_ENABLED` and `WEBSOCKET_PORT` have been deprecated since v1.29.0 of Vaultwarden and will be ignored.<br>
 After v1.29.0, you can disable Websocket notifications by setting `ENABLE_WEBSOCKET` to the `false` value, which will reduce resources used by Vaultwarden (though not that much).
+Since v1.31.0, support for WebSocket traffic on port 3012 has been removed, as it's been integrated on the main HTTP port.
 
 <br>