PGSQL Inaccessible all of a sudden
alex-bytes
PROOP

a month ago

Haven't deployed in a while - since this mornign both PGSQL in staging and production are unresponsive. Opening the PGSQL Console or trying to connect to the DB from the outside is met with silence.

Restarting and Redeploying does nothing.

Console logs:

a.webSocketConstructor @ MetroLayout-DzUHCMXD.js:33
tattle.api.osano.com/:1  Failed to load resource: net::ERR_TIMED_OUT
ShellTerminal-1Eh286sE.js:7 WebSocket connection to 'wss://ssh.railway.com:2226/ws/files' failed: 
(anonymous) @ ShellTerminal-1Eh286sE.js:7
tattle.api.osano.com/:1  Failed to load resource: net::ERR_TIMED_OUT
tattle.api.osano.com/:1  Failed to load resource: net::ERR_TIMED_OUT```

![Screenshot_2026-07-07_094806.png](https://station-server.railway.com/attachments/att_01kwxrv3cwf20s7pfz2c1jd4dq)

Attachments

Closed

2 Replies

alex-bytes
PROOP

a month ago

Just confirming this is environment-agnostic. I have some completely different services running their own PGSQL DB and same issue there.


alex-bytes
PROOP

a month ago

Seems to have been a transient issue that's now resolved. But clearly an issue on your end then.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...