Updating

Platform

System status

Component availability for this environment. Trading, funding and support are services; market data reflects the public feed your browser is connected to.

Some systems offline

Updated continuously from the client market-data connection.

  • Trading

    matching engine, order ticket and order history.

    matching engine running in your browser. Live order routing is not enabled.

    Operational
  • Deposits

    inbound transfers and deposit addresses.

    deposits settle after a delay. No blockchain transactions occur.

    Operational
  • Withdrawals

    outbound transfers, eligibility checks and review queue.

    Withdrawals are only. Real payouts stay disabled until custody and compliance are live.

    Degraded
  • Market data

    Public prices, candles, order book and trade feed.

    Establishing the market-data connection.

    Degraded
  • Authentication

    Sign-in, 2FA challenge and session management.

    local authentication. No credentials leave the browser.

    Operational
  • Public API

    REST and WebSocket endpoints for developers.

    Documented contract only. No public API keys are issued and no endpoints are served.

    Offline
  • Support

    Help centre, automated assistant and tickets.

    Tickets and replies are and stored locally.

    Operational

Notices

  • OfflineOngoing

    Public API not yet served

    The developer documentation describes the intended contract. Endpoints, keys and rate limits go live only after the backend, authentication and rate-limiting layers are independently implemented.

  • DegradedOngoing

    Withdrawals limited to processing

    Withdrawal requests move through the full review lifecycle but never leave the ledger. Real payouts require custody, sanctions screening and treasury operations.