Building Transparently: Binance’s H2 2024 API Uptime Report
Main Takeaways
The second half of 2024 saw all-time highs in terms of user traffic to the Binance platform, putting extra load on our systems. However, core services such as Spot, Futures, and Margin remained stable during these traffic spikes.
Spot and Futures CM trading maintained a 100% API uptime, ensuring a smooth trading experience for users in the 24/7 crypto market. Overall, Binance maintained a 99.99% API uptime for the second half of 2024.
While several incidents had occurred, our monitoring system detected them automatically and immediately, which helped minimize the downtime.
At Binance, we understand that trust is built on transparency and performance. As part of our ongoing commitment to openness and continuous improvement, we’re sharing a detailed look at our API performance and system incidents for the second half of 2024. This report highlights how we’re working behind the scenes to ensure reliable, scalable, and stable services for our global user base – because innovation requires both consistency and openness.
H2 API Monitoring
Many of Binance's almost 270 million users depend on our application programming interfaces (APIs) for key data such as price, depth, trading activity, and various other metrics vital for their market analysis and trading strategies. It is thus crucial that these data feeds remain consistently accessible to support the demands of the 24/7 cryptocurrency market.
The following chart shows how our systems performed in the second half of 2024, showcasing how we’re continuing to strengthen our infrastructure to meet the demands of the ever-evolving crypto landscape.
The list of APIs presented in the table is available here. These APIs are mainly used for following real-time changes in the market, allowing traders and investors to track the latest prices and see historical trends for various assets and financial instruments.
The second half of 2024 saw Spot and Futures CM maintain a 100% API uptime. Across all services, there were two incidents, which impacted some of our API endpoints during periods of unprecedented trading activity.
One incident happened in July, impacting some of the Cross Margin functions for 38 minutes. Another incident took place in October, affecting Futures UM functions like placing orders and getting market data, for 35 minutes.
More details on each of our trading APIs are available at the following links:
Uptime Calculation
We calculate the yearly uptime by dividing the number of hours our domains are up and running per year by 8,784 (the overall number of hours in a year) and multiply the resulting value by 100 to get the percentage.
In the third quarter of 2024 we had: 44,640 uptime minutes in July; 44,640 minutes in August; and 43,200 minutes in September, amounting to the overall 132,480 minutes in Q3. Accounting for the incident in July, which resulted in 38 minutes of partial downtime on some of our Margin API services (leaving us with 132,442 minutes of uptime), our uptime percentage calculation looks like this for Margin:
132,442 mins / 132,480 mins * 100 = 99.97%
In the fourth quarter of 2024 we had: 44,640 uptime minutes in October; 43,200 minutes in November; and 44,640 minutes in December, amounting to the overall 132,480 minutes in Q4. Accounting for the incident in October, which resulted in 35 minutes of partial downtime on some of our Futures UM API services (leaving us with 132,442 minutes of uptime), our uptime percentage calculation looks like this for Futures UM:
132,445 mins / 132,480 mins * 100 = 99.97%
If you have any suggestions as to how we can improve our APIs, please raise them using our Product Feedback & Suggestions platform.