2 months ago
params: ab21efca-fc01-41dd-becc-1d930ca32c81,d47qpVjBEBEmq7j8rKBKuf0i7w4,1
at PostgresJsPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:73:11)
at listOnTimeout (node:internal/timers:583:11)
at process.processTimers (node:internal/timers:519:7) {
code: 'CONNECT_TIMEOUT',
errno: 'CONNECT_TIMEOUT',
address: 'yamabiko.proxy.rlwy.net',
port: 59974
}
}
params: [
'ab21efca-fc01-41dd-becc-1d930ca32c81',
'd47qpVjBEBEmq7j8rKBKuf0i7w4',
1
],
cause: Error: write CONNECT_TIMEOUT yamabiko.proxy.rlwy.net:59974
at connectTimedOut (file:///app/node_modules/postgres/src/connection.js:257:20)
at Timeout.done [as onTimeout] (file:///app/nodemodules/postgres/src/connection.js:1039:8)
[api-logger] Failed to log API call to MongoDB: Socket 'connect' timed out after 5001ms (connectTimeoutMS: 5000)
2 Replies
2 months ago
Thanks for confirming! We've called a retroactive incident at https://status.railway.com/cmkp3viv2095wb4fh9ggdmw4l.
Going to consider this resolved, please feel free to re-open this thread or create a new one if you're still experiencing issues.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved ray-chen • about 2 months ago