Failed to start deployment

reece

PROOP

7 months ago

railway is down

Solved

20 Replies

reece

PROOP

7 months ago

c0e3b2af-8f03-40c2-85e3-30ac2bf30ceb

noahd

EMPLOYEE

7 months ago

Investigating

reece

PROOP

7 months ago

@mzh are you also deploying to us-east?

Anonymous

PRO

7 months ago

crowe

PRO

7 months ago

Hi, I'm facing the same issue, one of my containers failed to build and deploy

crowe

PRO

7 months ago

oh nvm it is up now

reece

PROOP

7 months ago

nice it's fixed

noahd

EMPLOYEE

7 months ago

Team is working on it

noahd

EMPLOYEE

7 months ago

oh lmao

reece

PROOP

7 months ago

i eagerly await the postmortem to hear how the railway team is able to deal with outages in minutes

reece

PROOP

7 months ago

they know something we don't

reece

PROOP

7 months ago

actually no I don't even want to think about how long the runbook must be in order to achieve this

brody

EMPLOYEE

7 months ago

GitHub revert 😎

cristflores

PRO

7 months ago

I had the same issue, but its already working again, for now!!

cristflores

I had the same issue, but its already working again, for now!!

cristflores

PRO

7 months ago

forget it, is down again

cristflores

forget it, is down again

jack

PRO

7 months ago

Just tried it a few times and didn't have any issues. (us-east)

lightshire

PRO

7 months ago

408 issues across

lightshire

408 issues across

cristflores

PRO

7 months ago

Yes, x1000

trustcore-system

PRO

7 months ago

Am trying to deploy my frontend and backend but it keeps on crushing what could be the matter?

noahd

EMPLOYEE

7 months ago

Status changed to Solved noahd • 7 months ago

Welcome!