> 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.