I am opening this new thread to get the attention of the Railway team.

A large number of users have reported the same issue with n8n and Postgres. While some threads seem ignored, I noticed that the Railway team has replied to others. From what I understand (please correct me if I’m wrong), the Railway team believes this is an n8n issue, not a Railway issue, and therefore has left it to community support rather than providing direct help.

Let me explain why I find this approach irresponsible.

n8n is a critical workload for many Railway users. Looking at the official “templates,” n8n has over 70k deployments — ranked #1. In comparison, the second-ranked template has only about 17k deployments. This shows how important n8n is for Railway’s community. If n8n stops working reliably on Railway, many users are at risk of leaving the platform entirely.

As most n8n users know, n8n updates are frequent — but new versions are only applied if the user chooses to redeploy. I, and I believe most users, did not redeploy before these crashes happened. That means nothing changed on our side. This strongly suggests that the crash is not due to an n8n update but something on Railway’s side. Blaming n8n for this incident feels unfair and dismissive.

In my other thread (which is still awaiting an official reply), I pointed out that the timing of the crash matches exactly with an automatic worker update on Railway Metal. That makes the cause on the Railway platform highly suspicious.

You can read more details here:
https://station.railway.com/questions/crashed-suddenly-for-n8n-df4c7ed3

Thank you for taking the time to read this. I truly hope the Railway team looks into this matter and resolves it quickly. I also invite other users who faced the same problem to share their observations in this thread.