Hey there! We've found the following might help you get unblocked faster:

• 🧵 Connectivity issue from US West region to MongoDB Atlas despite open IP whitelist

• 🧵 Simple django app chokes with concurrent requests

• 🧵 Increased Network Latency

If you find the answer from one of these, please let us know by solving the thread!

=========================
Container failed to start
=========================
 
Failed to start deployment.
If this error persists, please reach out to the Railway team at https://station.railway.com.

Seeing this trying to redeploy a previously successful deploy.

same

same

++ but I don't see an outage marked on the status page?

Bump. Same issue here

Same in US East

same for europe

same

same

cry

works for me now on us east

Looks like it may be an issue related to a recent incident mentioned in another post (https://station.railway.com/questions/failed-to-start-deployment-a4269225), supposedly the team is investigating it and some users are reporting it working in some regions.

My builds are still hanging and production (us-west-2) is still 408/499ing all public traffic from western US, but not central/eastern US.

Same here, 408s and 499 for me on production builds

+1 on the 408/499ing all public traffic (asia-SE-1)

Railway is broken but their status page shows its all green: https://status.railway.com/

Could you please give some examples of these issues? We had an incident prior https://status.railway.com/cmflvsdnb01081nuxvbbzkoyd, but it should be resolved

https://usevault.app

I'm able to load that just fine? What is the steps to reproduce?

https://usevault.app

All traffic to my frontend service is returning 408. http://new-frontier-demo.up.railway.app/

https://railway.com/project/a41a4ccd-9849-4c35-b6a1-efbed80bea67/service/3dd4887f-5c0f-4943-9698-ff4eeab0e278?environmentId=ebd2d436-eaa8-4ea2-a536-d754646923bd&id=0e8c2671-ce81-4cb5-bd9c-e8d074a2d1a4#http

filter: -@httpStatus:200

– afaict, all public network requests from western US are 408/499ing at the metal edge (via a cloudflare proxied domain). If I VPN into central/eastern US, they succeed as 200s. If I generate a random public domain, all 200s from western US.

We are experiencing this issue as well. It showed up earlier where we were getting 502s, then it was fixed for a brief moment, and now after another deployment it's not working. Check here: https://rounds.so/

hmm I'm seeing 408

Same for me as well. Calls to my fastify backend are all returning as 408s, 499s and we also had 502 earlier as well.

Some requests getting through but intermittent

Okay, I THINK we found an issue. It's for a pretty small portion of applications. We rolled out a fix; could you redeploy and check again?

Thats working now thankyou

Working now, thank you

You're VERY welcome. And here's an incident called for it.

https://status.railway.com/cmfotwolf00gl35cmg21dl2sr

Please note, it was a VERY small subset of traffic, and even occured before this thread was posted. Appreciate the patience.

Builds are still failing. cannot redeploy: ERROR: failed to build: failed to solve: Canceled: context canceled

Managed to redeploy and it is working now for me. Thank you!

Network issues fixed after a redeploy. Deploys are still super flaky.

This issue I believe is back