Quo Outage History
35 incidents recorded over the last 365 days, 35 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Quo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Support Chat Outage Our service provider has returned to normal operations; chat is functioning as expected. | 1h 56m | Resolved |
| Oct 17, 2026 | Elevated calling errors within the APAC regionThe regional issue has been resolved. | 36 min | Resolved |
| Oct 15, 2026 | Delayed contact and task updatesAll systems have been operating within acceptable latencies. We are resolving this incident. | 260h 35m | Resolved |
| Oct 14, 2026 | Delayed notificationsNotifications for new messages, calls, and voicemails have been arriving on time since our fix. We apologize for the disruption and thank you for your patience. | 1h 11m | Resolved |
| Oct 1, 2026 | Calling OutageInbound and outbound calling is fully restored. | 53 min | Resolved |
| Sep 27, 2026 | Degraded performance in TasksAll systems are performing normally. | 2h 4m | Resolved |
| Sep 17, 2026 | Analytics are not displaying in the appThe data has finished backfilling and analytics is complete. | 162h 47m | Resolved |
| Sep 17, 2026 | Disruption to Sona (AI Agent) MessagingAll systems are performing normally. | 1h 13m | Resolved |
| Sep 1, 2026 | Intermittent issues sending messagesThe issue has been resolved and service is back to normal. We apologize for any inconvenience this caused and thank you for your patience. | 1h 40m | Resolved |
| Aug 18, 2026 | Public API and MCP experiencing issuesPublic API and MCP are fully stable. | 45 min | Resolved |
| Jul 27, 2026 | Calling OutageInbound and outbound calling has been fully restored. | 3h 37m | Resolved |
| Jul 24, 2026 | Salesforce Account LinkingNew Salesforce connections can now be made. | 93h 49m | Resolved |
| Jul 8, 2026 | Calling ExperienceAll systems are continuing to operate as expected. | 45 min | Resolved |
| Jul 6, 2026 | Post-call activities are delayedCall events are fully operational | 56 min | Resolved |
| Jun 26, 2026 | Outbound MMS messages failingThe root cause of the issue has been identified and a permanent fix has been prepared. | 6 min | Resolved |
| Jun 22, 2026 | Inbound SMS issuesAll delayed messages have been delivered and systems are performing normally. | 3h 34m | Resolved |
| Jun 19, 2026 | Call flow greetings: file uploads and in-app recordings are temporarily unavailableCustom file uploads and custom greetings in the call flow are now operational. | 9h 39m | Resolved |
| Jun 19, 2026 | Porting request and carrier registration interruptionsPort-in requests and carrier registration submissions are functioning normally. | 9h 44m | Resolved |
| Jun 18, 2026 | Call recording disclosure notification unavailable**Call recording disclosure** **has been fully restored.** We have confirmed normal operation and consider this incident resolved. Thank you for your patience. | 17h 14m | Resolved |
| Jun 18, 2026 | Outgoing MMS temporarily unavailable** iOS and Android outbound MMS restored** All platforms are now operational | 42h 6m | Resolved |
| Jun 4, 2026 | Investigating reports of a system outageAll systems and services are operating normally. | 45 min | Resolved |
| Jun 1, 2026 | Authentication issuesThis incident has been resolved. | 53 min | Resolved |
| May 26, 2026 | Degraded Performance of Call EventsThis incident has been resolved. | 146h 40m | Resolved |
| May 21, 2026 | Application degradationThis incident has been resolved. | 267h 3m | Resolved |
| May 20, 2026 | Application LogoutsThis incident has been resolved. | 290h 1m | Resolved |
| May 19, 2026 | Calling DegradedAll systems are operating normally. We are declaring the incident resolved. | 4h 52m | Resolved |
| May 14, 2026 | Calling Phone Menu IncidentAll systems continue to operate normally. We declaring the incident resolved. | 23h 49m | Resolved |
| Apr 22, 2026 | Message sending issuesThe Engineering team has identified the potential cause and has deployed a fix. We are actively monitoring the situation. We apologize for any impact this has had this morning. | 1h 33m | Resolved |
| Apr 20, 2026 | Web and Desktop Login IssuesService has been updated successfully. We were able to confirm that only members of an Alpha feature cohort were impacted by this bug. | 45 min | Resolved |
| Apr 18, 2026 | Emergency MaintenanceServices have been successfully deployed. Call disruption was minimized. We again apologize for any adverse impact. | 43 min | Resolved |
| Apr 15, 2026 | Services OutageThe issue has been resolved, all impacted service areas are back to fully operational. | 10 min | Resolved |
| Mar 13, 2026 | Search is experiencing slowdownsWe're pleased to inform you that the issue has been resolved and all services are now fully operational. We apologize for any inconvenience this may have caused and thank you for your patience. | 53 min | Resolved |
| Mar 11, 2026 | Conversations issue causing client issuesAll systems have been operating normally, we are resolving this incident. | 1h 41m | Resolved |
| Mar 6, 2026 | Inbound Email IncidentThe incident with our mail service provider has been resolved. Service has been restored. We apologize for any inconvenience. | 29 min | Resolved |
| Feb 27, 2026 | Calling IncidentAll systems are operating normally. | 49 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Quo incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Quo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Quo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Quo outage in this window ran 12d 2h, against a mean recovery of 1d 14h. If you depend on Quo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.