HTTP code · source checked September 28, 2026

429 error code: too many requests

HTTP 429 Too Many Requests indicates rate limiting: a user sent too many requests in a given amount of time.

System: HTTPPrimary reference: IETF / RFC Editor

Plain-language meaning

What does HTTP code 429 mean?

According to IETF / RFC Editor: RFC 6585 defines HTTP 429 as a response for too many requests in a given amount of time. The response may include a Retry-After header indicating how long to wait before making another request. RFC 6585 says the response representation should explain the condition, and it notes that a server is not obligated to use 429 at all — it may instead drop connections when defending against a request flood.

Keep the code in its namespace

What does this code tell you, and what does it not?

A 429 describes request rate, not a permanent account ban. The response may explain the limit, and the server is not required to include a retry time. RFC 6585 also states that responses with the 429 status code must not be stored by a cache, so each 429 should reflect the server's current rate decision rather than a cached copy.

Conservative next step

Where should I check next?

Check the response for Retry-After and honor the service's documented rate limit. If you are a regular visitor, stop repeated refreshes and retry later; if you maintain the client, reduce request frequency rather than trying to evade the limit.

Primary source

Which official source supports this?

This explanation is scoped to the linked IETF / RFC Editor material, checked September 28, 2026. The original source takes priority and may change its instructions.

RFC 6585, Section 4: 429 Too Many Requests

Same code system

Browse platform codes