I started using Railway in March, and at some point had my Django app on Metal out east, and the Postgres DB in the GCP, maybe it was out west. The lag was significant with this, so I manually stood up a new metal DB out east, and it was AMAZING.

Everything was good up until about 1+ weeks ago, when I started seeing a lot of slow responses. (My app is a single user app so there's not a lot of load on it.)

About 2 weeks ago I noticed you'd done the metal migration even though it was already on there, but I imagine it was missing something else or you had a good reason to do that. This was fine, I didn't even notice it when it happened, and I don't think the slowdown started right at that time.

I've been monitoring the forum and seeing some other DB/SQL performance issues and wanted to let you know that if you did something over the past day to mitigate this generally, it seems to be working! For me, anyway, and maybe I'm speaking up too soon.

Funny since I spent a good chunk of time yesterday adding a loading spinner. Last night I'd only see it briefly and this morning not at all. Figures! But it is a "nice to have", so no complaints.

Railway is great! I'm loving it for my hobby project. Keep up the great work!