2 months ago
We’ve been experiencing server latency recently. API calls and page responses are taking noticeably longer than before, even under normal traffic.
This issue occurs intermittently throughout the day and is more noticeable during peak hours. No application-level changes were made prior to the issue appearing.
Environment details:
- Platform: Railway
- Service type: Web application (API-based)
- The issue affects both frontend requests and backend API calls
We would like to check:
- Whether there are any server-side performance issues or resource constraints
- If there were recent platform changes, maintenance, or incidents related to latency
- Any recommendations for optimization or configuration adjustments on our side
Please let us know if logs, timestamps, or additional details are needed. We’re happy to provide them.
Thank you.
12 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Railway
Hey there! We've found the following might help you get unblocked faster: - [📚 Production Readiness Checklist](https://docs.railway.com/reference/production-readiness-checklist) If you find the answer from one of these, please let us know by solving the thread!
2 months ago
Thanks for sharing the Production Readiness Checklist.
We’ve reviewed the checklist and verified that there are no obvious configuration, resource, or deployment issues on our side. The service is running continuously (not serverless), and there have been no recent application or configuration changes.
However, we are still experiencing intermittent server latency, including slower API responses and page load times, even under normal traffic conditions.
Could you please help check if there are any platform-side performance issues, resource constraints, or recent changes that might be contributing to this behavior?
We can provide logs, timestamps, or additional details if needed.
Thanks for your help.
2 months ago
Yes i'm also experiencing this, every request has suddenly got a lot slower, to a point where an unauthorized or basic /health check takes 500 ms
I'm on Metal and in Amsterdam just FYI
Somebody from Railway needs to look at this ASAP
2 months ago
I have the same! I thought that it's maybe someting in my project but.. I don't think so.
kriss145
I have the same! I thought that it's maybe someting in my project but.. I don't think so.
2 months ago
It is not, if you are using Cloudflare Proxy, it's routing your requests through Asia, which is super weird, disabling it returns it back to normal latency
2 months ago
I did it right now and.. stil my curl showing me: x-railway-edge: railway/asia-southeast1-eqsg3a
2 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!
2 months ago
The fact that it has been over 12 hours, and you have no ETA while all the requests are being routed through Asia giving crazy latency issues, and you're not flagging it as a P0 incident. Should be a warning to everyone doing anything serious on Railway.
2 months ago
✅ The ticket Asia routing issue for non-Asia traffic has been marked as completed.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
In one on my domains I have now "x-railway-edge: railway/us-east4-eqdc4a" but should be region in Europe.
The domain is in the Cloudflare with proxy. Without proxy I have the problem with SSL also.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting User Response noahd • about 2 months ago
2 months ago
Hey there! Are you able to run this?
https://cf-trace.up.railway.app
Would love to see what it shows. From what I know internally, we have since resolved the root issue so I'm confused if you're still encountering this.
2 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 • about 2 months ago
