← All status codes
403

Forbidden

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

In monitoring, most 403s have nothing to do with permissions. They come from bot protection: a WAF, a CDN rule, or a security plugin decides the probe looks like a bot and blocks it. The site works in your browser, and every check fails.

What we see on Larm

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

403 was the most common failure by number of checks: 41,277 failed checks. They came from only 4 monitors, and the median time to first byte was 18 ms. A reply that fast on every check is what a block rule at the edge looks like, answering before the request reaches the app.

COMMON CAUSES

Bot protection blocking automated requests, like Cloudflare Bot Fight Mode, a WAF rule, or a security plugin
An IP or country blocklist
The API key doesn't have permission for this resource
A service that returns 403 for rate limits instead of 429
A web server with directory listing turned off and no index file

HOW TO FIX IT

Look at the response body. Bot protection pages usually say what blocked the request
Allow the Larm user agent, Larm/<version> (+https://larm.dev), in your WAF, or skip the bot check on your health endpoint
Check the API key's scopes
If it's a rate limit in disguise, check less often

What this means for monitoring

A 403 that starts right after you put a site behind a CDN or turn on bot protection is almost always the probes being blocked, not an outage. Fix the rule instead of turning the monitor off.

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.

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.

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.

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.