Why is Quantiply not giving the Static IP functionality like other Platforms?
Exchanges have explicitly clarified to all Algo Platforms and Brokers that platforms are not permitted to provide clients with static IP-based access. Under the new regulatory framework, algo platforms are required to operate strictly from within the Broker’s infrastructure, and not from their own independent systems.
Any platform continuing to offer services from its own infrastructure—whether through static IPs or similar workarounds—will be considered 'in violation' of the framework. Such non-compliance may attract strict regulatory action and could potentially result in service disruptions for end users.
What is the downside of using Static IPs for advanced trading?
The primary limitation of using a static IP or running your own algo setup is the regulatory rate limit of 10 OPS. As per Exchanges, this does not mean 10 orders per second, but rather 10 total API requests per second. These requests include all actions like order placement, modification, and cancellation combined.
In high-volatility scenarios, or when a portfolio-level target or stop-loss is triggered, this constraint becomes a significant bottleneck. Since only 10 requests can be processed per second, it is not possible to exit all open positions simultaneously. This leads to staggered exits, delayed order conversions (modifications from Limit to Market), resulting in increased slippage, and a higher likelihood of execution errors.
Additionally, the system may encounter repeated rate-limit breaches, causing retries and potential looping of requests, further compounding the issue. The same limitation also impacts entry orders, making timely execution difficult with increased slippages.
On the other hand, when the platform operates directly from the Broker’s infrastructure, it benefits from a significantly higher rate limit—typically exceeding 20 requests per second for each category of order management operation, such as order placement, modification, and cancellation. This higher individual rate limit overall enables smooth and simultaneous execution of entries and exits, effectively eliminating bottlenecks, delays, and slippage.