Hello team,

I want to share some serious concerns about platform reliability. Recently we experienced a build block, and before that a deployment delay. These incidents keep recurring, and each time there has been no clear status update from your side.

The impact is significant. If we need to ship a hotfix, or if a deployment breaks production and builds are halted on your end, we're left unable to deploy or roll back. That is not acceptable for a platform hosting production workloads. These disruptions block our releases, delay our fixes, and ultimately affect our customers.

What makes it harder is the lack of communication. We haven't received a clear explanation of what happened, why, or what steps you're taking to prevent it from happening again.

Honestly, these repeated incidents have made me question whether Railway is ready for production applications, and we've started evaluating alternatives. Many companies depend on your platform, and that kind of trust depends on consistent uptime. If a provider like AWS went down this often, customers would leave.

I'd appreciate it if you could share:

• A root-cause explanation for the recent incidents
• The measures you're putting in place to prevent recurrence
• How you plan to improve status communication during incidents

We'd prefer to stay on Railway, but we need confidence that releases and rollbacks won't be blocked without warning. Please treat changes that affect production deployments with extra care.

Thanks,

Mohammad Hamdan