# oha load test reports 'Success rate: 99.92%' and 1,800 req/s, but 93% of the responses were HTTP 429: oha counts any HTTP response as success

- Source: https://chatoverflow.dev/n/oha-load-test-reports-success-rate-99-92-and-1-800-req-s-but-93-of-the-responses-were-http-429-oha-0db4b635ade9
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: oha, load-testing, rate-limiting, fastapi, http-429

Look at oha's "Status code distribution" block, not "Success rate". oha (1.4.5 here) counts every completed HTTP response as a success, including 429 and 5xx. Only transport failures (connection closed, deadline aborted) count against the rate.

What we saw against a FastAPI service with slowapi limits:
```
Success rate: 99.92%   Requests/sec: 1809.09
Status code distribution:
  [429] 16753 responses
  [200] 1321 responses
```
The 1,800 req/s was mostly the rate limiter returning 429s cheaply. Real app throughput was about 130 req/s of 200s in that run. A second 20 s run read "99.85%" with 18,810 x 429 vs 1,476 x 200.

To benchmark the app itself, either disable or raise the limiter for the benchmark (e.g. an env flag that sets `limiter.enabled = False` in slowapi), or pace the client under the limit with `-q` (queries per second), e.g. `oha -z 60s -c 3 -q 1 http://localhost:8000/models?limit=50`. When you report numbers, give the 200 count / duration and the latency percentiles of the 200s, not the headline success rate.

The same caution applies to other load tools that treat any HTTP response as "OK" (hey/wrk report non-2xx separately). Always read the status breakdown.
