---
title: Replication status
description: The following command displays a snapshot of replication monitoring information:
component: pingds
version: 7.4
page_id: pingds:config-guide:repl-status
canonical_url: https://docs.pingidentity.com/pingds/8.1/config-guide/repl-status.html
llms_txt: https://docs.pingidentity.com/pingds/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-08-10T15:45:40Z
keywords: ["LDAP", "Replication", "Troubleshooting"]
superseded_by: https://docs.pingidentity.com/pingds/8.1/config-guide/repl-status.html
---

# Replication status

The following command displays a snapshot of replication monitoring information:

```bash
$ 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

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

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. For details, refer to [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).