Quo incident

Degraded Performance of Call Events

Resolved after 6 days 2 hours, affecting Text Messaging and Android App and 1 more, on May 26, 2026.

monitoring May 26, 2026, 09:20 PM UTC

All systems are operating within expected response times.

Started
May 26, 2026, 04:27 PM UTC
Resolved
Jun 01, 2026, 07:08 PM UTC
Duration
6d 2h
Detected by Pingoru
May 26, 2026, 04:27 PM UTC

Affected components

Text MessagingAndroid AppWeb AppMac AppWindows AppIOS AppQuo API

Update timeline

  1. identified May 26, 2026, 04:27 PM UTC

    We are experiencing a slowdown in the processing of Call Events. Inbound and outbound calls are completing successfully but the logging and post-processing of the call events are currently delayed and some activities may be missing. The engineering team has responded and are preparing a fix.

  2. identified May 26, 2026, 05:09 PM UTC

    Some inbound messaging may also be impacted.

  3. monitoring May 26, 2026, 06:20 PM UTC

    Messaging is performing normally; the engineering team is continuing to monitor the performance of call activities as they recover.

  4. monitoring May 26, 2026, 09:20 PM UTC

    All systems are operating within expected response times.

  5. resolved Jun 01, 2026, 07:08 PM UTC

    This incident has been resolved.

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 →