Make sure the port your application is listening to is the same port your URL is mapped to.

We have not modified the source of the application or the Railway deployment configuration.

I just received an email from Railway.

A server running your service has experienced a hardware failure. We are actively working to restore it. No action is needed on your part — your service will automatically resume once the issue is resolved.

The root cause was the hardware failure.

Does a redeploy help?

Already tried that, it did not helped.

If there is a hardware failure why is it not reflecting the Railway status page? 🤔

https://status.railway.com/

That's an outage only specific to the server that host your app, not global outage

hi, does your issue resolve? I received the same hardware failure email since last 1 hr, mentioned to resolve within 10mins. Affecting my database container. Now my system 503 unable to connect to db. Still not resolve even after redeploy.

It's isolated to that specific server hosting that specific instance. Statuses are only created if it's widespread across the platform/product.

Whenever an application or server starts returning errors, the first thing most of us do is check the application logs. If nothing obvious shows up there, we expand our investigation to the third-party services the application depends on. In many cases, those services provide a status page where we can quickly confirm whether they're experiencing an incident.

In Railway's case, however, the status page doesn't appear to report server-specific hardware failures. More importantly, Railway also didn't display any hardware failure alert or banner in the dashboard itself. We only received an email notification about 16 minutes later.

So my main point is: Railway should display hardware failure incidents directly in the dashboard, rather than relying solely on delayed email notifications.