Railway - Internal network failure – Incident details

We are resolving the incident while continuing to root-cause the issue.

The recent incidents with network update propagation were related to internal connectivity issues between our api servers and the backing database. We upgraded our connection pooler to pull in some patches to address this, but that did not have the desired effect.

We've reverted this change and scaled up the pooling layer and are continuing to monitor the situation.

We’re investigating errors with network initializations on builds, and have paused new deployments for hobby and trial users.

We're seeing failures on builds and deployments again, and are investigating the cause of the incident.

We are still monitoring the fix. If your deploy failed or your service is getting network errors, please redeploy it from the dashboard.

Our fix has deployed and we are re-enabling builds and deploys. We will keep monitoring as new builds go out.

We implemented a fix and are currently monitoring the result.

Certain parts of the dashboard may fail to load when accessing affected components - mainly the architecture tab of a project