Changes to live connection limits
Starting February 16, 2025, we're changing our live connection ( session ) limits.
- Usage-based and Standard users will be limited to 10 simultaneous live sessions per dataset.
- Plus, Unlimited and Enterprise users will be limited to 50 simultaneous live sessions per dataset.
Previously, any user could open up to 100 simultaneous sessions on the live API.
The live API allows users to subscribe to multiple schemas and symbols within a single session, even after it has started. This approach is recommended as a best practice so that users have fewer connections to manage and can reuse existing sessions. As a result, most users shouldn't require a large number of connections if their application is implemented accordingly.
However, some users are unaware of this feature and create an unnecessary number of connections, which can strain the live gateway and impact their feed performance. This change is intended to address the issue by discouraging this antipattern.
If you need to distribute data to more than 10 or 50 applications per user (depending on your pricing plan), we recommend implementing a middleware layer within your system to redistribute the data internally. This approach is typically more bandwidth-efficient and can also improve latency by optimizing TCP congestion control.
If you feel that you have important circumstances that require a higher connection limit, please contact our support team.
No. The session limit is applied per user, so adding more API keys will not allow you to exceed it.
Since the limit isn't applied per team, teams can invite additional users to establish more connections. However, this is inconvenient and likely an antipattern. We suggest creating a middleware layer to redistribute data internally within your system instead.
Learn more in our live documentation .