---
title: Replication status
description: The following command displays a snapshot of replication monitoring information:
component: pingds
version: 8.1
page_id: pingds:config-guide:repl-status
canonical_url: https://docs.pingidentity.com/pingds/8.1/config-guide/repl-status.html
revdate: 2026-02-09T09:34:08Z
keywords: ["LDAP", "Replication", "Troubleshooting"]
---

# Replication status

The following command displays a snapshot of replication monitoring information:

```console
$ dsrepl \
 status \
 --hostname localhost \
 --port 4444 \
 --bindDN uid=monitor \
 --bindPassword password \
 --trustStorePath /path/to/opendj/config/keystore \
 --trustStorePassword:file /path/to/opendj/config/keystore.pin \
 --no-prompt
```

> **Collapse: Show output**
>
> ```
> Base DN            Status  Receive     Replay
>                            delay (ms)  delay (ms)
> -------------------------------------------------
> dc=example,dc=com  OK               0           0
> uid=monitor        OK               0           0
> cn=schema          OK               0           0
> ```

Read the [dsrepl status](../tools-reference/dsrepl.html#dsrepl_status) command reference for details about the command output.

The command connects to each known server to read status information. It will eventually time out if other servers cannot be contacted.

To get a balanced view of replication delays, monitor them over time. You can do this with repeated use of the `dsrepl status` command, or by reading the monitoring information over LDAP or HTTP. Learn more in [Replication delay (Prometheus)](../monitoring-guide/http-monitoring.html#monitoring-replication-delay-http) or [Replication delay (LDAP)](../monitoring-guide/ldap-monitoring.html#monitoring-replication-delay-ldap).

|   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | You can also get replication status information by reading monitoring information over LDAP or HTTP. Learn more in [Replication delay (Prometheus)](../monitoring-guide/http-monitoring.html#monitoring-replication-delay-http) or [Replication delay (LDAP)](../monitoring-guide/ldap-monitoring.html#monitoring-replication-delay-ldap).Notice the value of the `Status` column in the command output doesn't necessarily match the monitoring attribute value. |