7 months ago
We recently moved our service from Google Cloud (Cloud Run + Cloud SQL Postgres) to Railway. Everything went pretty smooth, however we are seeing a lot of high latency requests, which appear to be caused by the database. Even when I repeatedly run a simple query against the DB I can reproduce the issue. It usually takes a couple hundred milliseconds, but occasionally it will take several seconds. I'm running out of ideas to troubleshoot this. Do you have any further guidance or ideas how to tackle this?
15 Replies
7 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
7 months ago
Hello,
Thank you for reporting this, we can confirm we are seeing the same issue, we will be looking into mitigations and the bot will relay the status of the ticket back to this thread.
Best,
Brody
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
Any news on this? Our app is performing time critical payment authorizations and our users are largely affected by this.
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
Apologies about this. Are you able to switch from "Metal (New)" region to a region without it (i.e. EU West)?
This will incur some downtime as your database will be migrated over.
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
Yes, I can do this tonight. It would probably be best to move all connected services then?
Status changed to Awaiting Railway Response Railway • 7 months ago
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
I had to make a cut and move back to the "legacy" infrastructure in the middle of the day because the problems suddenly got much worse. The app is way more responsive now and the latency spikes are gone. That was quite a painful experience and made the metal infrastructure appear very immature. Can I somehow follow progress on this topic?
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
Hello,
We are really sorry about the inconvenience here, we have two infrastructure engineers staffed work on resolving the underlying issue.
As for following the status, the bot will relay whenever the ticket status changes to this thread.
Best,
Brody
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
✅ The internal ticket Increased latency between metal<->metal private networking has been marked as completed.
7 months ago
Hello,
Just wanted to follow back up here and confirm if your latency issues have been solved?
7 months ago
I migrated back to metal after the issue was resolved and everything is working as expected now 
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
Amazing, really glad to hear!
Going to close this one out but if you have any more questions, please send them our way!
Status changed to Awaiting User Response Railway • 7 months ago
Status changed to Solved chandrika • 7 months ago
7 months ago
We're back in latency spike land since ~3 hours 
Status changed to Awaiting Railway Response Railway • 7 months ago
Status changed to Awaiting User Response Railway • 7 months ago
6 months ago
❌ The internal ticket Increased latency between metal<->metal private networking has been marked as canceled.
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago