4 months ago
is there an outage? this just started
cause: Error: write CONNECT_TIMEOUT pgvector-rfxj.railway.internal:5432
at connectTimedOut (file:///app/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/src/connection.js:262:20)
at Timeout.done [as onTimeout] ( _file:///app/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/src/connection.js:1059:8)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'CONNECT_TIMEOUT',
errno: 'CONNECT_TIMEOUT',
address: 'pgvector-rfxj.railway.internal',
port: 5432
9 Replies
4 months ago
public url is down too. trying to redeploy postgres container and thats just stuck. Is there an outage?
4 months ago
cant view or create backups either
/orchestrator.RouterLegacyService/ListVolumeInstanceSnapshots UNAVAILABLE: connection error: desc = "transport: Error while dialing: dial tcp 10.64.128.16:50052: i/o timeout"
4 months ago
Tried to delete the postgres service to attach it's volume to a new one and now completely stuck 'Applying Changes'
Please asssit
4 months ago
Finally resolved itself
4 months ago
Hello,
There was an issue with the host your database was on, and it needed to be rebooted. We have sent you a notification about this.
We are deeply sorry for the impact this has had.
Status changed to Awaiting User Response Railway • 4 months ago
brody
Hello, There was an issue with the host your database was on, and it needed to be rebooted. We have sent you a notification about this. We are deeply sorry for the impact this has had.
4 months ago
its still happening sporadically. CONNECT_TIMEOUT to the database from other services over the internal url
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
I'm not seeing any issues with any of the hosts your apps are on; they all have a clean bill of health according to the metrics.
Status changed to Awaiting User Response Railway • 4 months ago
brody
I'm not seeing any issues with any of the hosts your apps are on; they all have a clean bill of health according to the metrics.
4 months ago
It's a weird problem I haven't seen until today. I'll deploy a service that depends on the database, it'll get stuck in the queue longer than normal, and then post deploy it gets connection refused to the database until I redeploy the same commit via Railway dashboard. Thank you
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
You should be good here, as we have made a myriad of improvements to many aspects of our network over the past 48 hours, but please let us know if you are still seeing issues.
Status changed to Solved dseravalli • 4 months ago