Our entire production service just got shut down because we hit the usage limits. I agree we set the limit (and forgot about it) when we started with Railway, but then there were no warning emails or anything that services will be completely shut down, we just got an email that everything is already down.

I have to say this is very unprofessional and a pretty bad solution. Furthermore there's no easy way to restart everything, just by re-deploying each service, one by one, that's a lot of downtime for customers. Needless to say we are paying for this service and there's no issue with payment.

I suggest you implement some warnings around the usage and a clear note that services will be shut down some time in advance. You could also implement some grace period, 5-10% is probably not going to damage anyone. Also some solution of restarting everything is very much needed.

On top of everything, after having to redeploy things manually, one service did not deploy, it just hanged which is another issue I've seen quite a lot with Railway, deployments hang regularly for all kinds of (technical) reasons and then we're out of the service completely.

Please take this a a stark warning for your service and business. I think you're providing a great service, but this kind of inconveniences is what makes us (and probably others) to re-consider our provider.