Call degradation on Weekly ...

Update timeline

1. investigating Feb 24, 2026, 07:25 PM UTC

   We are seeing calls degraded on Weekly channel. The team is looking into the issue and will share updates here.

2. resolved Feb 25, 2026, 05:50 PM UTC

   Incident report: Impact: A service disruption affected call reliability on the Weekly channel. Some calls ended unexpectedly with worker-not-available or worker-died end reasons. Timeline (all times PT): 8:07 AM - We detected a burst of call failures across the platform. 8:16 AM - Automated monitoring alert fired. We acknowledged and began investigating. 8:42 AM - We scoped the impact across affected accounts. 8:47 AM - The issue self-resolved. We identified the root cause as resource contention in our call processing infrastructure during a traffic spike. 9:18 AM - We completed an initial root cause analysis and identified an underlying bottleneck in our call queue infrastructure. 11:13 AM - A related issue resurfaced due to cascading effects from the earlier contention. We began investigating immediately. 11:25 AM - We published a status page to notify customers. 11:38 AM - We confirmed the root cause as CPU contention between infrastructure components. 11:39 AM - We applied a mitigation. Call queue metrics began recovering. 11:45 AM - We updated the status page with the identified cause and fix. 11:46 AM - Error rates began declining. We continued active monitoring. 1:11 PM - We declared resolution on the status page. ~1:35 PM - A brief secondary spike occurred during an infrastructure resource adjustment. We responded immediately. 3:21 PM - All systems fully stabilized. Action Items Enforce resource limits across processing components and improve infrastructure isolation for critical call processing. Note A full root cause analysis is underway and will be available upon request. We sincerely apologize for the disruption and thank you for your patience.

3. investigating Feb 25, 2026, 05:50 PM UTC

   Incident report: **Impact:** A service disruption affected call reliability on the Weekly channel. Some calls ended unexpectedly with `worker-not-available` or `worker-died` end reasons. **Timeline (all times PT):** - **8:07 AM** - We detected a burst of call failures across the platform. - **8:16 AM** - Automated monitoring alert fired. We acknowledged and began investigating. - **8:42 AM** - We scoped the impact across affected accounts. - **8:47 AM** - The issue self-resolved. We identified the root cause as resource contention in our call processing infrastructure during a traffic spike. - **9:18 AM** - We completed an initial root cause analysis and identified an underlying bottleneck in our call queue infrastructure. - **11:13 AM** - A related issue resurfaced due to cascading effects from the earlier contention. We began investigating immediately. - **11:25 AM** - We published a status page to notify customers. - **11:38 AM** - We confirmed the root cause as CPU contention between infrastructure components. - **11:39 AM** - We applied a mitigation. Call queue metrics began recovering. - **11:45 AM** - We updated the status page with the identified cause and fix. - **11:46 AM** - Error rates began declining. We continued active monitoring. - **1:11 PM** - We declared resolution on the status page. - **~1:35 PM** - A brief secondary spike occurred during an infrastructure resource adjustment. We responded immediately. - **3:21 PM** - All systems fully stabilized. **Action Items** Enforce resource limits across processing components and improve infrastructure isolation for critical call processing. **Note** A full root cause analysis is underway and will be available upon request. We sincerely apologize for the disruption and thank you for your patience.