MatrixTrak
Tool · Trading Bot Reliability

Rate Limit Headroom Calculator

Calculate real-time rate limit headroom for Binance, Bybit, Kraken, KuCoin, and OKX. Get burst ceiling recommendations and prevent 429 errors before they trigger exchange bans.

5exchanges
3endpoint tiers
real-timecalculation

Exchange rate limits are a contract, not a bug. Each exchange enforces a maximum request weight per time window. Exceeding the limit triggers HTTP 429 responses, temporary IP bans, or permanent API key revocation. This calculator helps you stay within the safe zone (≤80% utilization) so retries and bursts don't push you over the edge.

Calculator

1,200 weight per minute. Endpoint weights range from 1 (POST order) to 20 (GET exchangeInfo).

Weight: 5 · e.g. GET /api/v3/depth

Requests per minute you expect to send

Safe25.0% of 1200 weight limit
0%70% warning90% critical100%
300 weight used1200 max
Headroom

900 weight

75.0% remaining

Safe Max RPM

192 RPM

At 80% utilization

Burst Ceiling

192 RPM

960 weight

Time to exhaustion

180s

180 requests left

All clear — rate is within safe bounds

Your current rate (25.0% utilization) leaves enough headroom for retries and occasional bursts. Safe max for this endpoint: 192 RPM.

# Binance Rate Limit Config
# Generated by MatrixTrak Rate Limit Headroom Calculator
# Window: 60s | Max weight: 1200

rate_limiter:
  exchange: binance
  window_ms: 60000
  max_weight: 1200
  current_weight_per_req: 5
  current_rate_rpm: 60
  consumption_pct: 25.0%
  safe_max_rpm: 192
  burst_ceiling: 192
  burst_ceiling_weight: 960
  status: Safe
  recommendations:
    - Rate is within safe bounds
    - 
    - Enable jitter on retry intervals to avoid thundering herd
    - Monitor X-RateLimit-Remaining header in responses

Related tools

Exchange Error Lookup

Live

Look up error codes for Binance, Bybit, Kraken, KuCoin, and OKX with recovery actions.

Timestamp Drift Checker

Live

Diagnose exchange clock drift and recvWindow errors with an interactive checklist.

Exchange Config Generator

Live

Generate YAML config snippets for Binance, Bybit, Kraken, KuCoin, and OKX.

Frequently asked questions

Frequently asked questions

What is a rate limit weight?
Exchanges like Binance assign a 'weight' to each API endpoint instead of counting raw requests. A lightweight call like GET /ticker might cost 1 weight, while a heavy call like GET /exchangeInfo costs 20. Your total weight consumed across all endpoints must stay under the exchange's per-window maximum (e.g., 1,200 weight/min for Binance).
What happens if I exceed the rate limit?
Exchanges return HTTP 429 (Too Many Requests) with a Retry-After header. Repeated violations can trigger temporary IP bans (5–60 minutes), and persistent abuse may lead to permanent API key revocation. Some exchanges also throttle your requests silently before returning errors.
Why should I stay at 80% utilization?
The 80% rule leaves headroom for retries after failures, occasional bursts from user actions or market events, and the fact that rate limit windows don't align perfectly with your request timing. Running at 90%+ means a single retry storm can push you over the limit and trigger a ban cascade.
How do I handle rate limit headers in code?
Exchanges return headers like X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After. Your bot should read these headers on every response and dynamically throttle — not rely on a static config. If Remaining drops below 10%, pause all non-critical requests until the window resets.
Which exchange has the strictest rate limits?
Kraken enforces the tightest public API limits at ~1 request/second. KuCoin uses short 3-second burst windows that reset quickly. Binance has the most forgiving system (1,200 weight/min) but also the most aggressive ban enforcement for repeat offenders.

What engineers say

What engineers say

“The retry policy generator alone saved us from a production incident. We had exponential backoff configured wrong for months — the timeline visualization made it obvious instantly.”
A

Alex R.

Senior Backend Engineer, Fintech Startup

1 / 16

Newsletter

Weekly engineering insights

Get practical tips on AI, .NET, trading bot reliability, and building scalable systems. No spam, unsubscribe anytime.