Vikram S.
Unfair Slippage Handling Led to Account Risk Level Breach
I had a very disappointing experience with FundedHive due to their slippage issues and how they handled it when slippages breach the risk levels. During my trades, I experienced extreme slippage—around 20–25% beyond my calculated stop loss only when i was near to the daily risk level limit. This directly caused my account to breach the risk limit. My allowed daily breach level was 3%, but my account closed at 3.0098%, which is just about $40 extra on a $100K account. The frustrating part is that I had already placed my trades with a buffer to account for slippage, yet the execution went far beyond normal expectations and gave me extra $151 & $199. When I contacted support, they acknowledged the slippage and refunded the portion of slippage exceeding 10% of the total loss (around $51). However, despite clearly recognizing the issue, they refused to reverse the breach status on my account—even though the breach happened solely because of their execution conditions. Additionally, in both accounts I was trading, slippage ranged between $151 and $199, which is more than 15% of the intended stop loss. This is not acceptable for a trading environment where risk management is critical. Overall, I’m very disappointed. While they partially compensated the slippage, they did not take full responsibility for the impact it had on my account, which ultimately cost me the account itself.
Response from Under Competitor AttackApr 14, 2026
Thank you for the detailed feedback. First, we want to make one thing clear: if support refunded part of the slippage, that already proves this was not a case of denial, avoidance, or pretending nothing happened. It means the case was reviewed under the slippage policy and handled according to the protection framework that exists on challenge accounts. The key issue here is where the misunderstanding begins. Real slippage and breach logic are not the same thing. In a real market environment, especially in volatile conditions, execution can move beyond the intended stop because orders are filled where actual liquidity is available. That is exactly why slippage protection exists in the first place. But slippage protection does not mean that every trade outcome or every account-state consequence can simply be erased afterward as if the market event never happened. In your own example, support acknowledged the slippage amount that qualified under the policy and refunded that portion. That is a protection mechanism. But the account breach logic is still rule-based and automated. It cannot be manually rewritten every time a trader is unhappy with the resulting account state, otherwise the entire system would stop being consistent and fair for everyone. It is also important to understand that the market does not care whether a breach happened by a wide margin or by a narrow margin. If the account crosses the defined threshold, the system registers it. That is exactly what automated rule enforcement means. You also mention that your slippage buffer was already built into the trade. That is fair, but in extreme volatility even a pre-planned buffer may still not fully absorb real execution movement. That is not ideal, but it is part of real market behavior, especially in instruments and moments where multiple liquidity levels are consumed quickly. What FundedHive does differently is that we do not hide this behind fake fills or manipulated charts. We openly acknowledge slippage, we built a slippage protection framework, and we reviewed your case under that policy. That is already far more transparent than how most firms in this industry operate. So the honest conclusion is this: your frustration is understandable, but this is not proof of unfair handling. It is proof that real execution and automated risk enforcement can create outcomes that traders do not like, especially near risk thresholds. FundedHive was built around real execution, real transparency, and rule consistency. That means when protection applies, it is applied. And when the system threshold is breached, it is enforced. That consistency is exactly why the model remains sustainable and credible long term.




