a month ago
Hi, my Express backend on Railway (Singapore, Hobby plan) shows ~12s TTFB on every single request including a /health endpoint with zero DB queries.
I added a timing middleware as the very first thing in Express and confirmed Express handles requests in 0ms once it receives them — both log lines appear at the same
Railway timestamp:
01:46:27.159807211Z [2026-04-25T01:46:24.003Z] RECEIVED GET /health
01:46:27.159815646Z health reached
The 12 seconds is entirely in Railway's proxy/ingress layer before the request reaches Node.js.
- Another Railway service I run (fuelscope, Singapore, same plan) responds normally
- Issue persists after deleting and recreating the service
- Same on Railway-generated domain and custom domain - Serverless is disabled
- The only visible difference between my slow service and the fast one: Metal Build Environment is enabled (and cannot be turned off — the toggle reverts immediately)
Environment - TTFB
Local - ~117ms
Render (same code, same DB) - fast
Railway - ~12,000ms
Is Metal Build Environment known to cause networking issues? Could this be a degraded host issue for this specific service?
1 Replies
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
This has now been resolved.
The latency was caused by an issue with our CDN provider Fastly, specifically affecting their KV store in the Asia region. Their incident report: https://www.fastlystatus.com/incident/378503
Apologies for the disruption.
Status changed to Awaiting User Response Railway • 27 days ago
20 days 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 • 20 days ago