Why am I getting rate-limited (429 responses)?
- Topic
- Troubleshooting
- Asked by
- Developers
A 429 Too Many Requests means you've hit a rate limit. Atlas rate-limits every endpoint per instance to protect against abuse, and returns standard headers so you can adapt:
Retry-After— how long to wait before retrying.RateLimit-*headers — your remaining budget and reset window.
To fix it:
Honor
Retry-Afterand use exponential backoff on retries.Cache things like the JWKS instead of fetching per request (the SDKs do this).
Batch management operations rather than looping one call per item.
Use the right key — heavy server-side work should go through the backend SDK/secret key, not the frontend.
Sensitive auth endpoints also apply account lockout after repeated failures, which can look like rate limiting. See rate limits.
Atlas applies per-instance rate limits with standard rate-limit headers. A 429 means you've exceeded the limit for that endpoint — back off using the Retry-After header, and batch or cache where you can.