Hi there, the fix is still being rolled out and we're monitoring it. We had started seeing some recovery but it is taking time to stabalise across the fleet. We'll share a more detailed postmortem on our status page post-incident. We're very sorry for the inconvenience!

Thank you, hang in there

Just an update: the fleet seems to be starting to stabilize now

my postgres container is not responding at all.
database?environmentId=4d95fe2d-710c-404b-aaad-48a582f205f0

Although at 12:00 Railway indicated that there was a widespread improvement, we are still experiencing slow requests and 502 errors. It is 12:22 in Madrid.

https://station.railway.com/questions/mongo-db-storage-down-a6bf869f

We are still seeing a major outage though status page reporting everything is operational.

Hi all, please open and keep to your own threads.

Its been a lengthy downtime and we need to reassure our clients, and looking for some reassurance ourselves. The issue around databases has not been clearly acknowledged and threads remain unreplied to regarding the issue.

Hey! Anyone of you currently still experiencing any issues? We believe this has been fully resolved since a few hours ago (as of this post).

Please let me know if you're still experiencing issues + share a link to your service so I can investigate. Again, apologies for the inconvenience here!

Hi, we wanted to share an update on this.

We published an incident report for December 16, 2025: https://blog.railway.com/p/incident-report-december-16-2025

Once again, we're deeply sorry for the impact this caused. We're actively working to eliminate the class of issues that contributed to this incident and to make the platform more resilient.

Best,

The Railway Team