Quo (formerly OpenPhone) outage on Jun 22, 2026

What happened

Quo (formerly OpenPhone) reported a partial outage starting Jun 22, 2026, 23:07 UTC. It was marked resolved at Jun 23, 2026, 02:41 UTC.

• The incident lasted 3h 34m from first report to resolution.
• Quo (formerly OpenPhone) had reported 4 other partial or major outages in the 90 days before it.
• 9 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Quo (formerly OpenPhone)

All delayed messages have been delivered and systems are performing normally.

Read Quo (formerly OpenPhone)'s official incident report ↗

What our independent monitoring saw

Our independent monitoring of Quo (formerly OpenPhone) started after this incident, so this report is based on Quo (formerly OpenPhone)'s status page.

Other outages around the same time

Significant incidents other vendors reported within 12 hours of this one.

• Major outageRemoteJun 22, 2026, 11:11 UTC

  Login unavailable for some users

• Major outageKinstaJun 22, 2026, 11:18 UTC

  MyKinsta dashboard login issues

• Partial outageToastJun 22, 2026, 14:13 UTC

  Toastweb Down

• Major outageGorgiasJun 22, 2026, 14:50 UTC

  Chat are not working properly

• Partial outageLinearJun 22, 2026, 15:27 UTC

  Some customers experiencing issues with Linear loading and syncing

• Partial outageWorkOSJun 22, 2026, 21:36 UTC

  Degraded performance for Directory Provisioning for Authkit

• Partial outageTwilio SegmentJun 22, 2026, 22:14 UTC

  (US West 2) Partial degradation of Linked Audiences, Linked Events, Reverse ETL, and Profile Sync due to external Snowflake Outage

• Major outageOnfido (Entrust)Jun 23, 2026, 02:38 UTC

  QES tasks cannot complete because our provider is encountering issues.

• Major outageWixJun 23, 2026, 09:16 UTC

  RESOLVED: Issues with Stores Product Catalog

Quo (formerly OpenPhone)'s overall reliability

Full Quo (formerly OpenPhone) reliability report and live status → · Most reliable Quo (formerly OpenPhone) alternatives →