Unable to Deploy
matthew-cameron1
PROOP

a year ago

I see the incidents in other posts have been marked as resolved but all my services failed to deploy with: ListDomainsForServiceInstance INTERNAL: list failed

I don't have the option to try a redeploy either.

Closed

18 Replies

a year ago

Can you screenshot this? Never seen it before.


matthew-cameron1
PROOP

a year ago

This is whats in the build logs of all my services haha

1427805588963856466


a year ago

Woof


a year ago

@Error Would you be able to escalate this too? This cannot be a user issue


a year ago

Do you have the metal builder enabled?


a year ago

Investigating a bit first


matthew-cameron1
PROOP

a year ago

They just started building again


matthew-cameron1
PROOP

a year ago

Perhaps propagating


a year ago

Can you link that deployment.


a year ago

Odd. Possibly remnants but definitely not natural.


a year ago

Ah Brody here <:salute:1137099685417451530>


a year ago

I'm always around


matthew-cameron1
PROOP

a year ago

Can confirm



matthew-cameron1
PROOP

a year ago

2 of my 3 services seem to have suddenly redeployed successfully lol


matthew-cameron1
PROOP

a year ago

But they were down for the last few hours, saw the status so left until it said resolved and they were still down


a year ago

Yes, that deployment went out during the incident.


version3034
HOBBY

a year ago

So for deployments, is everything being run off railways own bare metal servers ?

Or is it a mixture of legacy Google servers or what?

There honestly is not a centralized place to get up to date information on, what kind of servers are running. Where these data centers are ? Who they are with…

I am sure it’s partially by design. People expect to upload their docker and it just run. But naturally customers have questions, especially those needing specific requirements for HIPPA or Sox compliance etc .


Welcome!

Sign in to your Railway account to join the conversation.

Loading...