Quo incident

Calling Incident

Resolved after 49 minutes, affecting Calling and Text Messaging and 1 more, on February 27, 2026.

monitoring Feb 27, 2026, 06:41 PM UTC

Calling metrics have returned to normal. The engineering team is continuing to monitor the situation.

Started
Feb 27, 2026, 06:20 PM UTC
Resolved
Feb 27, 2026, 07:09 PM UTC
Duration
49m
Detected by Pingoru
Feb 27, 2026, 06:20 PM UTC

Affected components

CallingText MessagingAndroid AppWeb AppMac AppWindows AppIOS App

Update timeline

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

    Monitoring has detected an abnormally high call failure rate. On-call engineers have acknowledged and are investigating the situation.

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

    The engineering team identified an issue with one of our service providers and are working to deploy a fix.

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

    Expanding scope to include impact on messaging

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

    Investigating reports of forced session logout as a result of the outage.

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

    Calling metrics have returned to normal. The engineering team is continuing to monitor the situation.

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

    All systems are operating normally.

Your product runs on more than Quo

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 →