Your usage page shows $3.22 for this cycle against a $10 compute hard limit, so your services should not have been stopped at that level. As an immediate fix, raising or temporarily removing your hard limit at railway.com/workspace/usage will automatically redeploy your stopped services; if any don't restart on their own, you can manually redeploy from the 3-dot menu on the most recent deployment.

Thank you, but this does not fully address the issue.

Why was my workspace considered to have reached the $10 limit when the dashboard shows only $3.22?

You were right, and this was a bug on our side. The counter our limit enforcement checks had drifted out of sync with your real usage, so it read about $10 when you'd actually used $3.22. That's why your services were stopped even though the dashboard showed you well under the limit.

We've reset the counter, so enforcement won't trip again at your current usage. Your services won't restart on their own though. Please redeploy each one from the 3-dot menu on the latest deployment, or toggle your usage limit off and back on to redeploy them automatically.

Sorry for the trouble, and thanks for flagging it.

Railway Team

Thanks for investigating and explaining what happened. Appreciate the support and transparency!

Best wishes <3