a month ago
Hi Railway team,
We experienced Redis connection timeouts across three different Railway accounts on February 11, 2026.
All n8n services started failing with:
"connect ETIMEDOUT"
"Cannot connect to Redis"
"Deployment blocked"
This happened simultaneously across multiple projects without any configuration changes.
We later saw the incident report about internal network degradation affecting deployments.
Could you confirm if this incident was the cause of the Redis timeouts and blocked deployments?
Also, is there any recommended configuration for n8n queue mode to avoid this in the future?
Thanks in advance.
1 Replies
a month ago
Hi there, could you please try restarting your services? We had an incident affecting private networking which may have caused the timeouts - this is now resolved. Please try connecting again, and let us know if the issue persists. We have also written a postmortem for it here: https://blog.railway.com/p/incident-report-february-11-2026
For n8n with Redis on private networking, our documentation recommends adding ?family=0 to your Redis URL for dual-stack DNS resolution - see this guide.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago