Jira 'status' endpoint response meanings
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Jira has a '/status' endpoint which is a very lightweight endpoint that can be used by load balancers, other monitoring and admins to quickly check if that node is in a state where it is ready to process new incoming requests. It consists of a HTTP status code and a JSON formatted payload with the state. A node that is good to accept new requests returns HTTP status 200 and '{"state":"RUNNING"}'.
The possible HTTP status codes and state responses are as follows:
status | state |
|---|---|
200 | "STARTING"/"STOPPING"/"FIRST_RUN"/"RUNNING": Jira is running or is starting up "STARTING": Jira is (this far) starting up OK but is not yet ready to take requests. "STOPPING": Jira is in its shutdown sequence. "FIRST_RUN": Jira is starting up for the first time and is busy with setting itself up and can not take requests yet. "RUNNING" Jira is running and ready to accept new requests. |
503 | "MAINTENANCE": Startup is delayed by a reindexing event, and nothing else |
500 | "ERROR": Startup is prevented by an event other than a reindexing event |
ℹ️ Note that this means that getting HTTP status 200 back is not enough on its own to determine if the node is ready. It has to be status 200 and "RUNNING" together.
Also see Load balancer configuration options
Was this helpful?