Have you tried redeploying the services? (Also, check the email inbox associated with your Railway account)

I don't think this is just happening to me, since everything is correct and the day was going smoothly, but the connection started dropping and then quickly coming back.

Dropping in to say that my site is getting a 502 as well

everyhting down for us too

Which region are the services deployed in?

US West (California, USA)

US West

my agent said

This looks like a live Railway platform issue (edge/proxy or networking layer), not something wrong with your individual apps.

The Station thread you linked was posted only minutes ago (around 12:19 AM Brasília time / roughly now in +07). Multiple users (including “shadstoneofficial”) are confirming the same widespread 5xx/502s, with services that were fine earlier suddenly failing. A moderator has already replied asking which regions are affected and suggesting a redeploy + checking the account email.

Official status page (status.railway.com) still shows Fully Operational across regions and components. This is typical for emerging incidents — smaller or rapidly developing problems often don’t appear on the status page immediately (they explicitly note that only significant widespread impact gets listed there).

Most likely cause right now

Railway’s edge proxy / public networking layer is having trouble reaching running containers (classic “Application failed to respond” → 502). This has happened before with:

Edge network / routing problems

Brief control-plane or proxy hiccups

Regional networking blips

Services can still show as “Online” in the dashboard while external traffic gets 502s.

What to do

Watch the Station thread you linked — it’s the fastest real-time signal right now. Reply with your region(s) if you haven’t.

Check status.railway.com periodically (it can lag).

Try a hard redeploy on critical services (dashboard or CLI). This has fixed residual routing issues after previous platform events.

Look at the service Metrics and HTTP logs for any upstream errors or resource spikes, though this currently looks platform-wide rather than app-specific.

If you have custom domains, note any x-railway-fallback: true headers — those point to edge routing problems.

This matches the pattern of previous short-lived edge/proxy incidents. Hang tight and keep an eye on that Station post; the team is usually quick once multiple reports pile up. Let me know your regions or if you see any recovery.

hey guys, I'm getting the same problem with my deployed services in Railway right now, can you share the current status for solution?

This issue has been raised with the Team. (The team is aware of the issue and is resolving this as we speak)

For now, I'd recommend deploying the affected service(s) in other regions. (US East, Asia, EU West are unaffected)

My services are deployed in the US East (Virgina, USA), seems that change to a another region wont't solve the problem :(

Try hard refreshing (Cmd/Ctrl + Shift + R) the browser, or using a different device).

still getting server errors after a hard refresh (bad gateway)

Same problem here. US WEST as well

Can you share the URL?

Incident has been created here: https://status.railway.com/incident/RL8FRJE6

for me it is https://wallet.gfavip.com and can we deploy on multiple locations at once ?

It’s still fluctuating here; I hope they resolve it soon, as my project is a fintech and relies on continuous availability.

Yes, you can add replicas in other regions by navigating to the settings tab of your service.

I don't think it is just for the US west region, US east is having an outage as well

I'd try testing with a VPN. I was able to access my projects deployed in US East from Asia.

Thanks for the info, mind making sure none of the transitive dependent deployments are hosted in US-West by accident?

i did, but still get 502 on https://wallet.gfavip.com and tried in incognito

Worth noting, Railway doesn't reattempt failed requests on other regions. The replica routing is strictly geographical, no failover. You'd need to remove the US-West deployment entirely for the time being if you want to avoid the current incident.

All of my services are deployed in the US East region (doble-cheched already), the service is very intermittent, still getting bad getway errors

Interesting, I'll keep an eye on other reports then, thank you!

Team confirmed that they're not seeing any issues on US-East. Keep in mind that US-West -> US-East communication could still be impacted

Incident is resolved now!

We deserve credit. 🚄