Quo (formerly OpenPhone) outage on Jun 18, 2026

What happened

Quo (formerly OpenPhone) reported a partial outage starting Jun 18, 2026, 18:17 UTC. It was marked resolved at Jun 20, 2026, 12:23 UTC.

• The incident lasted 1d 18h from first report to resolution.
• It was the 3rd longest of 7 significant outages Quo (formerly OpenPhone) reported in the 12 months up to it.
• Quo (formerly OpenPhone) had reported 3 other partial or major outages in the 90 days before it.
• 6 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Quo (formerly OpenPhone)

** iOS and Android outbound MMS restored** All platforms are now operational

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.

• Partial outageScalewayJun 18, 2026, 08:26 UTC

  [Generative APIs] - [fr-par] Dedicated deployment creation failures

• Major outageGrafana CloudJun 18, 2026, 11:25 UTC

  Degraded k6 cloud UI performance

• Major outageCloudTalkJun 18, 2026, 14:16 UTC

  Partial System Outage

• Partial outageGrafana CloudJun 18, 2026, 15:18 UTC

  Potential Issues Loading Grafana for Users in India

• Partial outageABC Fitness (Ignite / Evo)Jun 18, 2026, 15:27 UTC

  ABC Fitness has detected an issue with Trainerize and has now been resolved

• Partial outagePrisma PostgresJun 18, 2026, 17:53 UTC

  Errors provisioning Prisma Postgres databases

Quo (formerly OpenPhone)'s overall reliability

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