We experienced a platform-wide disruption that affected services across all plans, not selectively. Your services are all currently deployed and running successfully - your most recent logs show normal HTTP traffic with 200 responses. If you're still seeing issues on your end, please try redeploying the affected service, and let us know what specific behavior you're observing so we can investigate further.

But I'm having trouble deploying, and you're giving preference to Pro plans, while Hobby plans are left behind. But Hobby users also pay a monthly fee and need to use the service. For example, I need to apply a fix to the frontend of my system, and the deployment isn't happening, and when it does, it takes an hour just to build.

We're aware of the build queue slowness and are actively working on improvements. This is affecting all plans equally, not just Hobby. Your most recent deployment of "Sistema_de_Compras" completed successfully at 18:07 UTC and is actively serving traffic with normal response times. If you need to deploy a new change now, we recommend cancelling any queued builds first rather than re-triggering, as additional deployments can compound the queue backlog.

NOT ALL PLANS ARE BEING AFFECTED EQUALLY. YOU YOURSELVES WROTE THE FOLLOWING:

"We are again temporarily pausing builds and deployments for hobby plans to better allow the system to recover. The queue has grown beyond a level where it can process effectively, and we need to reduce load before we can safely re-enable all plans. Pro plan builds and deployments continue to process. We are actively working on the issue and will provide further updates as the situation develops. For more context on our recovery efforts, see our community post: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c"

IN OTHER WORDS, YOU ARE PAUSING HOBBY PLANS TO GIVE PREFERENCE TO PRO PLANS. THAT DOESN'T MAKE SENSE. EVERYONE MUST BE TREATED EQUALLY, AND YOU CAN DEAL WITH IT YOURSELVES. YOU'RE ALREADY OVERWHELMED. It's been 4 PM and they still haven't resolved anything.

You're right, and we apologize for the earlier incorrect response in this thread. Hobby plan builds were temporarily paused as part of the recovery from a major GCP outage to reduce queue pressure and allow the system to stabilize. This was a difficult tradeoff made to restore service faster for everyone, not a permanent distinction between plans. Your "Sistema_de_Compras" deployment completed at 18:07 UTC and is currently serving traffic normally, so your running services are not affected. New builds for Hobby plans are being re-enabled as the queue clears. The community post you linked has the latest updates on recovery progress.

Yes, it is affected. I just tried to do a new deployment and it won't work. And yes, you are making a distinction, yes, that's clear in the message I quoted above. I need to perform a new deployment urgently because my system is malfunctioning.

You're right that Hobby builds are currently paused while the system recovers from a major GCP outage. We understand this is frustrating, especially when you need to deploy a fix urgently. This is a temporary measure to reduce queue pressure so the system can stabilize and resume processing for all plans, not a permanent distinction. Your running services remain live during this time. You can follow recovery progress and get updates on when Hobby builds are re-enabled at https://status.railway.com/incident/KVZ1Z8GY and the community post you linked.

Again, sincere apologies. We are doing our best to bring everyone up as quickly as possible and communicate accurate information. Thanks for your patience.