We are seeing consistent ~12s latency on all public requests to our Railway service, including /api/health.
puspesh
HOBBYOP

2 months ago

Evidence:

- App startup is clean:

- Deployment ID: 6e0b94af

- Deploy logs show next start and Ready in 100ms

- App code is not slow:

- GET /api/health returns: {"ok":true,"basicMs":0,"dbMs":0,"totalMs":0}

- But browser/devtools shows ~12s total time even for /api/health

- This happens after clean rebuild/redeploy as well

- We changed deployment region and still see the issue

Service details:

- Service: otterly

- Domain: https://otterly-production.up.railway.app

- Deployment ID: 6e0b94af

- Region: US East (Virginia) / Singapore - both tried

- Replica count: 1

Please investigate possible edge/public-network routing or proxy delay before requests reach the container.

Attached / included:

- deploy log screenshot

- devtools screenshot

- response headers including X-Railway-Edge and X-Railway-Request-Id

- /api/health response body

Solved

3 Replies

Status changed to Open Railway 2 months ago


There is currently an ongoing incident: https://status.railway.com/incident/L9HP750V


2 months ago

The incident was resolved.

Attachments


Status changed to Awaiting Railway Response brody 2 months ago


2 months 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 2 months ago


Railway
BOT

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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...