CloudTalk incident

Issues with inbound calls to groups

Resolved on February 19, 2026, affecting Global (Mobile Application) and Global (Analytics) and 1 more.

resolved Feb 19, 2026, 08:40 AM UTC

On 19 February 2026 at 09:40 CET, we experienced an incident where a portion of inbound calls to call groups did not reach available agents and were not connected. Impact: Some inbound group calls were not successfully routed to online agents during the incident window. Other call types were not affected. Root cause: The issue was caused by a recent configuration change in our call routing layer. The change modified the routing logic responsible for delivering inbound calls to the system component that connects calls to agents, which resulted in certain calls not being properly forwarded. Resolution: The configuration change was reverted, restoring the previous routing logic. Call routing returned to normal operation, and we have confirmed stable behavior since resolution. Preventive measures: We are reviewing our change validation procedures to strengthen safeguards around routing-layer updates and reduce the risk of similar incidents in the future. We apologize for the disruption and appreciate your patience.

Started
Feb 19, 2026, 08:40 AM UTC
Resolved
Feb 19, 2026, 08:40 AM UTC
Duration
–
Detected by Pingoru
Feb 19, 2026, 08:40 AM UTC

Affected components

Global (Mobile Application)Global (Analytics)Global (Call recording)Global (CloudTalk Dialer)Global (Integrations)Global (Desktop Application)Global (CloudTalk Dashboard)Global (Messaging)Global (VoiceAgents)Australia (Outbound calls)

Update timeline

  1. resolved Feb 19, 2026, 08:40 AM UTC

    On 19 February 2026 at 09:40 CET, we experienced an incident where a portion of inbound calls to call groups did not reach available agents and were not connected. Impact: Some inbound group calls were not successfully routed to online agents during the incident window. Other call types were not affected. Root cause: The issue was caused by a recent configuration change in our call routing layer. The change modified the routing logic responsible for delivering inbound calls to the system component that connects calls to agents, which resulted in certain calls not being properly forwarded. Resolution: The configuration change was reverted, restoring the previous routing logic. Call routing returned to normal operation, and we have confirmed stable behavior since resolution. Preventive measures: We are reviewing our change validation procedures to strengthen safeguards around routing-layer updates and reduce the risk of similar incidents in the future. We apologize for the disruption and appreciate your patience.

Your product runs on more than CloudTalk

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →