Skip to content
Same as "Cloudflare-proxied domain routes to mel1" - second account affected (MRS → mel1)
todayistoday7
OP

an hour ago

Reporting the same issue as this closed thread, from a different account, as requested there:

https://station.railway.com/questions/cloudflare-proxied-domain-routes-to-mel1-f3b47faa

My custom domains panstwamiastagra.com and roomforgames.com (Cloudflare proxy, free plan) show the same pattern:

  • Cloudflare MRS (Marseille) → x-railway-edge: mel1 → 700-1300 ms per request
  • Cloudflare CDG (Paris) → x-railway-edge: cdg1 → ~100 ms
  • Native domain panstwa-miasta-production-030a.up.railway.app → bcn1 → ~100 ms

Example: x-railway-request-id HY84_r8YQvGjvrIQjUJq2g, x-hikari-trace mel1.35qs

My service is a real-time multiplayer game (Socket.IO), so almost all traffic is dynamic and cannot be cached. Every player routed through MRS gets ~1 s extra on every move. Happy to share project/service IDs or run more tests.

Awaiting User Response

1 Reply

Status changed to Awaiting Railway Response Railway • 44 minutes ago


41 minutes ago

This sounds like a routing issue. Could you follow the steps in https://docs.railway.com/networking/troubleshooting/network-diagnostics and send the report here?


Status changed to Awaiting User Response Railway • 41 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...