Hi Railway team,

I'm getting recurring, brief 502 Bad Gateway outages on a production service. Each lasts ~8 minutes, they recur every few days with no correlation to my traffic or deploys, and they self-recover.

During each window my container is fully healthy — same instance, no crash, no restart, event loop steady at ~5ms, memory flat — and it keeps serving the requests it manages to receive. Your edge HTTP logs show the failures as connection dial timeout (5000ms, retried 3×) from the edge to the instance, with detail: "Retried single replica", then 502. So the edge can't open a TCP connection to a healthy instance for several minutes, then can again. This looks like an edge↔host networking fault, not my application.

To preempt the usual first questions: the service runs normally outside these windows, so port binding and health-check config are correct — this is purely intermittent edge-to-instance reachability, not a startup, port, or health-check problem.

This matches a prior report your team attributed to a transient regional network issue (station thread: https://station.railway.com/questions/cloudflare-502s-bad-gateway-9d905d08). Since mine recurs every few days, I'd like to understand whether it's a persistent problem with my host/region placement rather than a one-off.

Most recent occurrence: 2026-06-08 21:51:56 → 21:59:50 UTC (~8 min). Edge region observed: asia-southeast1-eqsg3a. I currently run a single replica.

I can provide the project/service/deployment/instance IDs and specific failing request IDs privately, or you can read them off my account.

Questions:

1. Can you inspect the host/networking for my instance during that window and confirm what caused the edge to be unable to dial it?

2. Is this a persistent issue with the host/region my workload is placed on — and can the workload be moved?

3. Beyond adding a second replica for failover, is there anything on my side that reduces exposure?

Thanks,

Jared