a month ago
Hello, my database using the railway template has stopped accepting connections, they just spin forver untill timeout. I found this thread https://station.railway.com/questions/database-no-longer-accepting-connections-47e930b3 and tried to redeploy. But it didn't work. Any help would be appreciated 
```
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/c6c9a9db-ffca-4b17-b384-d5ee10572577/vol_43d1u4yb8xeh12tg
Starting Container
2026-02-11 19:13:24.933 UTC [12] LOG: database system is ready to accept connections
Certificate will not expire
Adding pg_stat_statements to shared_preload_libraries...
PostgreSQL Database directory appears to contain a database; Skipping initialization
2026-02-11 19:13:24.397 UTC [12] LOG: starting PostgreSQL 17.7 (Debian 17.7-3.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-02-11 19:13:24.397 UTC [12] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-02-11 19:13:24.397 UTC [12] LOG: listening on IPv6 address "::", port 5432
2026-02-11 19:13:24.403 UTC [12] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-02-11 19:13:24.414 UTC [35] LOG: database system was interrupted; last known up at 2026-02-11 19:05:58 UTC
2026-02-11 19:13:24.880 UTC [35] LOG: database system was not properly shut down; automatic recovery in progress
2026-02-11 19:13:24.885 UTC [35] LOG: redo starts at 0/2141658
2026-02-11 19:13:24.885 UTC [35] LOG: invalid record length at 0/2141690: expected at least 24, got 0
2026-02-11 19:13:24.885 UTC [35] LOG: redo done at 0/2141658 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2026-02-11 19:13:24.898 UTC [33] LOG: checkpoint starting: end-of-recovery immediate wait
2026-02-11 19:13:24.926 UTC [33] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.002 s, total=0.031 s; sync files=3, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB; lsn=0/2141690, redo lsn=0/2141690
```
5 Replies
a month ago
So sorry you encountered this problem. We had an incident that caused problems for some users (https://status.railway.com/cmli5y9xt056zsdts5ngslbmp). I see that your service is online now. Please try restarting the service if you are still having problems. Let us know if that does not resolve it and we can investigate further. If you are having connection problems, please let us know if it is using the private or public address.
Status changed to Awaiting User Response Railway • about 1 month ago
sam-a
So sorry you encountered this problem. We had an incident that caused problems for some users (https://status.railway.com/cmli5y9xt056zsdts5ngslbmp). I see that your service is online now. Please try restarting the service if you are still having problems. Let us know if that does not resolve it and we can investigate further. If you are having connection problems, please let us know if it is using the private or public address.
a month ago
Seems good now, connection works again. Thank you
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Glad to hear!
For some extra context a full post mortem is available at:
https://blog.railway.com/p/incident-report-february-11-2026
Status changed to Awaiting User Response Railway • about 1 month ago
noahd
Glad to hear!For some extra context a full post mortem is available at:https://blog.railway.com/p/incident-report-february-11-2026
a month ago
Hey could I get a bit more insight into your processes ? I noticed yesterday that my production DB didn't experience the outage only on my staging environemnt. Do you have a policy where you identify the user production and not production environments and release first to the non critical ones ? Or was my prod DB at risk of being affected by the 3% of services ? If so is there anything I can do to mitigate the risk ?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We have no environment differentiators; your services were just part of that random 3%.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved poljsakerik • about 1 month ago