- Detected by Pingoru
- Sep 17, 2026, 06:19 PM UTC
- Resolved
- Sep 17, 2026, 06:19 PM UTC
- Duration
- —
Affected: Text Messaging
Timeline · 3 updates
-
identified Sep 17, 2026, 05:05 PM UTC
Status: Identified Disruption to Sona (AI agent) sending SMS messages Sona is currently unable to send SMS messages. This affects text messages sent by Sona during calls and SMS responses to new leads through Sona for lead capture. Regular SMS messaging is not impacted. This disruption is limited to messages sent by Sona. Our team is actively working to resolve the issue. We’ll share updates as more information becomes available. Affected components Text Messaging (Partial outage)
-
monitoring Sep 17, 2026, 05:48 PM UTC
Status: Monitoring Messaging has been restored for AI agents. Affected components Text Messaging (Operational)
-
resolved Sep 17, 2026, 06:19 PM UTC
Status: Resolved All systems are performing normally. Affected components Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 07:16 PM UTC
- Resolved
- Sep 01, 2026, 07:16 PM UTC
- Duration
- —
Affected: Text Messaging
Timeline · 3 updates
-
investigating Sep 01, 2026, 05:35 PM UTC
Status: Investigating We’re investigating an issue causing some messages to intermittently fail to send. Our team is actively monitoring the situation. We apologize for the disruption and will share another update as soon as more information is available. Affected components Text Messaging (Partial outage)
-
monitoring Sep 01, 2026, 05:53 PM UTC
Status: Monitoring Message delivery is now operating normally, and we haven’t observed any recent failures. We’ll continue monitoring closely to ensure service remains stable. Thank you for your patience while we worked through this issue. Affected components Text Messaging (Operational)
-
resolved Sep 01, 2026, 07:16 PM UTC
Status: Resolved The issue has been resolved and service is back to normal. We apologize for any inconvenience this caused and thank you for your patience. Affected components Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 09:42 PM UTC
- Resolved
- Aug 18, 2026, 09:42 PM UTC
- Duration
- —
Affected: Quo API
Timeline · 3 updates
-
investigating Aug 18, 2026, 08:57 PM UTC
Status: Investigating The Quo Public API and MCP are currently experiencing issues. The engineering team is aware and investigating. Affected components Quo API (Full outage)
-
monitoring Aug 18, 2026, 09:01 PM UTC
Status: Monitoring The Public API and MCP have come back online. Affected components Quo API (Operational)
-
resolved Aug 18, 2026, 09:42 PM UTC
Status: Resolved Public API and MCP are fully stable. Affected components Quo API (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 08:14 PM UTC
- Resolved
- Jul 28, 2026, 08:14 PM UTC
- Duration
- —
Affected: Integrations
Timeline · 2 updates
-
identified Jul 24, 2026, 10:24 PM UTC
Status: Identified We are currently experiencing an issue establishing new account connections to Salesforce Data Cloud. Existing customer integrations are performing normally. Our engineering and partnership teams have identified the issue causing the failure and are working with the Salesforce support team to resolve the situation. Affected components Integrations (Partial outage)
-
resolved Jul 28, 2026, 08:14 PM UTC
Status: Resolved New Salesforce connections can now be made. Affected components Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 08:12 PM UTC
- Resolved
- Jul 27, 2026, 08:12 PM UTC
- Duration
- —
Affected: Calling
Timeline · 4 updates
-
investigating Jul 27, 2026, 04:35 PM UTC
Status: Investigating Inbound and Outbound calling is currently experiencing issues. The engineering team is aware and is investigating. Affected components Calling (Full outage)
-
investigating Jul 27, 2026, 06:46 PM UTC
Status: Investigating We're still experiencing issues with inbound and outbound calling. We're working closely with our provider to restore service as quickly as possible and will share updates as soon as we know more. Affected components Calling (Full outage)
-
monitoring Jul 27, 2026, 07:34 PM UTC
Status: Monitoring Inbound/outbound calling is partially restored, though some users may still experience issues. We're continuing to monitor traffic and will share an update once service is fully restored. Affected components Calling (Full outage)
-
resolved Jul 27, 2026, 08:12 PM UTC
Status: Resolved Inbound and outbound calling has been fully restored. Affected components Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 07:14 PM UTC
- Resolved
- Jul 08, 2026, 07:14 PM UTC
- Duration
- —
Affected: CallingAndroid AppWeb AppMac AppInfrastructure
Timeline · 3 updates
-
investigating Jul 08, 2026, 06:29 PM UTC
Status: Investigating Our engineering team is investigating elevated error rates on our platform. We are seeing issues with login and delayed call status. Affected components Android App (Degraded performance) Mac App (Degraded performance) Calling (Degraded performance) Web App (Degraded performance) Infrastructure (Degraded performance)
-
monitoring Jul 08, 2026, 06:34 PM UTC
Status: Monitoring The engineering team has identified the failing system component and deployed a fix. All platform services are operating normally at this time. We are continuing to monitor performance. Affected components Web App (Operational) Infrastructure (Operational) Android App (Operational) Mac App (Operational) Calling (Operational)
-
resolved Jul 08, 2026, 07:14 PM UTC
Status: Resolved All systems are continuing to operate as expected. Affected components Android App (Operational) Mac App (Operational) Calling (Operational) Web App (Operational) Infrastructure (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 04:00 PM UTC
- Resolved
- Jul 06, 2026, 04:00 PM UTC
- Duration
- —
Affected: CallingVoicemailAndroid AppIOS App
Timeline · 3 updates
-
investigating Jul 06, 2026, 03:03 PM UTC
Status: Investigating We are investigating an issue causing delays to post-call activities, including missed call notifications, call recordings, and voicemails. This issue began at approximately 10:00 AM ET. We are actively working to resolve this and will provide updates as we learn more. Affected components Android App (Degraded performance) Voicemail (Degraded performance) IOS App (Degraded performance) Calling (Degraded performance)
-
monitoring Jul 06, 2026, 03:46 PM UTC
Status: Monitoring A fix has been deployed and call activity delays should be fully resolved shortly. Affected components Android App (Degraded performance) Voicemail (Degraded performance) IOS App (Degraded performance) Calling (Degraded performance)
-
resolved Jul 06, 2026, 04:00 PM UTC
Status: Resolved Call events are fully operational Affected components Android App (Operational) Voicemail (Operational) IOS App (Operational) Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 07:43 PM UTC
- Resolved
- Jun 26, 2026, 07:43 PM UTC
- Duration
- —
Affected: Text Messaging
Timeline · 3 updates
-
investigating Jun 26, 2026, 07:37 PM UTC
Status: Investigating We are investigating increased client error rates sending outbound MMS messages on the platform. Affected components Text Messaging (Degraded performance)
-
identified Jun 26, 2026, 07:40 PM UTC
Status: Identified The engineering team have identified the system causing delivery errors and have implemented a remediation while we investigate root cause. Affected components Text Messaging (Degraded performance)
-
resolved Jun 26, 2026, 07:43 PM UTC
Status: Resolved The root cause of the issue has been identified and a permanent fix has been prepared. Affected components Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 02:41 AM UTC
- Resolved
- Jun 23, 2026, 02:41 AM UTC
- Duration
- —
Affected: Text Messaging
Timeline · 4 updates
-
investigating Jun 22, 2026, 11:07 PM UTC
Status: Investigating We are investigating reports of issues with inbound SMS messaging. Affected components Text Messaging (Partial outage)
-
monitoring Jun 22, 2026, 11:09 PM UTC
Status: Monitoring Service has been restored, we are monitoring the situation. Affected components Text Messaging (Operational)
-
monitoring Jun 22, 2026, 11:55 PM UTC
Status: Monitoring We are continuing to monitor reports of delayed delivery of inbound messages. Affected components Text Messaging (Degraded performance)
-
resolved Jun 23, 2026, 02:41 AM UTC
Status: Resolved All delayed messages have been delivered and systems are performing normally. Affected components Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2026, 12:23 PM UTC
- Resolved
- Jun 20, 2026, 12:23 PM UTC
- Duration
- —
Affected: SupportCallingText MessagingAndroid AppIOS App
Timeline · 5 updates
-
investigating Jun 18, 2026, 06:17 PM UTC
Status: Investigating We are experiencing an outage of our media attachment system. Media attachments in messages may be temporarily unavailable during this time. This may impact the ability to send attachments on outgoing messages, and the visibility of attachments in message history. Affected components Text Messaging (Partial outage)
-
investigating Jun 18, 2026, 11:44 PM UTC
Status: Investigating Inbound calls with custom greetings encounter errors We've identified an issue affecting inbound calls for phone numbers using custom greetings. Callers will hear an error message if your call flow includes an custom audio greeting, phone menu greeting, or custom voicemail. We're actively working on a resolution and will update this page once service is restored. Workaround: To continue receiving calls, create a temporary call flow: https://support.quo.com/core-concepts/administration/call-flows/temp-call-flows#temporary-call-flows that routes directly to a "ring users" step: set your flow to Incoming Call → Ring Users. Our system default voicemail is currently operational, and can be used as a fallback Inbound Porting Requests are also erroring. Affected components Text Messaging (Partial outage) Support (Partial outage) Calling (Degraded performance)
-
investigating Jun 19, 2026, 02:54 PM UTC
Status: Investigating Call Recording Disclosure These features are functioning normally. Inbound Calls with Custom Greetings These features are functioning normally. Affected components Text Messaging (Partial outage) Support (Partial outage) Calling (Degraded performance)
-
identified Jun 20, 2026, 02:38 AM UTC
Status: Identified Restored on web and desktop apps Outgoing MMS attachments are now functioning normally on web and desktop apps. Temporarily unavailable on Android and iOS Resolution for outbound MMS is in progress for Android and iOS. We are working towards a resolution and will update the status page once service is restored. Affected components Android App (Degraded performance) Text Messaging (Degraded performance) IOS App (Degraded performance) Support (Operational) Calling (Operational)
-
resolved Jun 20, 2026, 12:23 PM UTC
Status: Resolved iOS and Android outbound MMS restored All platforms are now operational Affected components IOS App (Operational) Support (Operational) Calling (Operational) Android App (Operational) Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2026, 03:07 AM UTC
- Resolved
- Jun 20, 2026, 03:07 AM UTC
- Duration
- —
Affected: VoicemailWeb AppMac App
Timeline · 2 updates
-
identified Jun 19, 2026, 05:28 PM UTC
Status: Identified Custom file uploads and in-app greeting recordings are temporarily unavailable for call flow greetings. You can still add a custom greeting using the text-to-speech option in the meantime. We are working toward a resolution and will update this page once service is restored. Affected components Web App (Degraded performance) Voicemail (Degraded performance) Mac App (Degraded performance)
-
resolved Jun 20, 2026, 03:07 AM UTC
Status: Resolved Custom file uploads and custom greetings in the call flow are now operational. Affected components Voicemail (Operational) Mac App (Operational) Web App (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2026, 02:52 AM UTC
- Resolved
- Jun 20, 2026, 02:52 AM UTC
- Duration
- —
Affected: SupportWeb AppMac AppWindows App
Timeline · 2 updates
-
identified Jun 19, 2026, 05:08 PM UTC
Status: Identified Some customers may experience issues submitting port-in requests and carrier registration submissions. Both in-app and form-based submissions are affected. We are working toward a resolution and will update this page once service is restored. Affected components Windows App (Degraded performance) Web App (Degraded performance) Mac App (Degraded performance) Support (Degraded performance)
-
resolved Jun 20, 2026, 02:52 AM UTC
Status: Resolved Port-in requests and carrier registration submissions are functioning normally. Affected components Mac App (Operational) Support (Operational) Windows App (Operational) Web App (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 01:00 PM UTC
- Resolved
- Jun 19, 2026, 01:00 PM UTC
- Duration
- —
Affected: Calling
Timeline · 2 updates
-
identified Jun 18, 2026, 07:45 PM UTC
Status: Identified Inbound and outbound calls are operational. However, call recording disclosure notifications are temporarily unavailable. In the meantime, please ensure you're manually disclosing call recording to comply with applicable laws. Affected components Calling (Degraded performance)
-
resolved Jun 19, 2026, 01:00 PM UTC
Status: Resolved Call recording disclosure has been fully restored. We have confirmed normal operation and consider this incident resolved. Thank you for your patience. Affected components Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 04:12 PM UTC
- Resolved
- Jun 04, 2026, 04:12 PM UTC
- Duration
- —
Affected: IntegrationsCallingVoicemailText MessagingAndroid AppWeb AppMac AppWindows AppInfrastructureIOS AppQuo API
Timeline · 4 updates
-
investigating Jun 04, 2026, 03:26 PM UTC
Status: Investigating Our monitoring systems have detected a platform degradation. Our Engineering on-call team has responded and are investigating the situation. Affected components Integrations (Partial outage) Text Messaging (Partial outage) Voicemail (Partial outage) IOS App (Partial outage) Windows App (Partial outage) Quo API (Partial outage) Android App (Partial outage) Mac App (Partial outage) Calling (Partial outage) Web App (Partial outage) Infrastructure (Partial outage)
-
identified Jun 04, 2026, 03:40 PM UTC
Status: Identified The engineering team has identified the cause of the issue and are working to deploy a remediation. Affected components Android App (Partial outage) Text Messaging (Partial outage) Mac App (Partial outage) IOS App (Partial outage) Calling (Partial outage) Web App (Partial outage) Integrations (Partial outage) Quo API (Partial outage) Voicemail (Partial outage) Windows App (Partial outage) Infrastructure (Partial outage)
-
monitoring Jun 04, 2026, 03:58 PM UTC
Status: Monitoring The remediation has been deployed. The team are continuing to monitor the system performance. Affected components Voicemail (Operational) Mac App (Operational) IOS App (Operational) Calling (Operational) Infrastructure (Operational) Quo API (Operational) Android App (Operational) Text Messaging (Operational) Windows App (Operational) Web App (Operational) Integrations (Operational)
-
resolved Jun 04, 2026, 04:12 PM UTC
Status: Resolved All systems and services are operating normally. Affected components Android App (Operational) Calling (Operational) Web App (Operational) Infrastructure (Operational) Quo API (Operational) Text Messaging (Operational) Voicemail (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:23 PM UTC
- Resolved
- Jun 01, 2026, 07:23 PM UTC
- Duration
- —
Affected: Mac AppWindows App
Timeline · 3 updates
-
investigating May 20, 2026, 05:22 PM UTC
Status: Investigating We are investigating reports of forced logouts on our desktop applications. Affected components Mac App (Degraded performance) Windows App (Degraded performance)
-
monitoring May 20, 2026, 11:46 PM UTC
Status: Monitoring Our service provider has identified and resolved an issue with their platform. We are seeing a dramatic improvement in error rate. The engineering team is continuing to monitor the situation. Affected components Mac App (Operational) Windows App (Operational)
-
resolved Jun 01, 2026, 07:23 PM UTC
Status: Resolved This incident has been resolved. Affected components Mac App (Operational) Windows App (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:23 PM UTC
- Resolved
- Jun 01, 2026, 07:23 PM UTC
- Duration
- —
Affected: Android AppWeb AppMac AppWindows AppInfrastructureIOS App
Timeline · 4 updates
-
investigating Jun 01, 2026, 06:29 PM UTC
Status: Investigating We are investigating an issue with our Identity provider that is causing authentication issues and is causing some users to be unexpectedly logged out. Affected components Android App (Degraded performance) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) Infrastructure (Partial outage)
-
identified Jun 01, 2026, 06:37 PM UTC
Status: Identified Our infrastructure provider have acknowledged a degradation within their platform and are escalating with their support team. Affected components Android App (Degraded performance) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) Infrastructure (Partial outage)
-
monitoring Jun 01, 2026, 06:55 PM UTC
Status: Monitoring Performance is recovering; we are continuing to monitor the situation. Affected components Android App (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational) Infrastructure (Degraded performance)
-
resolved Jun 01, 2026, 07:23 PM UTC
Status: Resolved This incident has been resolved. Affected components Infrastructure (Operational) Android App (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:08 PM UTC
- Resolved
- Jun 01, 2026, 07:08 PM UTC
- Duration
- —
Affected: Text MessagingAndroid AppWeb AppMac AppWindows AppIOS AppQuo API
Timeline · 5 updates
-
identified May 26, 2026, 04:27 PM UTC
Status: Identified We are experiencing a slowdown in the processing of Call Events. Inbound and outbound calls are completing successfully but the logging and post-processing of the call events are currently delayed and some activities may be missing. The engineering team has responded and are preparing a fix. Affected components Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) OpenPhone API (Degraded performance) Android App (Degraded performance)
-
identified May 26, 2026, 05:09 PM UTC
Status: Identified Some inbound messaging may also be impacted. Affected components Text Messaging (Partial outage) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) OpenPhone API (Degraded performance) Android App (Degraded performance)
-
monitoring May 26, 2026, 06:20 PM UTC
Status: Monitoring Messaging is performing normally; the engineering team is continuing to monitor the performance of call activities as they recover. Affected components Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) OpenPhone API (Degraded performance) Android App (Degraded performance) Text Messaging (Operational)
-
monitoring May 26, 2026, 09:20 PM UTC
Status: Monitoring All systems are operating within expected response times. Affected components Quo API (Operational) Android App (Operational) Text Messaging (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational)
-
resolved Jun 01, 2026, 07:08 PM UTC
Status: Resolved This incident has been resolved. Affected components Quo API (Operational) Android App (Operational) Text Messaging (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:07 PM UTC
- Resolved
- Jun 01, 2026, 07:07 PM UTC
- Duration
- —
Affected: Text MessagingInfrastructure
Timeline · 3 updates
-
investigating May 21, 2026, 04:03 PM UTC
Status: Investigating We are currently experiencing a degradation in call activities. Some call activities will be missing or will be inaccurate during this time. The engineering team is investigating. Affected components Text Messaging (Degraded performance) Infrastructure (Degraded performance)
-
monitoring May 21, 2026, 04:36 PM UTC
Status: Monitoring The engineering team has resolved the issue, all activities & notifications should be fully up to date at this time. Affected components Text Messaging (Operational) Infrastructure (Operational)
-
resolved Jun 01, 2026, 07:07 PM UTC
Status: Resolved This incident has been resolved. Affected components Text Messaging (Operational) Infrastructure (Operational)
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 07:30 PM UTC
- Resolved
- May 19, 2026, 07:30 PM UTC
- Duration
- —
Affected: Calling
Timeline · 3 updates
-
identified May 19, 2026, 02:38 PM UTC
Status: Identified We have identified an issue impacting calling. The team is working to prepare a fix. Affected components Calling (Degraded performance)
-
monitoring May 19, 2026, 03:30 PM UTC
Status: Monitoring Calling has been restored; we are monitoring the situation to ensure stability is maintained. Affected components Calling (Operational)
-
resolved May 19, 2026, 07:30 PM UTC
Status: Resolved All systems are operating normally. We are declaring the incident resolved. Affected components Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 02:04 PM UTC
- Resolved
- May 15, 2026, 02:04 PM UTC
- Duration
- —
Affected: Calling
Timeline · 3 updates
-
investigating May 14, 2026, 02:14 PM UTC
Status: Investigating We have received user reports of phone menus failing. On-call engineers have acknowledged and are investigating the situation. Affected components Calling (Degraded performance)
-
monitoring May 14, 2026, 04:01 PM UTC
Status: Monitoring We have identified the issue, and services should be working as normal again. We will continue to monitor. Affected components Calling (Degraded performance)
-
resolved May 15, 2026, 02:04 PM UTC
Status: Resolved All systems continue to operate normally. We declaring the incident resolved. Affected components Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 03:23 PM UTC
- Resolved
- Apr 22, 2026, 03:23 PM UTC
- Duration
- —
Affected: Text Messaging
Timeline · 2 updates
-
investigating Apr 22, 2026, 01:50 PM UTC
Status: Investigating We’re currently experiencing an issue that may prevent messages from sending. Our team is investigating and working to restore normal service as quickly as possible. We’ll share an update soon. Affected components Text Messaging (Partial outage)
-
resolved Apr 22, 2026, 03:23 PM UTC
Status: Resolved The 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. Affected components Text Messaging (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 03:31 PM UTC
- Resolved
- Apr 20, 2026, 03:31 PM UTC
- Duration
- —
Affected: Web AppMac AppWindows App
Timeline · 3 updates
-
investigating Apr 20, 2026, 02:46 PM UTC
Status: Investigating We are investigating reports of sporadic issues logging in with the Web and Desktop clients. Affected components Mac App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance)
-
identified Apr 20, 2026, 03:13 PM UTC
Status: Identified The engineering teem has identified the root cause of the issue. They are preparing a release to address the defect and will release it once it has been tested and validated. Affected components Web App (Degraded performance) Mac App (Degraded performance) Windows App (Degraded performance)
-
resolved Apr 20, 2026, 03:31 PM UTC
Status: Resolved Service has been updated successfully. We were able to confirm that only members of an Alpha feature cohort were impacted by this bug. Affected components Mac App (Operational) Windows App (Operational) Web App (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 18, 2026, 01:21 AM UTC
- Resolved
- Apr 18, 2026, 01:21 AM UTC
- Duration
- —
Affected: CallingVoicemailText MessagingAndroid AppWeb AppMac AppWindows AppIOS App
Timeline · 2 updates
-
investigating Apr 18, 2026, 12:37 AM UTC
Status: Investigating We have experienced an urgent stability incident requiring an immediate deploy of system services. Unfortunately this deploy will cause a disruption of active calling sessions and interrupt inbound and outbound calling. Our engineering team are working to execute this deployment in the least disruptive way possible. We apologize for the impact. Affected components Text Messaging (Full outage) Voicemail (Full outage) Mac App (Partial outage) IOS App (Partial outage) Windows App (Partial outage) Calling (Full outage) Web App (Partial outage) Android App (Partial outage)
-
resolved Apr 18, 2026, 01:21 AM UTC
Status: Resolved Services have been successfully deployed. Call disruption was minimized. We again apologize for any adverse impact. Affected components Web App (Operational) Android App (Operational) Text Messaging (Operational) Voicemail (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Calling (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 09:07 PM UTC
- Resolved
- Apr 15, 2026, 09:07 PM UTC
- Duration
- —
Affected: Android AppWeb AppMac AppWindows AppIOS AppQuo API
Timeline · 3 updates
-
identified Apr 15, 2026, 08:56 PM UTC
Status: Identified We are experiencing a service degradation impacting core application features. The engineering team has identified the cause and is working to prepare a fix. Core calling features are operating normally. Features impacted include: Contacts Search Workflow AI Services Affected components Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) OpenPhone API (Degraded performance) Android App (Degraded performance)
-
resolved Apr 15, 2026, 09:07 PM UTC
Status: Resolved The issue has been resolved, all impacted service areas are back to fully operational. Affected components Android App (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational) OpenPhone API (Operational)
-
resolved Apr 15, 2026, 09:07 PM UTC
Status: Resolved The issue has been resolved, all impacted service areas are back to fully operational. Affected components Windows App (Operational) Web App (Operational) Quo API (Operational) Android App (Operational) Mac App (Operational) IOS App (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 10:36 PM UTC
- Resolved
- Mar 13, 2026, 10:36 PM UTC
- Duration
- —
Affected: Android AppWeb AppMac AppWindows AppIOS App
Timeline · 3 updates
-
investigating Mar 13, 2026, 09:43 PM UTC
Status: Investigating We're currently experiencing a system-wide slowdown affecting search results. The team has started investigating the issue. Affected components Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance) Android App (Degraded performance)
-
identified Mar 13, 2026, 09:53 PM UTC
Status: Identified Our team has identified the root cause and is working on deploying a solution. We sincerely apologize for the inconvenience and appreciate your continued patience. Affected components Android App (Degraded performance) Mac App (Degraded performance) IOS App (Degraded performance) Windows App (Degraded performance) Web App (Degraded performance)
-
resolved Mar 13, 2026, 10:36 PM UTC
Status: Resolved We'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. Affected components Android App (Operational) Mac App (Operational) IOS App (Operational) Windows App (Operational) Web App (Operational)
Read the full incident report →