HTTP 4xx
429 Too Many Requests
The client has sent too many requests in a given amount of time and is being rate limited.
What causes it
- A client, bot, or scraper exceeded a rate limit.
How to fix it
Respect the Retry-After header and back off. If it is your own traffic, raise limits or spread requests out.
Example response
A typical raw HTTP response a client receives for a 429, with the headers this code is defined around.
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: text/html; charset=utf-8Related codes
400Common
Bad RequestThe server could not understand the request, usually because it was malformed.401Common
UnauthorizedAuthentication is required and has failed or not been provided.403Common
ForbiddenThe server understood the request but refuses to authorize it. Unlike 401, authenticating will not help.404Common
Not FoundThe server could not find the requested resource. The URL may be wrong or the resource may have been removed.405
Method Not AllowedThe HTTP method is not supported for this resource, for example a POST to a read-only endpoint.408
Request TimeoutThe server timed out waiting for the client to finish the request.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 4xx error, so you can fix it before it costs you.