Find answers, guides, and tutorials to supercharge your content delivery.

429 Too Many Requests

Updated on October 4, 2018
429 Too Many Requests

What does a 429 Too Many Requests error mean?

A 429 Too Many Requests error occurs when a user tries to perform too many requests within a certain timeframe. This error is triggered based on the particular rate limiting settings that a service provider's servers have in place. Rate limiting is used in order to limit the number of requests a user is able to perform to help reduce the risk of their server's being overloaded.

How you might see a 429 Too Many Requests error

There are a few different ways that you may see a 429 Too Many Requests error. The following list outlines a few of these variations that you may see. Although they are slightly different, each one means the same thing.

  • 429 Error
  • Error 429 (Too Many Requests)
  • 429 Too Many Requests
  • Too Many Requests
  • HTTP 429

How to fix a 429 error

As a user receiving a 429 Too Many Requests error, there isn't really a way to "fix" it. As mentioned above, a 429 error is due to too many requests being made within a given timeframe. The server is therefore not willing to process all of the requests being made at once. Therefore, it's important to know what rate limiting scheme your service provider has in place and to avoid reaching that limit in order to avoid receiving a 429 error.

According to RFC 6585, a 429 Too Many Requests response should also include details regarding the condition of the rate limiting scheme in place. The server may also return a Retry-After header which indicates how long the user should wait before making another request. An example 429 status response may look similar to the following.

HTTP/2 429 Too Many Requests
Content-Type: text/html
Retry-After: 600

        <title>Too Many Requests</title>
    <h1>Too Many Requests</h1>
       <p>I only allow 50 requests per hour to this Web site per
 logged in user. Try again soon.

Although returning a 429 status code error is beneficial as it lets the user know that they have reached a limit in the amount of allowable requests, servers are not required to return this status code. For instance, if a server is under attack it would require the use of valuable resources in order to return a 429 error to each request. Therefore, in such a case it may be more beneficial to simply drop connections or employ another form of defense which is less resource intensive.


Overall, if you are receiving a 429 Too Many Requests error, you will most likely need to reduce the amount of requests being made to the server during a given timeframe. If you are unsure what the details are regarding the rate limiting scheme that the particular service you are using has in place, it is best you contact them to see what in fact the limit is. Additionally, some services may have different plans in place that allow you to increase your request limit based on your needs.

KeyCDN uses cookies to make its website easier to use. Learn more about cookies.