← All status codes
429

Too Many Requests

The client sent too many requests in a given amount of time, and the server is asking it to slow down.

The response may include a Retry-After header, either in seconds or as a date, saying when to try again. Not every service uses 429 for rate limits. Some send 403 or 503 instead.

What we see on Larm

Failed HTTP checks on Larm from 9 October to 8 November 2026, across about 130 monitors.

One monitor got 429s in this period, 11 failed checks in total.

COMMON CAUSES

Going over a per-IP, per-key, or per-account limit
Many clients sharing one IP address, like CI runners or an office network
A retry loop with no backoff
Monitoring checks that count against the same limit as real traffic

HOW TO FIX IT

Read Retry-After and wait that long before retrying
Add exponential backoff with jitter to retries
Ask for a higher limit, or a separate key for monitoring
Check less often

What this means for monitoring

If the monitor sends an API key, every check counts against that key's limit. Give the monitor its own key, or monitor an endpoint that isn't rate limited.

Related status codes

4xx Client Error

400
Bad Request

The server can't process the request because something is wrong with it. Missing required fields, invalid JSON, wrong data types. Check your request body and query parameters.

401
Unauthorized

The server needs to know who you are, and the request either didn't say or said it wrong. Despite the name, 401 is about authentication (who you are), not authorization (what you're allowed to do). That's 403.

403
Forbidden

The server understood the request and won't allow it. Unlike 401, sending the same credentials again won't help.

404
Not Found

The server can't find anything at this URL. The path is wrong, the resource was removed, or it was never there.

405
Method Not Allowed

The HTTP method isn't supported for this URL. You sent a DELETE to an endpoint that only accepts GET and POST. The response includes an Allow header listing valid methods.

408
Request Timeout

The server gave up waiting for the client to finish sending its request. It's the server saying the client was too slow, not the other way around.

409
Conflict

The request conflicts with the current state of the resource. Common with concurrent updates: two people editing the same record, or trying to create a resource that already exists.

410
Gone

The resource existed but has been permanently deleted. Unlike 404, this is deliberate: the server is saying "it was here, it's not anymore, and it's not coming back."

413
Content Too Large

The request body is larger than the server is willing to accept. Common when uploading files that exceed the server's size limit.

415
Unsupported Media Type

The server doesn't support the Content-Type of the request. You sent XML but the endpoint only accepts JSON, or you forgot the Content-Type header entirely.

422
Unprocessable Content

The request is well-formed but the content is invalid. The JSON is valid, but the data doesn't pass validation: missing required fields, values out of range, business rule violations.

Get alerted when your endpoints return unexpected status codes.

Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.