Apologies for the trouble. We had an incident affecting our Edge Network in US regions with elevated latency and packet loss, which has since been resolved. Please give your project another try, and let us know if the slowness persists. You can see the full timeline here: status.railway.com/incident/TAW34N30

Hi, our services are still experiencing very high latency even after the incident was marked as resolved. Even our lightweight endpoints are taking much longer than usual to respond. Could you please check if there are still any networking or infrastructure issues affecting our deployment? Thank you.

Same here. My project is still very, very slow following the resolution.

same here

Hey! Have you guys redeployed (not restart) your apps? Does changing the deployment region has any effect?

Thanks for the suggestion. No, I hadn’t tried that yet. So I redeployed everything and, honestly, it may have made it worse

Nothing out of the norm. This is a very small personal project that I built for myself and my coworkers. Very few users on it. Mostly just me at any given time. No errors in any of the apps, nothing overwhelmed (if anything, all diagnostics as far as memory usage, disk usage, network, ram, etc are at or below normal). I don't have a domain attached to it at the moment. I'm just using a custom ****.up.railway.com domain.

What's strange is the first page load is very quick. Maybe it's cached but I have my doubts. But then all subsequent requests are extremely slow.

it seems to be related to interconnection between various internal processes and public transit. Just few minutes ago it took over half a second to access a robots.txt file, like 10k tops. Nothing has been quite the same since yesterday my site went down. I'm seeing response times from my db that would have typically been 50ms at 1200ms

My issue still remains unresolved. As suggested, I created a health check endpoint which, for now, simply returns some timing results. Bare minimum db hits. The request takes less than 0.05ms to make it's way through my app but the overall request response takes 5000+ ms. Sometimes longer. This is not an issue with my app. It runs fine locally, 0 errors in my logs. There's still something going on

Can you give more info about what your stack looks like? How many services do you have, what do they do, how does traffic flow between them etc?

Thanks for the suggestions. Curling the base url is quite quick so I'm adding some additional health check endpoints to get more detailed timing. My stack is django, Postgres, redis, celery, celery-beat, htmx. 5 services; my app, redis, Postgres, celery, and celery-beat. Curling my base url was nearly instant.

After adding the new endpoints, pushing the update, and clearing my cache (again) my app seems to be back to normal. I'm not sure what the issue was