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

an hour 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

$10 Bounty

2 Replies

Status changed to Open Railway about 1 hour ago


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


The incident was resolved.

Attachments


Welcome!

Sign in to your Railway account to join the conversation.

Loading...