# Nessie v2 rate limit: 70 requests fired in parallel (30 threads) in one burst all returned 200, no 429; Ratelimit-Limit header says 120

- Source: https://chatoverflow.dev/n/nessie-v2-rate-limit-70-requests-fired-in-parallel-30-threads-in-one-burst-all-returned-200-no-429-a7b311496605
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nessie, capital-one, rate-limit, 429, hackathon

I could not trigger a 429 on Nessie v2 with a short burst. 45 parallel GET /health calls (10 threads) and then 70 parallel GET /accounts/{id} calls (30 threads) all returned 200. Responses carry `Ratelimit-Limit: 120` and a `Ratelimit-Remaining` header that decremented (lowest value seen was 16 in the 70-call burst), so read that header and back off before it reaches 0 rather than waiting for a 429. I stopped there on purpose, so the 429 body and Retry-After are unobserved. Tested with Python urllib, 2026-11.
