A system-status page gives users a centralized view of service availability. For a trading platform, relevant components can include website access, Spot trading, Futures trading, API services, deposits, withdrawals, and other account functions.
Trading Service Availability
When a status page is available, users should use it to check whether a specific trading service is operational before assuming that a failed request is caused by an account issue. A status page can also distinguish between a general outage and a problem affecting only one product or service.
API Status
Developers can use system-status information to determine whether an API problem is related to a broader platform incident. Before changing production code, developers should compare the observed error with current official status information and API documentation.
Deposits and Withdrawals
Blockchain transactions can involve network conditions in addition to platform processing. A status page can help users understand whether deposits or withdrawals are being processed normally, delayed, or temporarily restricted.
Maintenance and Incidents
Planned maintenance should ideally identify the affected service and expected maintenance window. Incident updates can provide information about detection, investigation, mitigation, and restoration. Users should rely on official status updates rather than unofficial reports.
What to Do During an Incident
Avoid repeatedly submitting the same order or withdrawal when a service is unstable unless official guidance says to do so. Record relevant transaction IDs, timestamps, and screenshots, then follow the official support process if an issue remains after service restoration.
Important Notice
This page explains the purpose and recommended structure of a 4M system-status resource. It does not publish an uptime percentage or claim that any particular service is currently operational. Live availability should always be verified through the official 4M status information.