1 day ago
3
We are pleased to announce a platform architecture upgrade to fundamentally enhance the core performance, security, and architectural stability of our trading platform. From Dec 2nd onward, the underlying rate limiting mechanism will be upgraded, and will be both faster and more consistent. No action is required from you at this time.
Please note the following:
Header Transientness: You might notice transient variations in the x-rate-limit-remaining and x-ratelimit-remaining-1s headers when sequential requests are routed to different processing servers simultaneously.
No Overall Change to Limits: crucially, the actual rate limits remain unchanged, and all requests will continue to count towards the same overall balance.
New Response Headers for Debugging
We are introducing three new response headers to improve client-side transparency and simplify debugging:
Header Name | Purpose |
x-ratelimit-limit-1s | Informs you of the maximum number of requests allowed within one second when the order burst rate limit is applied. |
x-request-id | A unique tracing identifier for each request. |
x-stream-id | A unique tracing identifier associated with the request stream. |
Including the x-request-id and x-stream-id in any bug reports or technical inquiries will allow our technical team to rapidly locate and diagnose corresponding log messages, significantly expediting issue resolution.
Thank you for your continued support and trust in our platform.
The BitMEX Team
English (US) · 