We've looked into this from our side and haven't found anything on the Railway platform that explains what you're seeing, so working it out means digging into your specific setup.

That's exactly what the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public and the thread closes.

We’re on multi-region, so Railway Static Outbound IP isn’t an option.

We worked around it by adding retries when we see network timeouts like:

{"kind":"network","errorMessage":"Error","errorCode":"ETIMEDOUT","causeCode":"ETIMEDOUT"}

Users may wait an extra 1–2 seconds occasionally. Looking at the logs, every ETIMEDOUT only needed one retry — we haven’t seen three ETIMEDOUTs in a row on the same request.