Calling Incident

Update timeline

1. investigating Feb 27, 2026, 06:20 PM UTC

   Status: Investigating Monitoring has detected an abnormally high call failure rate. On-call engineers have acknowledged and are investigating the situation. Affected components Calling (Partial outage)

2. identified Feb 27, 2026, 06:32 PM UTC

   Status: Identified The engineering team identified an issue with one of our service providers and are working to deploy a fix. Affected components Calling (Partial outage)

3. identified Feb 27, 2026, 06:37 PM UTC

   Status: Identified Expanding scope to include impact on messaging Affected components Text Messaging (Partial outage) Calling (Partial outage)

4. identified Feb 27, 2026, 06:40 PM UTC

   Status: Identified Investigating reports of forced session logout as a result of the outage. Affected components Calling (Partial outage) Web App (Degraded performance) Android App (Degraded performance) Text Messaging (Partial outage) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance)

5. monitoring Feb 27, 2026, 06:41 PM UTC

   Status: Monitoring Calling metrics have returned to normal. The engineering team is continuing to monitor the situation. Affected components Text Messaging (Partial outage) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Calling (Partial outage) Web App (Degraded performance) Android App (Degraded performance)

6. resolved Feb 27, 2026, 07:09 PM UTC

   Status: Resolved All systems are operating normally. Affected components Android App (Operational) Text Messaging (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Calling (Operational) Web App (Operational)