InfoFounding Members35 lifetime licenses available: view the offerInfoMCP launch announcementConnect Claude, Cursor or any MCP client with your API token to let an agent create monitors, manage incidents and configure alerts. Read the docs
Tools
Free tool

HTTP status codes

A searchable reference for the status codes you see in logs, APIs and uptime monitors. Filter by class or search by code, name or description.

43 codes
1xx · Informational
  • 100Continue
    The server received the request headers and the client should send the body.
  • 101Switching Protocols
    The server agrees to switch protocols, used for WebSocket upgrades.
  • 102Processing
    WebDAV: the server is still working on the request.
  • 103Early Hints
    Sent before the final response so the client can preload resources.
2xx · Success
  • 200OK
    The request succeeded. The meaning depends on the method used.
  • 201Created
    The request succeeded and a new resource was created.
  • 202Accepted
    The request was accepted for processing but is not finished yet.
  • 204No Content
    The request succeeded but there is nothing to return in the body.
  • 206Partial Content
    Only part of the resource is returned, used for range requests.
  • 207Multi-Status
    WebDAV: the response contains several status codes for sub-requests.
3xx · Redirection
  • 300Multiple Choices
    The resource has several representations and the client must choose one.
  • 301Moved Permanently
    The resource has moved to a new permanent URL.
  • 302Found
    The resource is temporarily at a different URL.
  • 303See Other
    Redirect to another URL, typically after a POST that should become a GET.
  • 304Not Modified
    The cached version is still fresh, no body is sent.
  • 307Temporary Redirect
    Temporary redirect that keeps the original HTTP method.
  • 308Permanent Redirect
    Permanent redirect that keeps the original HTTP method.
4xx · Client error
  • 400Bad Request
    The server cannot parse the request, often malformed syntax or headers.
  • 401Unauthorized
    Authentication is required or the credentials are missing or invalid.
  • 402Payment Required
    Reserved for future use, sometimes used for paid APIs.
  • 403Forbidden
    The server understood the request but refuses to authorize it.
  • 404Not Found
    The requested resource does not exist on the server.
  • 405Method Not Allowed
    The HTTP method is not supported for this resource.
  • 408Request Timeout
    The server timed out waiting for the request to complete.
  • 409Conflict
    The request conflicts with the current state of the resource.
  • 410Gone
    The resource is permanently deleted and will not come back.
  • 413Payload Too Large
    The request body exceeds the size limit of the server.
  • 415Unsupported Media Type
    The payload format is not supported by the server.
  • 418I'm a teapot
    An April Fools joke from RFC 2324, sometimes still implemented literally.
  • 422Unprocessable Entity
    The request is well formed but contains semantic errors.
  • 425Too Early
    The server refuses to process a request that might be replayed.
  • 429Too Many Requests
    The client sent too many requests in a given time, rate limited.
  • 431Request Header Fields Too Large
    The request headers exceed the server's size limit.
  • 451Unavailable For Legal Reasons
    The resource is blocked for legal reasons.
5xx · Server error
  • 500Internal Server Error
    The server hit an unexpected condition it cannot handle.
  • 501Not Implemented
    The server does not support the functionality the request needs.
  • 502Bad Gateway
    A gateway or proxy received an invalid response from upstream.
  • 503Service Unavailable
    The server is temporarily overloaded or down for maintenance.
  • 504Gateway Timeout
    A gateway or proxy did not get a response from upstream in time.
  • 507Insufficient Storage
    WebDAV: the server cannot store the representation needed.
  • 508Loop Detected
    WebDAV: the server detected an infinite loop in the request.
  • 510Not Extended
    The server needs extended features that the client did not request.
  • 511Network Authentication Required
    The client must authenticate to the network before accessing the resource.

More free tools

Know when 5xx means your problem, not the client's

Uptriva classifies check results by status code and alerts you with the response detail attached, so you see the 503 before your users do.

Free tool by Uptriva. Reference data is bundled with the page.