a month ago
Our self-hosted n8n instance on Railway is completely down due to the active storage incident in the SG3 region (incident #28BGWVE8).
Issues we are experiencing:
- n8n returns {"code":503,"message":"Database is not ready!"} on all requests
- Primary service deploy logs show repeated "Database connection timed out" and "timeout exceeded when trying to connect" errors
- Postgres service itself shows as Active/Online but is unreachable from our n8n services
Our setup:
- Primary service (n8n)
- Worker service (n8n worker)
- Postgres (SG3 region, with cow-volume attached storage)
- Redis
The database connection timeouts started around the same time as the SG3 storage incident (June 5, 08:44 UTC).
Please prioritize resolution of the SG3 storage incident as it is causing complete downtime for our production n8n instance.
5 Replies
a month ago
We're aware of storage degradation affecting the SG3 region and our infrastructure team is actively working on resolution. Your n8n project's services in this region are impacted, and connectivity should restore once the underlying storage issue is resolved - no action needed on your side.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We're aware of storage degradation affecting the SG3 region and our infrastructure team is actively working on resolution. Your n8n project's services in this region are impacted, and connectivity should restore once the underlying storage issue is resolved - no action needed on your side.
a month ago
Until when will it be resolved?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We don't have a specific ETA for resolution at this time. Our infrastructure team is actively working on it, and your services should recover automatically once the underlying storage issue is addressed.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
May I confirm if this is related to the Host reboot notice earlier?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Yes, host reboot notices are part of how we handle infrastructure events. Railway initiates redeployments when a host requires updates or experiences a fault, as described in our deployment docs. A storage incident in the same region can trigger host-level recovery actions, so the two are likely connected. Your services should recover automatically once the underlying issue is resolved.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved Anonymous • 29 days ago