feat: add per-client rate limiting for presence events#1705
Merged
Conversation
Adds rate limiting at the individual WebSocket connection level to prevent a single client from exhausting the tenant's presence quota. Each client is limited to a configurable number of presence calls within a time window (defaults to 10 calls per 60 seconds). new CLIENT_PRESENCE_MAX_CALLS and CLIENT_PRESENCE_WINDOW_MS options This feature prevents individual misbehaving or malicious clients from consuming the entire tenant's presence rate limit quota, improving fairness and abuse prevention.
filipecabaco
approved these changes
Feb 8, 2026
edgurgel
force-pushed
the
feat/client-presence-max-calls
branch
from
06efdd2 to
f8d9e61
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Member
Author
|
Member
|
🎉 This PR is included in version 2.76.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Adds rate limiting at the individual WebSocket connection level to prevent a single client from exhausting the tenant's presence quota. Each client is limited to a configurable number of presence calls within a time window (defaults to 5 calls per 30 seconds).
new
CLIENT_PRESENCE_MAX_CALLSandCLIENT_PRESENCE_WINDOW_MSoptionsThis feature prevents individual misbehaving or malicious clients from consuming the entire tenant's presence rate limit quota, improving fairness and abuse prevention.
The ideal place to do this is at the socket level but we don't have (yet) control on the phoenix.socket.