Live / Quo / Incident
Quo: Delayed notifications
Quo · quo.comMinor incidentResolved2026-10-14 19:24 UTC
Public — what happened
Summary
Quo reported a minor incident on October 14, 2026, beginning at 18:13 UTC, in which alerts for incoming texts were reaching some customers later than they should across its apps. By 18:41 UTC the company said it had put a fix in place and that alerts for new texts, calls and voicemails were showing up promptly again, though it did not say what caused the delays. Quo kept watching the service afterward and marked the incident resolved at 19:24.
Timeline
- Started — 2026-10-14 18:13 UTC
- Investigating — 2026-10-14 18:13 UTC
- Monitoring — 2026-10-14 18:41 UTC
- Resolved — 2026-10-14 19:24 UTC · 1h 11m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.