> For the complete documentation index, see [llms.txt](https://docs.mercurydata.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercurydata.app/genaral-info/service-availability.md).

# Service availability

### Health Status

`GET /rest/health` returns the current status of Mercury and its ingestion lag relative to the Stellar network. No authentication required.

\
**Endpoints**

* <https://mainnet.mercurydata.app/rest/health>
* <https://testnet.mercurydata.app/rest/health>

\
**Response**

```json
{
  "service": "up",
  "mercury_latest_ledger": 62458843,
  "stellar_latest_ledger": 62458843
}
```

| Field                   | Description                                                                  |
| ----------------------- | ---------------------------------------------------------------------------- |
| `service`               | `"up"` if all systems are operational, `"down"` if any component is degraded |
| `mercury_latest_ledger` | The latest ledger Mercury has indexed                                        |
| `stellar_latest_ledger` | The current Stellar network tip (from Horizon)                               |

If `mercury_latest_ledger` is significantly behind `stellar_latest_ledger`, Mercury is catching up. Both fields may be absent if unavailable.

### Live status updates

Mercury posts live status updates to the public `live-status` Discord channel. You'll see a message whenever:

* The service/API goes down or comes back online
* Ingestion falls behind the Stellar network tip and later catches back up

Join the server (see [Access & Get in Touch](/genaral-info/access.md)) and activate notifications for the channel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mercurydata.app/genaral-info/service-availability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.