Hello,

We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.

You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026

Our deepest apologies for the inconvenience this has caused.

Redeploying didn't work. The n8n service is still in a Crashed state because the database files were corrupted during the platform incident. Since I don't have access to the SQL console or terminal, please manually repair the database so it can initialize.

A collation version mismatch is not data corruption.

Running SQL on user databases is not a service we offer.

I am a paying customer, and my n8n service has been down for too long now. It is currently in a Crashed state.

I read your previous response, but I do not understand how to fix this. My dashboard shows the database is "Online", yet n8n fails to start and gives me errors like "Connection terminated unexpectedly" and "There was an error initializing DB".

I don't have a "Query" tab or a terminal to run any commands, and I am not a database administrator. I simply need the service I pay for to work.

Since this started with a platform incident on your side, I am asking you to please fix whatever is broken in the connection between n8n and Postgres so I can get back to work.

Thank you.

I'm sorry for the frustration this is causing, but our database offerings are unmanaged, which means you are the database administrator and responsible for maintenance, repairs, and recovery. We don't run SQL commands or perform repairs on user databases.

I don’t understand how to restore the service. I have critical data in n8n and Postgres, so I cannot just start from scratch. Can you at least provide specific instructions on how to make my n8n functional again?

I'm sorry, but we're not able to assist with n8n configuration or troubleshooting. n8n is a third-party application, and issues with its database initialization are outside the scope of our support. You may find better assistance through n8n's community forums or their documentation.

The issue is not with n8n configuration. The logs clearly show that the n8n initialization fails only because the Postgres connection is terminated unexpectedly by the database itself. This is a direct result of the WAL corruption (invalid record length) and collation mismatch caused by your platform incident. Sending me to n8n support is unhelpful because they cannot repair corrupted database files on Railway's infrastructure. Please provide a way to fix the database logs so the service can start.

I understand this is frustrating, but we cannot assist further. Our databases are unmanaged - you are responsible for all maintenance and recovery. We do not run SQL commands, repair data, or troubleshoot third-party applications like n8n on your behalf.