Worth noting about the same time my disk usage shot up a gig, unknown reason, no interaction with the environment at that time - and, if you're feeling spicy to help, the fact the DB chews up 900MB of ram all of the time is marginally annoying, and this issue seems to be specific to Railway

=========================

Container failed to start

=========================

An unknown error occurred.

If this error persists, please reach out to the Railway team at https://station.railway.com.

hello,

terribly sorry about this, I've raised this to the team and will let you know a solution as soon as I know.

Issue resolved, thx

Following up here.

We've identified that a component in our deployment infrastructure became unresponsive, which caused your deployment to hang before eventually failing. We sincerely apologize for the frustration this caused.

We've now implemented additional monitoring to detect this type of issue immediately, so our team can resolve it much faster if it happens again.

Thanks for your patience, and please don't hesitate to reach out again if you have any other questions or concerns.

Also, I wanted to clarify our support response times to set proper expectations going forward.

As a Pro user, our standard response time is within 24 hours, which we maintained for your ticket. For customers who need faster response times (within 1 hour for critical issues), we offer that level of support through our Enterprise plan.

If faster response times would be valuable for your use case, I'd be happy to connect you with our sales team to discuss Enterprise options.

Thanks again for your understanding!

A) I didnt cause this issue, your system decided to start the process and it then hung, this is entirely on you

hiding behind a 24 hour response time is pretty piss poor

B) You need to fix this 24 hour response time nonesense if you're hosting infrastructure

if something critical is down, respond to tickets, fix it.

I'm out of railway

good luck

A) I didnt cause this issue, your system decided to start the process and it then hung, this is entirely on you
hiding behind a 24 hour response time is pretty piss poor

100% on us. We've rolled out a fix

B) You need to fix this 24 hour response time nonesense if you're hosting infrastructure
if something critical is down, respond to tickets, fix it.

24 hours is the SLA for Pro. Happy to do higher SLA on Enterprise agreements

I'm out of railway
good luck

Sorry to see you go

Same thing happened to me :(

https://share.catlab.gg/img/pjDFhs.png

https://share.catlab.gg/img/AbmCmA.png

hey, can you create your own help thread?