2 days ago
Hi! Is anyone else seeing this, or is there an issue on Railway's side?
We have two Postgres databases:
- Production DB: no public URL, only reachable over private networking. Our app is deployed on Railway and uses it without any problem; the app works and the data loads normally.
- Dev DB: has a public URL (TCP proxy), because we develop locally, outside Railway.
What we're seeing:
- Dev DB over the public TCP proxy (metro.proxy.rlwy.net): the connection times out (ETIMEDOUT). DNS resolves fine, and from the same network the same port is reachable on another host, so it doesn't look like a local firewall problem.
- Production DB in the Railway dashboard: the Database → Data tab gets stuck on "Attempting to connect to the database..." and then times out. "Deployment Online" and "Required Variables" both show as OK.
[3. Dev DB in the Railway dashboard: same behaviour as the production DB.]
The status page shows everything as operational. Is anyone else having this problem, or is there something we should check on our side (e.g. the TCP proxy settings)?
Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • 1 day ago
Status changed to Solved apsurdos • 1 day ago
2 days ago
Update: it's working again (since around 17:44 UTC on Oct 4). We had re-created the TCP proxy a few minutes earlier, but it still timed out right after that, so we can't tell whether it fixed itself or the new proxy just took a while to start working.
One suggestion: during all this the status page showed everything as operational. We spent quite a while running diagnostics to figure out whether the problem was on our side. It would really help if the status page reflected issues like this, or if users got some kind of notice when public TCP proxy connections are affected.
Thanks!
Status changed to Awaiting Railway Response Railway • 1 day ago
Status changed to Solved noahd • about 9 hours ago