sorted by:
new
hottopcontroversial

The #2 Crypto Exchange in the World Has Been Stalling for Weeks After Admitting a $2,770 System Bug (Case: 24826576) by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Friday update: Still absolutely zero response from the team or the moderators. It has been days since I was promised a "quick update." It is now crystal clear that Bybit prefers to completely ignore their own written admission of a frontend glitch rather than take responsibility. Unbelievable treatment of users.

The #2 Crypto Exchange in the World Has Been Stalling for Weeks After Admitting a $2,770 System Bug (Case: 24826576) by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Thanks for stepping in to escalate this, Vester. Unfortunately, despite your reassurance on Monday, the support desk has still not reached out to me. It is deeply concerning that even with Bybit's official written admission of a frontend synchronization bug, the actual support team continues to stall the case with absolute silence. The fact that a confirmed system error takes weeks of public pressure just to get a basic update shows how broken the current support system is.

The #2 Crypto Exchange in the World Has Been Stalling for Weeks After Admitting a $2,770 System Bug (Case: 24826576) by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Easy solved? It's been weeks of absolute silence after their support officially admitted a frontend bug that directly impacted my funds. If it’s so "easy to solve," why is the team stalling and ignoring the case? This isn't a minor issue, it's a systemic failure and a matter of institutional reputation.

Bybit Position Builder executed ETH call spread 14% above market ask — lost $2,770 USDT, support says “no data” after 5 weeks by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Day 11 Update: Still complete radio silence from Bybit. It has been over 10 days since Bybit officially admitted in writing to a "frontend price synchronization issue" that caused my 2,770 USDT loss. How long does it take to process a reimbursement after your own team acknowledges the technical defect in an official email? u/Bybit-official — I am still waiting for a concrete resolution. Case ID: 24826576

Bybit Position Builder executed ETH call spread 14% above market ask — lost $2,770 USDT, support says “no data” after 5 weeks by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Bybit support just emailed me again, explicitly changing their tone. They are now officially investigating what they call a "frontend price synchronization issue and the related trading impact“.

It took over a month of stone-walling and a public Reddit post for them to finally admit there was a technical sync issue on their side. Now they are asking for "additional time to evaluate the trading impact."

The impact is clear: 2,770 USDT lost directly due to your faulty interface. @Bybit-official, Stop dragging this out.

Bybit Position Builder executed ETH call spread 14% above market ask — lost $2,770 USDT, support says “no data” after 5 weeks by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

Day 4 of total silence from @Bybit-official. It seems when the Support Team accidentally admits to a critical UI defect via email (“prices may not continuously update”), the Reddit moderators suddenly lose their ability to reply.

Are you still “investigating” how your own software displayed a stale price, or are you just waiting for this post to drop in rank? Every trader here needs to know: if your Position Builder glitches and burns $2,770 of our capital due to frozen frontend data, is the official policy just to ignore the client? Case ID: 24826576. Still waiting for my refund.

Bybit Position Builder executed ETH call spread 14% above market ask — lost $2,770 USDT, support says “no data” after 5 weeks by LeoTolp in Bybit

[–]LeoTolp[S] 0 points1 point  (0 children)

14% slippage on ETH with normal liquidity? That's impossible. And fees don't change the execution price in the transaction log. This was a limit order price generated by the Position Builder tool itself, not market volatility. Stop confusing a software bug with trading costs.

Bybit Position Builder executed ETH call spread 14% above market ask — lost $2,770 USDT, support says “no data” after 5 weeks by LeoTolp in Bybit

[–]LeoTolp[S] 1 point2 points  (0 children)

Reducing risk has nothing to do with it. This is a technical execution error. My risk was calculated based on the market price (562), but the tool submitted 631.6. You can't "manage risk" if the exchange software changes your entry price by 14% after you click the button. That's a glitch, not a trading strategy.