Building Transparently: Binance’s H1 2024 API Uptime Report
Main Takeaways
Binance’s H1 2024 API uptime report, showcases our dedication to stable, scalable, and available trading for over 200 million users globally.
Binance maintained an impressive 99.99% API uptime in the first half of 2024, ensuring continuous support for the 24/7 crypto market.
Our proactive monitoring and transparent reporting of API performance reflect Binance's core values of user-driven innovation, transparency, and continuous improvement.
At Binance, we believe in the power of transparency and user-driven innovation, which means being open about the performance of our systems and always ready to improve based on your feedback. As Rohit Wad, our Chief Technology Officer, put it, “Despite being a leading global blockchain ecosystem, one of our strongest values at Binance is we always stay humble.”
It is in this spirit of transparency that we wanted to share more details on our API uptime and incidents in the first half of this year, to show how we ensure stable, scalable and available trading for all our users.
Why API Uptime Monitoring is Essential
Many of Binance’s 200M+ users rely on our application programming interfaces (APIs) for price, depth, trading activity, and many other data points essential for their market research and trading strategies. Therefore, we need to ensure these data feeds are always available to meet the needs of the 24/7 crypto market.
In order to do this, we closely monitor our uptime across all of our essential trading APIs. Below is a look at how we performed in H1 of 2024.
The list of APIs presented in the table is publicly available here. These APIs are mainly used for tracking real-time changes in the market, allowing traders and investors to track the latest prices and see historical trends for instruments such as equities, fixed-income products, derivatives, and currencies.
However, during periods of high traffic volume, APIs can sometimes not work as expected. The HTTP Return Codes section of this document describes potential reasons HTTP requests may fail to be successfully completed.
The first half of 2024 saw one incident, which impacted some of our API endpoints during a period of unprecedented trading activity.
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 first quarter of 2024 we had: 44,640 uptime minutes in January; 41,760 minutes in February; and 44,640 minutes in March, amounting to the overall 131,040 minutes in Q1. Accounting for the incident in February, which resulted in 12 minutes of partial downtime on some of our query API services (leaving us with 131,028 minutes of uptime), our uptime percentage calculation looks like this:
131,028 mins / 131,040 mins * 100 = 99.99%
Going forward, we will be sharing similar uptime reports each quarter. In the meantime, if you have any suggestions as to how we can improve our APIs, please raise them using our Product Feedback & Suggestions platform.