Thanks for your hard work, quick recovery and clear comms throughout. The price of success!

Thank you for your hard work and relatively quick resolution of the problem. I confess I was a little worried because I recently chose you as my main server, haha.

Our service is still down, server kept on crashing.

Hey Khaime, could you please open a support thread with us regarding any issues you're still seeing so we can get you sorted? The incident is resolved so there shouldn't be any remaining impact from it, so this is likely unrelated

As a new user here, I build and deploy apps very frequently—even for the tiniest fixes. So the way your team fixed things so quickly yesterday is something I really appreciate and welcome!

Thank you so much for the kind words, and welcome! As Angelo mentioned we know you rely on us and as such, we are working hard to improve resiliency across the platform

https://station.railway.com/questions/postgre-sql-proxy-broken-econnreset-893b2cff
This is the link to the detail description of the issue we are currently facing

Muchas gracias por avisar, estaremos pendiente.

Hi Chandrika, Urgent Here！

As our team data is currently inaccessible, this issue has become quite urgent for us. Could someone from the Trust & Safety team please help review our appeal or guide us on the next step?

At the moment, all connections to the db are failing. Hoping we can expedite this a little faster.

Hi! thanks for the update and the hard work you guys are doing in this platform, it's really incredible and i use it on a daily basis for my job.
unluckily i'm experiencing issues as well, despite being outside the maintenance window you mentioned. i'm deploying one service, which usually takes 2 minutes at most, but it has been already 40 minutes and it's still "building"
any thoughts on that? you think everything will still be solved by 3pm?

All my deployments are now failing. I'm not sure how you manage to mess everything up so badly. Cloudflare pages deploys in less than 10 seconds but railway takes over 5 minutes and still fails.

During the ongoing Queued Actions Upgrade maintenance (ref:

https://status.railway.com/cmml4u6k102xtf03oixzrplw8), the internal

GraphQL endpoint

https://backboard.railway.com/graphql/internal?q=networking appears to be

returning errors.

This is impacting our ability to view and modify networking

configurations (e.g. custom domains, TCP proxies, service networking

settings) through the dashboard.

The maintenance notice mentioned potential delays for "platform

configuration updates," but didn't mention networking/GraphQL API

availability being affected. Could you confirm whether this is an

expected side effect of the upgrade, and provide an ETA for restoration?

I'm having the same issue - custom domains failing, not appearing but still being visible, cloudflare SSLs not firing.....will all this be resolved once maintenance is over or is this a new issue?

We’ve been running Transfrly on Railway and it’s been incredibly smooth for us.

The platform fits perfectly with how Transfrly is designed. Even if infrastructure pauses or maintenance windows happen, it doesn’t disrupt our philosophy — it simply reflects the underlying hosting layer doing its job or the platform improving itself.

Transfrly is built differently:

ANONYMOUS • STATELESS • EPHEMERAL

We started with a simple question:

What if a conversation only existed while it was happening?

No archives.

No digital attic.

No “just in case.”

Transfrly doesn’t store a single byte of your conversations. Which means there’s nothing to guard, nothing to harvest, and nothing to leak.

Railway’s simplicity and reliability make it a natural home for that kind of architecture.

— Transfrly

Transfrly.com

when i deploy it - only 2 min and crashed again - is this because the maintainence ?

could you open your own support thread?

From where ?

Update: we have completed the maintenance with no downtime on any of our systems. I'm sure Angelo will have a nicer explanation than I do, but this should buy us significant headroom for future growth.

Thank you all for sticking with us throughout the recent outages. Our team will continue to work hard on improving platform reliability over the coming weeks.

Until now, my experience with you has been wonderful.
I wish you success, and I hope you will speed up finding the solution.

Okay, after action. It looks like the upgrade is helping us handle the load quite well.

We should see less hang ups when it comes to staged deployments and builds.

For the person that is reporting a slow build of 5 minutes, unfortunately, that is the default experience- that said, we are working on making deployments instant. More to announce on that front when we have something to show for everyone here.