A Propr trader has alleged that lag on the crypto-native prop firm’s custom trading terminal caused orders to disappear from view, fees to appear later for trades the user believed had not executed and, in one case, a sell position to appear after the trader says they submitted a buy.
The claims were published in an unprompted Trustpilot review on October 4 and have not been independently verified. The reviewer did not provide public order IDs, timestamps, screenshots or Hyperliquid transaction records that would establish exactly what happened.
However, the complaint is more notable because it is not the first report of technical execution problems on Propr’s relatively new platform.
Earlier customers have complained about latency and problems managing stop-loss and take-profit orders, and Propr itself has previously acknowledged both platform latency and bugs associated with updates.
The key question now is whether the October 4 allegations represent another frontend problem on Propr’s beta terminal or whether incorrect instructions actually reached the execution infrastructure underlying the platform.
Trader Says Orders Disappeared Before Charges Appeared Later
The October 4 reviewer described Propr’s website as lagging during critical trading moments and claimed that some orders did not appear to execute after submission.
According to the trader, refreshing the page still did not show the trades, leading them to believe the orders had not been placed. The reviewer said charges associated with those trades later appeared in the account history.
The customer also alleged that on one occasion they intended to open a buy position but subsequently saw a sell order instead.
That is potentially the most serious allegation because a wrong-side trade is fundamentally different from ordinary latency. A delayed confirmation can create uncertainty about whether an instruction reached the market. A sell order created from a buy instruction would indicate either a user-interface problem, state-synchronization issue or deeper order-routing error.
There is currently no public evidence establishing that such a reversal occurred.
The trader also complained about approximately $9 in round-trip trading costs. That figure should not be interpreted as evidence of a fixed $9 Propr commission. Hyperliquid’s base perpetual taker fee is percentage-based, meaning costs depend on notional trade size.
Propr Has Already Acknowledged Platform Latency
The new complaint follows older reports that give the issue more context.
In late June, another Trustpilot reviewer complained of false account breaches and platform downtime during important trading hours.
Propr CEO Louis Régis responded that the company had experienced latency issues for several days after user growth exceeded expectations and placed pressure on its infrastructure.
The company said engineering improvements were being implemented and offered a full refund where an account breach could be shown to have resulted from platform latency.
That response was significant because Propr did not simply dispute the complaint. It publicly acknowledged that latency existed.
Platform latency becomes financially meaningful when live trading instructions are involved, as recent order-processing problems at CMC Markets demonstrated. The crucial distinction is whether the customer sees information late or whether the instruction itself is delayed, rejected or executed differently from what was intended.
Propr Said in September That Its Terminal Was Still in Beta
An August 31 complaint raised a separate order-management issue.
That reviewer said stop-loss and take-profit levels sometimes required several attempts to position correctly and alleged that one stop was later found at an unexpected level, resulting in the position being closed.
Propr responded on September 1 that the platform was still in beta and acknowledged that bugs can sometimes occur when updates are pushed.
The company also said it refunds or resets accounts when platform bugs cause problems and offered to do so for the reviewer.
That response matters more now because the October 4 complaint again involves the relationship between what a trader believes was submitted through the interface and what later appears in the account.
The incidents are not proven to share a technical cause. But they create a reasonable question about whether the execution and state-display issues Propr acknowledged during the summer have been fully resolved.
Propr’s Hyperliquid Connection Should Make the Dispute Easier to Investigate
Propr differs from many traditional forex-style prop firms because it operates its own web terminal rather than relying primarily on MetaTrader or another established retail platform.
On its official platform page, Propr says its custom terminal draws deep order-book liquidity from Hyperliquid and that execution occurs on-chain.
The company promotes transparency as a central part of its model, saying trades, positions and payouts can be independently examined.
That architecture should make the latest allegations unusually testable.
If the trader supplies exact order IDs and timestamps, Propr should be able to determine whether an instruction left the frontend, what side and size were encoded, when the system received it and whether an associated order ultimately reached the relevant execution layer.
This is the same evidence problem that arose when a Revolut trader alleged a failed WTI exit turned into a $5,300 loss. Screenshots can establish what a customer saw, but server-side order records are what show whether an instruction actually reached the trading system.
A Missing Trade Can Mean Several Very Different Things
The phrase “trade did not execute” can describe several technically different failures.
A browser may fail to display an order even though the backend accepted it. A request may reach Propr but fail before being forwarded. Hyperliquid may receive an order and reject it. The order may execute while the frontend fails to refresh the resulting position. Or a trader may unintentionally submit the instruction more than once while repeatedly clicking during lag.
Those scenarios can look almost identical from the customer’s screen while producing very different account histories.
That is why complaints about lag should not automatically be interpreted as proof of incorrect execution.
Dave Finances found a similar distinction in recent Capital.com complaints involving platform interruptions. Customer reports can establish that something appeared wrong at the interface, but transaction logs are needed before assigning the resulting P&L to a specific infrastructure failure.
The Wrong-Side Order Claim Is the One Propr Most Needs to Resolve
Ordinary latency is frustrating but understandable in a fast-growing beta platform.
A buy becoming a sell is different.
If the trader simply clicked the wrong side or submitted another instruction while the page was lagging, the order records should show that clearly.
If Propr’s server received a buy instruction but subsequently created a sell, that would point toward a much more serious execution bug.
A third possibility is that the actual execution was correct but the interface displayed the position incorrectly. That would still be a significant problem because traders make subsequent risk decisions based on the positions shown on screen.
In each case, the necessary evidence should include the original client instruction, server timestamp, side, quantity, instrument, backend response and any corresponding Hyperliquid execution or hedge record.
The same evidentiary standard matters in other execution disputes. A recent Tickmill copy-trading complaint also turned on whether apparently related accounts received materially different executions rather than simply whether one trader reported an unfavorable outcome.
Beta Status Is an Explanation, Not a Complete Answer
There is a reasonable argument in Propr’s favor: it is building a new trading platform rather than placing a branded evaluation layer on top of mature third-party software.
That creates room for faster product development and closer integration with crypto-native infrastructure.
It also creates more software risk.
A beta label tells users that defects may still exist. But once a company sells paid evaluation accounts whose balances can be breached because of trading outcomes, bugs stop being ordinary software inconveniences.
If a streaming app freezes, someone misses a video. If a prop terminal freezes while a trader is managing leveraged exposure, the same software defect can determine whether an account survives its drawdown limits.
Propr appears to recognize that distinction by offering refunds and account resets where its own bugs are responsible.
The difficult part is determining responsibility quickly and consistently.
Custom Platforms Create Both an Advantage and a Liability
Propr’s custom terminal is one of its main selling points.
The company can control the interface, integrate Hyperliquid markets directly and build functionality specifically for crypto-native prop traders rather than depending on legacy broker technology.
But ownership of the platform also means ownership of its failures.
When a MetaTrader broker experiences a client-terminal bug, responsibility can potentially be divided between broker infrastructure, MetaQuotes software, connectivity providers and the user’s device.
Propr has fewer layers to point toward because it promotes the terminal as part of its own product.
That can eventually become an advantage. Controlling the full stack should make debugging easier and allow the firm to reconcile frontend events against backend and on-chain records.
Until reliability matures, however, the same vertical integration concentrates reputational risk.
The Next Evidence Should Come From Order Logs, Not Another Review
The October 4 complaint is not enough to establish that Propr systematically executes orders incorrectly.
The platform has many positive customer reviews, including reports of rapid payouts and smooth trading, while the most serious new claims come from one trader whose underlying order records are not public.
But the historical context means the complaint should not simply be dismissed as an isolated angry review.
Propr has acknowledged previous latency. It has acknowledged that beta updates can introduce bugs. Customers have previously complained about stop-management and execution behavior.
The decisive evidence is therefore relatively straightforward.
The October 4 trader should provide exact order timestamps, instruments, sizes and any available order identifiers. Propr can then show whether those instructions were received, what direction they specified, whether they reached Hyperliquid-linked infrastructure and why any resulting trade appeared later than expected.
If the logs show that the orders were correctly received and executed, the case may largely be a frontend-display dispute.
If they show rejected instructions that the interface later represented incorrectly, Propr has a synchronization problem to fix.
If they show a buy becoming a sell inside the firm’s own order pipeline, the story becomes considerably more serious.
Until those records emerge, the responsible conclusion is narrower: Propr is facing a fresh customer allegation involving lag and unexpected order behavior on a platform where the company has already acknowledged beta-stage technical problems.
For a prop firm selling access to a custom terminal, proving that the screen and the execution engine always agree is not merely a user-experience issue. It is part of the product traders are paying to trust.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.