← All status codes
304

Not Modified

The resource hasn't changed since your last request. The server is telling the client to use its cached copy. This is a good thing — it means caching is working.

COMMON CAUSES

Client sent If-Modified-Since or If-None-Match headers
Resource hasn't changed since the cached version

HOW TO FIX IT

Nothing to fix — caching is working correctly
If you don't want caching, remove conditional request headers

What this means for monitoring

If your monitor sends caching headers (ETag, If-Modified-Since), you might get 304s instead of 200s. Most monitoring tools don't send these.

Related status codes

3xx Redirection

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.