24 days ago
MinIO error: Error: connect ETIMEDOUT
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: 'xxxx:xxxx:Xxxxx:xxx',
port: 9000
}
ErrorWithContext:Post "http://bucket.railway.internal:9000/": dial tcp [XXXX:XXX:cde3:0:1000:2e:XXX:XXX]:9000: i/o timeout
%!(EXTRA *errors.errorString=invalid login)
1 Replies
24 days ago
Hello,
We had an incident earlier that caused deployments to go offline while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.
You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026
Our deepest apologies for the inconveniences this has caused.
Status changed to Awaiting User Response Railway • 24 days ago
16 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 16 days ago