On February 10, a service disruption affected trading and data display features on our platform. This report details the incident timeline, root cause, and the ongoing work to enhance system stability and minimize future occurrences.
Incident Timeline and System Downtime Description
Between 5:37 am and 7:36 am UTC on February 10, our monitoring systems detected abnormal behavior affecting website access and trading features.
Our engineering team identified that these issues stemmed from a traffic overload, which subsequently led to an authentication service outage and internal service timeouts. The following timeline outlines the key events during this incident:
- 5:37 am UTC: Initial detection of system abnormalities. Users experienced issues with market information and trading depth data not displaying on web and app interfaces. API interfaces intermittently returned a "server error" with an "Invalid Authority" prompt.
- 5:40 am UTC: Engineers identified the root cause as traffic overload and immediately initiated urgent repairs to address the authentication service failure.
- 7:36 am UTC: Full trading functionality was restored across web, app, and API interfaces. Market information display on the app was also fully recovered.
Our Commitment to Platform Stability and Improvements
We are dedicated to providing a secure and reliable trading environment. While we strive for 100% uptime, the complex nature of high-performance trading systems means unexpected issues can rarely occur. Our primary goal is to continuously improve system resilience and minimize any potential disruption to user activity.
To this end, we are consistently working on several key initiatives:
- Enhanced Engineering and Testing: We strengthen our quality assurance processes and optimize our test systems. New code for features must run stably in a demo trading environment for a significant period before being launched to the public.
- Architectural Upgrades: We are realizing high availability through multiple servers across various regions. This architectural strategy significantly reduces potential downtime caused by isolated hardware or software problems.
- Stateless Hot Upgrades: Implementing hot upgrades in a stateless manner minimizes the impact of necessary system updates on user transactions, allowing for smoother maintenance periods.
We understand that system stability is paramount for your trading success. For a deeper look at the advanced technologies powering our platform, you can explore our system architecture insights.
How to Receive Official Updates and Notifications
Transparent communication during any service issue is a top priority. We provide updates through official channels to keep our users informed.
- Status Page: Immediate failure notifications are published on our official Status page as soon as an incident is detected.
- Scheduled Upgrade Notifications: For any planned system maintenance or upgrades, we announce details in advance on our Status page. These notifications are also disseminated through our market and community channels.
- API User Updates: API users can subscribe to the dedicated System/Status channel to receive timely notifications about system updates and status changes.
Frequently Asked Questions
What exactly happened on February 10?
The platform experienced a partial outage caused by an unexpected surge in traffic that overloaded the authentication service. This affected the display of market data and interrupted trading for a limited time.
How long did the service disruption last?
The incident began at 5:37 am UTC and was fully resolved by 7:36 am UTC, resulting in a total duration of approximately two hours.
Was user fund security compromised during this incident?
No. The issue was related to service accessibility and data display. All user funds remained secure throughout the entire event and were never at risk.
How can I check if the platform is experiencing issues in the future?
The most reliable source for real-time system status is our official Status page. It provides immediate updates on any ongoing incidents or planned maintenance.
What is being done to prevent this from happening again?
We are continuously investing in infrastructure upgrades, including architectural improvements for higher availability and more robust testing protocols to handle unexpected traffic spikes. You can view our real-time status and updates for ongoing improvements.
How are API users notified of system issues?
API users are advised to subscribe to the System/Status channel through the API system to receive automated alerts about system status and any scheduled upgrades.