a month ago
We experienced a significant outage today affecting multiple services across two of our projects (zonic and n8n-ramp-flows). Starting around 14:50 UTC on February 11, 2026, numerous services received unexpected SIGTERM signals and restarted, some repeatedly at 5-minute intervals.
Affected services:
• Project: n8n-ramp-flows (ID: 7b886366-ffac-424d-a974-c429d0db35c5) • Redis (zonic-n8n-redis) - SIGTERM at 14:50:12 UTC
• Worker instances - SIGTERM at 14:50:17 UTC, followed by cascading failures due to lost Redis connections
• Project: zonic (ID: 05dadfa4-d886-46c4-bbc7-37201b2b4b16) • WhatsBailey-2, 3, 5, 6 - All received SIGTERM starting 14:50 UTC
• Some instances restarted repeatedly every ~5 minutes
Impact:
• n8n workers crashed and couldn't recover (10s Redis reconnect timeout exceeded)
• WhatsApp connectivity interrupted for customers
• Campaign/bulk sender functionality unavailable
Questions:
1. Was there a Railway infrastructure event or maintenance around 14:50 UTC today?
2. Why did multiple services across different projects receive SIGTERM signals simultaneously?
3. What can we do to prevent cascading failures when Redis restarts?
We'd appreciate any insight into the root cause. Happy to provide additional logs or deployment IDs.
Thanks,
Jan
Zonic Team
7 Replies
a month ago
You were probably in lucky 3%
https://blog.railway.com/p/incident-report-february-11-2026
a month ago
Even after postmordem was posted, we are still experiencing crashes of database services on some instances.
a month ago
Hello,
We had an incident earlier that caused some running workloads to be unexpectedly terminated 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 inconvenience this has caused.
Status changed to Awaiting User Response Railway • 29 days ago
brody
Hello,We had an incident earlier that caused some running workloads to be unexpectedly terminated 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-2026Our deepest apologies for the inconvenience this has caused.
a month ago
This issue is still occurring on our services. Even after the “resolved” check, we have had 5 databases go offline. Please advise
Status changed to Awaiting Railway Response Railway • 29 days ago
thelamedia
This issue is still occurring on our services. Even after the “resolved” check, we have had 5 databases go offline. Please advise
a month ago
In some cases, you may need to redeploy your services.
Status changed to Awaiting User Response Railway • 29 days ago
brody
In some cases, you may need to redeploy your services.
a month ago
We have redeployed all services and some continue to go offline
Status changed to Awaiting Railway Response Railway • 29 days ago
thelamedia
We have redeployed all services and some continue to go offline
a month ago
Please open your own thread so we can look into it for you.
Status changed to Awaiting User Response Railway • 29 days ago
Status changed to Solved yaneq • 28 days ago