Droplet → Managed PostgreSQL: Standby readiness timing after automatic failover

Objective

The goal is to determine how long a DigitalOcean Managed PostgreSQL cluster remains in a write‑unavailable state after the primary node becomes unreachable and failover is triggered.

Constraints

Network latency between the Droplet and the database can skew measurements, and the synchronization period of the standby varies by PostgreSQL version and cluster configuration. The documentation does not specify an exact window during which the standby is catching up.

Unresolved Behavior

While the cluster status endpoint reports the current role of each node, it is unclear whether a change to "standby" immediately implies that the node accepts write connections, or if there is an intermediate period of replication lag that temporarily blocks writes.

Specific Questions

• What is the typical duration of the standby synchronization window after an automatic failover?
• Are there API endpoints or status flags that reliably indicate when the standby is fully ready for write operations?
• Can monitoring tools be configured to detect the moment the standby accepts writes, and if so, what metrics or logs should be examined?