2 months ago
We're experiencing another issue that we'd like your assistance with.
This morning, we noticed that when our application loads, it needs to retrieve data from our backend API hosted on Railway.
API URL: https://newapi-production-7ab0.up.railway.app
When testing individual API endpoints using Postman, most requests respond very quickly and perform as expected.
However, when the application is accessed through a browser, multiple API requests are sent simultaneously to load the page. In this scenario, many of the requests become extremely slow, causing the page to hang and, in some cases, preventing data from being returned altogether.
Could you help us determine whether there are any platform limitations, networking issues, concurrency limits, resource constraints, or configuration settings on Railway that could be contributing to this behavior?
If possible, please test or review the service from your end using the URL above. We're happy to provide additional details, logs, or performance metrics if needed.
Thank you.
2 Replies
2 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
I'd try removing all of the requests from the webpage in a staging environment and see how the page responds, then add them back one by one.
2 months ago
Quick update on the latency you reported. We've rolled out a series of edge changes over the past week, tied to our new CDN, that should address the intermittent TTFB spikes.
Are you still seeing slow requests? If so, send a few X-Railway-Request-Id values from recent slow ones with rough timestamps, and we'll trace them through the edge to confirm whether anything's still off on our side.
Railway Team