Live  /  Quo  /  Incident

Quo: Elevated calling errors within the APAC region

Quo · quo.comMinor incidentResolved2026-10-17 18:06 UTC
Public — what happened

Summary

Quo reported a minor incident involving a higher-than-normal rate of calling errors in the APAC region, beginning at 17:29 UTC on 2026-10-17. The company said its regional provider was reporting that only some phone numbers were affected. Quo marked the incident resolved at 18:06 UTC the same day, and its posted text did not describe a fix or a cause beyond the provider's report.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Quo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Quo: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Quo report →

More from Quo

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Quo status & history page.

Related: Quo status & history. SquidGrid is not affiliated with Quo.