When a monitor's state changes, the
state change history log entry includes a
status code and a human-readable
description explaining why the state changed. This page documents every status code that can appear in that field, including the standard HTTP status codes returned by the monitored resource and a set of custom Pinghome codes used by port checkers.
How These Codes Affect Monitor State
Whether a code results in state: 1 (up) or state: 0 (down) depends on the monitor's checker type:
- Port checkers (raw TCP/UDP) — up only on 200–299 or the custom 2000 code; if conditions are configured, a passing condition also means up. The custom codes 4030, 4080, and 5000 always mean down.
- HTTP checkers — up on 200–299 or 300–399 (redirects) when no conditions are configured, or on a passing condition. Everything else means down, including the synthetic 408 and 500 codes generated when a check fails before a real HTTP response is received.
Custom Status Codes
| Code | Description |
|---|
| 2000 | The request has succeeded. |
| 4030 | The request failed because one or more conditions were not met. |
| 4080 | The client did not receive a complete response within the time that it was prepared to wait. |
| 5000 | Connection to server refused |
1xx — Informational
| Code | Description |
|---|
| 100 | The request can be continued. |
| 101 | The server is switching protocols. |
| 102 | The server has received the request headers and is processing them. |
2xx — Success
| Code | Description |
|---|
| 200 | The request has succeeded. |
| 201 | The request has been fulfilled and has resulted in one or more new resources being created. |
| 202 | The request has been accepted for processing, but the processing has not been completed. |
| 203 | The information presented in the response is not the definitive set as it is from a third-party source. |
| 204 | The server has successfully fulfilled the request and that there is no additional content to send in the response payload body. |
| 205 | The server has fulfilled the request and desires that the user agent reset the "document view", which caused the request to be sent, to its original state as received from the origin server. |
| 206 | The server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation that correspond to the satisfiable ranges found in the request's Range header field. |
| 207 | The server has fulfilled a request for the resource, and the returned representation is a representation of the result of one or more instance-manipulations applied to the current instance. |
| 208 | The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again. |
| 226 | The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. |
3xx — Redirection
| Code | Description |
|---|
| 300 | The server is providing multiple options for the resource from which the client may choose. |
| 301 | The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs. |
| 302 | The target resource resides temporarily under a different URI. |
| 303 | The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request. |
| 304 | The server has not modified the selected resource. |
| 305 | The requested resource must be accessed through the proxy given by the location field. |
| 307 | The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide a temporary response to the request. |
| 308 | The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide a permanent response to the request. |
4xx — Client Error
| Code | Description |
|---|
| 400 | The server cannot or will not process the request due to something that is perceived to be a client error. |
| 401 | The request has not been applied because it lacks valid authentication credentials for the target resource. |
| 402 | The payment required to access the target resource has not been provided. |
| 403 | The server refuses to authorize the request. |
| 404 | The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. |
| 405 | The method specified in the request is not allowed for the target resource. |
| 406 | The server cannot produce a response matching the list of acceptable values defined in the request's headers. |
| 407 | The client needs to authenticate itself to get the requested response. |
| 408 | The client did not receive a complete response within the time that it was prepared to wait. |
| 409 | The request could not be completed due to a conflict with the current state of the target resource. |
| 410 | The target resource is no longer available at the origin server and that this condition is likely to be permanent. |
| 411 | The server refuses to accept the request without a defined Content-Length. |
| 412 | One or more preconditions contained in the request header fields evaluated to false when tested on the server. |
| 413 | The server refuses to process the request because the request payload is larger than the server is willing or able to process. |
| 414 | The server refuses to service the request because the request-target is longer than the server is willing to interpret. |
| 415 | The server refuses to accept the request because the payload format is in an unsupported format. |
| 416 | The server cannot serve the requested range. |
| 417 | The server cannot meet the requirements of the Expect request-header field. |
| 418 | This HTTP status is used as an Easter egg in some websites, including Google.com. |
| 421 | The request was directed at a server that is not able to produce a response. |
| 422 | The server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. |
| 423 | The source or destination resource of a method is locked. |
| 424 | The method could not be performed on the resource because the requested action depended on another action and that action failed. |
| 426 | The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. |
| 428 | The origin server requires the request to be conditional. |
| 429 | The user has sent too many requests in a given amount of time. |
| 431 | The server is unwilling to process the request because its header fields are too large. |
| 451 | The user requests an illegal resource, such as a web page censored by a government. |
5xx — Server Error
| Code | Description |
|---|
| 500 | The server encountered an unexpected condition that prevented it from fulfilling the request. |
| 501 | The server does not support the functionality required to fulfill the request. |
| 502 | The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request. |
| 503 | The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. |
| 504 | The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request. |
| 505 | The server does not support, or refuses to support, the major version of HTTP that was used in the request message. |
| 506 | The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process. |
| 507 | The server is unable to store the representation needed to complete the request. |
| 508 | The server detected an infinite loop while processing the request. |
| 510 | Further extensions to the request are required for the server to fulfill it. |
| 511 | The client needs to authenticate to gain network access. |
