OKX/Ouyi customer service is terrible. OKX’s system experienced an abnormality. The platform refuses to provide the calculation basis and data, repeatedly evades responsibility, and refuses to refund the overcharged fees. Ticket #33210456 remains unresolved.
Desired Outcome:
Refund all overcharged fees.
Provide the calculation basis and underlying data.
Provide a written explanation for the charges.
Escalate this complaint to a competent compliance/risk team.
Stop the evasive replies and resolve Ticket #33210456.
Evidence Available:
Trading records, platform rule documentation, customer-service chat transcripts, and Ticket #33210456.
Claimed loss: 14880USDT
Desired outcome: 14880USDT
Confidential Information Hidden: This section contains confidential information visible to verified OKX representatives only. If you are affiliated with OKX, please claim your business to access these details.
On March 30, 2026, an abnormal forced liquidation occurred on OKX/Ouyi. According to OKX’s documented rules, when the maintenance margin rate falls below 100%, high-tier bracket positions should first be reduced/deleveraged. However, in order to evade responsibility, OKX customer service has been force-reverse-engineering a cause from the result produced by the abnormal system. Their conclusion violates the trading rules in multiple respects.
I have repeatedly raised objections, but the OKX specialist has consistently avoided them. They keep copy-pasting evasive scripts and refusing to provide any explanation. My ticket number is [protected], and the issue remains unresolved.
Desired Outcome:
Provide the complete forced-liquidation calculation process and underlying data.
Explain how the liquidation complied with the documented high-tier bracket reduction rules.
Correct the erroneous forced liquidation and refund/compensate any improper fees or losses.
Escalate this complaint to a competent compliance/risk team.
Stop evading the issue and respond substantively to Ticket #[protected].
Evidence Available:
Trading records, platform rule documentation, customer-service chat transcripts, and ticket #[protected].