got same error too status.orderhero.id

Hey My App is now Down since more than 2h can i expect some answer ?

Same error here

2 H and nobody took some time to reply to me ? do you still have people working for Railway ?

Is this also causing our degrade mongodb perfomance?

We had issues all day and spent a lot of time investigating our queries and code

to see why things where slow.

how can an incident like this drag on almost all day without anybody responding or taking action..

I have notice multiple threads here with people having issues spread out over the entire day.

The amount of incidents in the last weeks is really to much making this service not very reliable, and making me wonder if we made the right choice migrating to railway

The linked incident says EU West (Metal / Amsterdam, Netherlands) but this issue is also in us-west and us-east as well. Almost a hour of degraded performance at this point.

I feel the same way.

We reported this issue throughout the day through multiple channels, including the community and Discord, but it took around 16 hours before we received a meaningful response, and nearly 24 hours before the issue was resolved. (https://station.railway.com/questions/latency-spike-1b5123e7, https://station.railway.com/community/repeated-incidents-host-level-performan-6b11ed93, https://station.railway.com/questions/gradual-increase-in-database-latency-e45411a8)

For an infrastructure provider, that is extremely concerning. It makes me wonder whether the on-call and monitoring systems are working as they should, especially when multiple users were reporting similar symptoms across different threads for most of the day.

We are now seriously considering migrating to AWS. We chose Railway because of the great DX and because we wanted to support the product, but for serious production workloads, the recent reliability issues have been very difficult to justify.

I also can't help but feel that unless a customer is spending $10k+ per month, they are not treated as a production customer. I really hope that is not the case, but that is how it feels from this experience.

I'm really frustrated with Railway in the last few months. The incidents come and go. They have a few weeks without incidents and many weeks with incidents. We just decided to migrate to AWS to avoid being impacted by that many incidents.

In the meantime, it happens again. Please Railway..

Solving this thread as the underlying incident has been resolved. https://status.railway.com/incident/QK1OHYXB