Hey all,

At times, if we notice an issue with a host and we aren't able to move the workload in time, we will report the error via email in case we expect to redeploy your service. This should all be within your plan's SLA.

Why is it still down?? It's been 10+ hours.

Hey there,

I am looking at your Service here (natural-peace / breedingo_auth_service) and it's currently running and active.

Looking at your logs, it looks like it's been active this entire time, so I'm not sure what you mean by it being down. Hopefully everything is good to go!

I had a very similar experience.

I received the same “Temporary Service Disruption” notice, and my service stayed unavailable for much longer than the stated 30 minutes (in my case, more than 10 hours).
During that time, the public URL of my web service was showing a Railway error page, so visitors could see that the service was unavailable.

What fixed it for me was manually restarting the service from the Railway dashboard (using “Restart” on the service).
After doing that, the error page at the public URL disappeared immediately and the service started working again.

So even if the service appears “running” in the dashboard or logs, it may be stuck in a bad state after maintenance.
If you haven’t tried it yet, I recommend doing a manual restart once.

Hope this helps.