Production outage: PostgreSQL unreachable, SSH and restart failing
nazarbuchkovskyi-sketch
PROOP

19 days ago

Our production app ShareMe is experiencing a database connectivity outage. Please escalate this to the infrastructure team.

Project ID: b073dc02-d550-4bd4-9456-7b5d6d4aedb5

Environment: production

Postgres service ID: 1046bdbf-226d-4c12-bc98-9541bf1bbf91

Postgres deployment ID: c6a9fff4-589c-4580-8729-b704d3992b08

Region: us-west2

Observed on September 16, 2026:

  • Website and Worker cannot connect to postgres.railway.internal:5432.
  • DNS resolves successfully, but direct TCP connection tests from the Website container time out over BOTH IPv4 and IPv6.
  • SSH into Website works; SSH into Postgres fails.
  • Two attempts to restart Postgres using the Railway CLI failed with “Problem processing request”.
  • Railway displays Postgres as Online despite these connectivity failures.
  • Worker logs repeatedly report “Connection terminated due to connection timeout”.
  • https://shareme.studio/readyz returns ready:false.
  • Admin login is unavailable, and the dashboard shows only 2/4 Worker replicas active.

The last PostgreSQL log available during our checks was at 16:25:45 UTC. Similar connection errors also occurred around 04:08–04:09 UTC earlier that day.

Could you check the Postgres host/container and private network connectivity, confirm whether this is a known incident, and help restore service while preserving the existing database volume and data?

Please provide an ETA if available. We have not confirmed the underlying cause.

Solved

1 Replies

adamlutz
PRO

19 days ago


Status changed to Awaiting User Response Railway • 19 days ago


Railway
BOT

12 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 12 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...