← All status codes
500

Internal Server Error

Something went wrong on the server and it has nothing more specific to say. It's what most frameworks return when your code throws an exception it doesn't handle.

Because it's generic, the status code alone won't tell you much. The useful information is in your application logs and error tracker, at the time of the failed check.

What we see on Larm

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

12 monitors got a 500 in this period, with 2,749 failed checks in total. The median time to first byte was 92 ms. The app answered quickly, it just answered with an error.

COMMON CAUSES

An unhandled exception in application code
The database is unreachable or a query fails
Missing or wrong configuration after a deploy, like an environment variable or secret
A dependency, like another API, fails and the error isn't handled
The disk is full and writes fail

HOW TO FIX IT

Find the error in your logs or error tracker at the time of the check
Check what shipped recently, and roll back if the timing lines up
Check that the database and other dependencies are reachable
Check disk space and memory

What this means for monitoring

If every location sees a 500, the app has a real problem. If only some do, it may be one bad instance behind a load balancer, which is worth looking at even when most requests succeed.

Related status codes

5xx Server Error

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.