specifically, after 5 second timeouts we are seeing: "failed to forward request to upstream: connection dial timeout" (we are not using nginx or other reverse proxy)

Hi DrMarshall, we're investigating.

Looks like redeploying has cleared the issue.

Thank you for the update. Please let us know if you experience this again.

Experiencing this issue again with a different service.

This is slightly different issue, but there seems to be some networking/configuration issue with Railway. Given that we're having networking issues before and after the major outage yesterday, I think these are related.

Hi, did this just happen in the last 5 minutes?

More like 20-30 minutes? Our most recent deploy was not a clean handover between old and new deployments – two services did not pick up new networking properly. Redeploying seems to have resolved the issue, but it caused an outage during the builds.
Deploy timestamp:

Dec 17, 2024 1:11 P
M pacific

Apologies about that..there was a small network issue in the past 30 mins for a part of a region. I am assuming that affected the clean handover. I wanted to recommend a redeploy but you already did it.

Everything is fine on our end now too.

Thanks for confirmation. Was there also an known issue yesterday (top of thread – a few hours before the bigger outage)?

I really do appreciate the confirmation and defined scope of the issue. This kind of acknowledgement lets me know that I can safely deploy again today and don't need to hunt for any configuration changes that could have caused this.

Yes you can

Not that I know of