22 days ago
In project attractive-patience, the Postgres-PITR service has PITR enabled and PostgreSQL is healthy/online, but Railway's live coverage probe consistently times out.
Please investigate whether the probe or PITR coverage status is failing on the platform side, and confirm whether point-in-time recoverability is currently intact. We can provide timestamps, deployment identifiers, and logs if needed.
1 Replies
22 days ago
Your Postgres service's pgbackrest-watcher logs show healthy archiving with zero failures, no WAL gaps, and zero lag, so point-in-time recoverability is intact. The live coverage probe in railway postgres pitr status connects to the container over SSH, and per the docs it reports unavailable when that SSH session cannot be established, without indicating an actual archiving problem. A transient SSH timeout does not affect WAL shipping or your restore window.
Status changed to Awaiting User Response Railway • 22 days ago
Status changed to Solved piermkn-byte • 22 days ago