24 days ago
Hi Railway team,
We experienced multiple deployment issues across three different Railway accounts on February 11, 2026.
Symptoms observed:
- n8n services failing with Redis connection timeouts:
"connect ETIMEDOUT"
"Cannot connect to Redis"
"Deployment blocked"
- Workflows not executing and staying in loading state
- Chatwoot deployments failing during the healthcheck step with:
"Deployment failed during network process"
"Healthcheck failed"
This happened simultaneously across multiple projects and accounts, without any configuration changes on our side.
Later we saw the incident report about:
- Degraded internal network performance
- Issues affecting deployments
Could you confirm:
1. If this incident was the cause of the Redis timeouts and healthcheck failures
2. Whether any configuration changes are recommended for services using Redis or queue-based architectures
3. If a full redeploy is sufficient or if any cleanup steps are recommended
These environments are used for production conversational assistants, so we want to make sure everything is stable after the incident.
Thanks in advance.
1 Replies
24 days ago
Hey there!
It looks like this was a part of a recent incident we have. I just checked and it should be good to go now. Can you give it a look and let me know what you're seeing?
For anything still stuck you'd need to trigger a restart or redeploy on the service.
Post mortem is here in case you're interested in reading it.
https://blog.railway.com/p/incident-report-february-11-2026
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