Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Openphone outage history

    44 recorded Openphone incidents since November 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Elevated calling errors within the APAC region

    Started October 17, 2026 at 5:29 PM UTC · 37m

    IssuesMinor incident
    1. October 17, 2026 at 5:29 PM UTCmonitoring

      We are are seeing elevated errors within the APAC region. The regional provider is reporting a subset of phone numbers are impacted.

    2. October 17, 2026 at 6:06 PM UTCresolved

      The regional issue has been resolved.

    Delayed contact and task updates

    Started October 15, 2026 at 6:05 PM UTC · 10d 20h

    Pending
    1. October 15, 2026 at 6:05 PM UTCinvestigating

      We're investigating delays in syncing some updates across our apps. Some customers may see changes to contacts and tasks take longer than expected to appear on their other devices. Our team is working to restore timely updates. We apologize for the disruption and will share another update as we learn more.

    2. October 26, 2026 at 2:41 PM UTCresolved

      All systems have been operating within acceptable latencies. We are resolving this incident.

    Delayed notifications

    Started October 14, 2026 at 6:13 PM UTC · 1h 11m

    IssuesMinor incident
    1. October 14, 2026 at 6:13 PM UTCinvestigating

      We’re investigating delays in notifications for incoming text messages. Some customers may receive notifications later than expected across our apps. Our team is working to restore this. We apologize for the disruption and will share another update as we learn more.

    2. October 14, 2026 at 6:41 PM UTCmonitoring

      We've applied a fix, and notifications for new messages, calls, and voicemails are arriving on time again. We're continuing to monitor closely to make sure everything stays stable.

    3. October 14, 2026 at 7:24 PM UTCresolved

      Notifications 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.

    Calling Outage

    Started October 1, 2026 at 5:15 PM UTC · 53m

    OutageCritical incident
    1. October 1, 2026 at 5:15 PM UTCinvestigating

      We are investigating an incident impacting inbound and outbound calling. Our on-call engineers have responded.

    2. October 1, 2026 at 5:19 PM UTCidentified

      Our engineers have identified an issue with a workflow management system and are working to deploy a fix.

    3. October 1, 2026 at 5:56 PM UTCidentified

      We've identified the cause and are still working on a fix. Inbound and outbound calling remain affected. We'll post another update within 30 minutes

    4. October 1, 2026 at 5:56 PM UTCmonitoring

      Calling is recovering. We are continuing to monitor system performance.

    5. October 1, 2026 at 6:08 PM UTCresolved

      Inbound and outbound calling is fully restored.

    Degraded performance in Tasks

    Started September 27, 2026 at 12:08 AM UTC · 2h 5m

    IssuesMinor incident
    1. September 27, 2026 at 12:08 AM UTCinvestigating

      We are aware with performance issues with Tasks and are investigating. Some actions may be delayed. Task History may be affected.

    2. September 27, 2026 at 1:11 AM UTCidentified

      We are aware with performance issues with Tasks and are investigating. Some actions may be delayed. Task History may be affected. We have identified the issue and are working on a fix.

    3. September 27, 2026 at 2:03 AM UTCmonitoring

      A fix for Tasks performance issues has been deployed and we are monitoring. Some actions may still be delayed and Task History may be affected while things settle. We will confirm once we have verified everything is back to normal.

    4. September 27, 2026 at 2:13 AM UTCresolved

      All systems are performing normally.

    Analytics are not displaying in the app

    Started September 17, 2026 at 6:11 PM UTC · 6d 18h

    Pending
    1. September 17, 2026 at 6:11 PM UTCidentified

      We've identified an issue causing the analytics in the app to not appear. The team is working on rolling out a fix.

    2. September 17, 2026 at 7:06 PM UTCidentified

      The team is continuing work on deploying the identified fix.

    3. September 17, 2026 at 8:37 PM UTCidentified

      The team is continuing to deploy updated infrastructure to resolve the issue.

    4. September 17, 2026 at 10:15 PM UTCidentified

      The fix has been applied and we are in the process of syncing data. An update will be posted with expected timeframes for full reporting availability.

    5. September 17, 2026 at 11:12 PM UTCidentified

      The pipeline that pushes data into our analytics engine was misdeployed, but it has now been restored, and data is beginning to stream back in. We still need to resync the data, so users may not see their current analytics immediately while we backfill. Once the resync is complete, users will see their data as normal. In the meantime, up‑to‑date data is available via the CSV download as reporting is restored.

    6. September 18, 2026 at 12:58 PM UTCidentified

      The data sync continuing and the team is monitoring, and will post an all-clear when it has completed.

    7. September 18, 2026 at 8:37 PM UTCidentified

      The data is continuing to replicate in to the database backing analytics. This is going to continue in to the weekend, we appreciate your patience. Up-to-date metrics are available via the CSV export functionality in the meantime.

    8. September 20, 2026 at 2:43 PM UTCmonitoring

      The data synchronization has finished and we are monitoring the analytics dashboards.

    9. September 21, 2026 at 5:14 PM UTCmonitoring

      New data is properly accounted for on the Analytics dashboards. We are currently backfilling data for Thursday and Friday from last week.

    10. September 22, 2026 at 7:01 PM UTCmonitoring

      The final data sync to backfill missing data will be happening this evening.

    11. September 23, 2026 at 4:41 PM UTCmonitoring

      The backfill is continuing. An update will be posted when it is complete.

    12. September 24, 2026 at 12:58 PM UTCresolved

      The data has finished backfilling and analytics is complete.

    Disruption to Sona (AI Agent) Messaging

    Started September 17, 2026 at 5:05 PM UTC · 1h 14m

    OutageMajor incident
    1. September 17, 2026 at 5:05 PM UTCidentified

      **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.

    2. September 17, 2026 at 5:48 PM UTCmonitoring

      Messaging has been restored for AI agents.

    3. September 17, 2026 at 6:19 PM UTCresolved

      All systems are performing normally.

    Intermittent issues sending messages

    Started September 1, 2026 at 5:35 PM UTC · 1h 40m

    OutageMajor incident
    1. September 1, 2026 at 5:35 PM UTCinvestigating

      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.⁠

    2. September 1, 2026 at 5:53 PM UTCmonitoring

      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.⁠

    3. September 1, 2026 at 7:16 PM UTCresolved

      The issue has been resolved and service is back to normal. We apologize for any inconvenience this caused and thank you for your patience.

    Public API and MCP experiencing issues

    Started August 18, 2026 at 8:57 PM UTC · 46m

    OutageCritical incident
    1. August 18, 2026 at 8:57 PM UTCinvestigating

      The Quo Public API and MCP are currently experiencing issues. The engineering team is aware and investigating.

    2. August 18, 2026 at 9:01 PM UTCmonitoring

      The Public API and MCP have come back online.

    3. August 18, 2026 at 9:42 PM UTCresolved

      Public API and MCP are fully stable.

    Calling Outage

    Started July 27, 2026 at 4:35 PM UTC · 3h 38m

    OutageCritical incident
    1. July 27, 2026 at 4:35 PM UTCinvestigating

      Inbound and Outbound calling is currently experiencing issues. The engineering team is aware and is investigating.

    2. July 27, 2026 at 6:46 PM UTCinvestigating

      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.

    3. July 27, 2026 at 7:34 PM UTCmonitoring

      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.

    4. July 27, 2026 at 8:12 PM UTCresolved

      Inbound and outbound calling has been fully restored.

    Salesforce Account Linking

    Started July 24, 2026 at 10:24 PM UTC · 3d 21h

    OutageMajor incident
    1. July 24, 2026 at 10:24 PM UTCidentified

      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.

    2. July 29, 2026 at 12:14 AM UTCresolved

      New Salesforce connections can now be made.

    Calling Experience

    Started July 8, 2026 at 6:29 PM UTC · 45m

    IssuesMinor incident
    1. July 8, 2026 at 6:29 PM UTCinvestigating

      Our engineering team is investigating elevated error rates on our platform. We are seeing issues with login and delayed call status.

    2. July 8, 2026 at 6:34 PM UTCmonitoring

      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.

    3. July 8, 2026 at 7:14 PM UTCresolved

      All systems are continuing to operate as expected.

    Post-call activities are delayed

    Started July 6, 2026 at 3:03 PM UTC · 57m

    IssuesMinor incident
    1. July 6, 2026 at 3:03 PM UTCinvestigating

      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.

    2. July 6, 2026 at 3:46 PM UTCmonitoring

      A fix has been deployed and call activity delays should be fully resolved shortly.

    3. July 6, 2026 at 6:36 PM UTCresolved

      Call events are fully operational

    Outbound MMS messages failing

    Started June 26, 2026 at 7:37 PM UTC · 7m

    IssuesMinor incident
    1. June 26, 2026 at 7:37 PM UTCinvestigating

      We are investigating increased client error rates sending outbound MMS messages on the platform.

    2. June 26, 2026 at 7:40 PM UTCidentified

      The engineering team have identified the system causing delivery errors and have implemented a remediation while we investigate root cause.

    3. June 26, 2026 at 7:43 PM UTCresolved

      The root cause of the issue has been identified and a permanent fix has been prepared.

    Inbound SMS issues

    Started June 22, 2026 at 11:07 PM UTC · 3h 34m

    OutageMajor incident
    1. June 22, 2026 at 11:07 PM UTCinvestigating

      We are investigating reports of issues with inbound SMS messaging.

    2. June 22, 2026 at 11:09 PM UTCmonitoring

      Service has been restored, we are monitoring the situation.

    3. June 22, 2026 at 11:55 PM UTCmonitoring

      We are continuing to monitor reports of delayed delivery of inbound messages.

    4. June 23, 2026 at 2:41 AM UTCresolved

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

    Call flow greetings: file uploads and in-app recordings are temporarily unavailable

    Started June 19, 2026 at 5:28 PM UTC · 9h 39m

    IssuesMinor incident
    1. June 19, 2026 at 5:28 PM UTCidentified

      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.

    2. June 20, 2026 at 3:07 AM UTCresolved

      Custom file uploads and custom greetings in the call flow are now operational.

    Porting request and carrier registration interruptions

    Started June 19, 2026 at 5:08 PM UTC · 9h 44m

    IssuesMinor incident
    1. June 19, 2026 at 5:08 PM UTCidentified

      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.

    2. June 20, 2026 at 2:52 AM UTCresolved

      Port-in requests and carrier registration submissions are functioning normally.

    Call recording disclosure notification unavailable

    Started June 18, 2026 at 7:45 PM UTC · 17h 15m

    IssuesMinor incident
    1. June 18, 2026 at 7:45 PM UTCidentified

      **Call recording disclosure notification unavailable** Call recording disclosure notifications are temporarily unavailable and will result in an error message being played. To stay compliant, manually inform callers that their call may be recorded. You can also temporarily disable call recording notifications in your settings to prevent any disruption. We're actively working on a resolution and will update this page once service is restored.

    2. June 19, 2026 at 3:40 PM UTCresolved

      **Call recording disclosure** **has been fully restored.** We have confirmed normal operation and consider this incident resolved. Thank you for your patience.

    Outgoing MMS temporarily unavailable

    Started June 18, 2026 at 6:17 PM UTC · 1d 18h

    OutageMajor incident
    1. June 18, 2026 at 6:17 PM UTCinvestigating

      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.

    2. June 18, 2026 at 11:44 PM UTCinvestigating

      **MMS attachment outage** Outgoing MMS is temporarily unavailable. Messages with attachments will fail to send. Remove attachments before sending messages to ensure delivery. **Port-in requests and carrier registration submissions unavailable** We're experiencing issues with submitting new port-in requests and carrier registration submissions. Both in-app and form-based submissions are temporarily affected. We're actively investigating these issues and will update this page as we learn more.

    3. June 19, 2026 at 2:54 PM UTCinvestigating

      Outgoing MMS remains unavailable. Messages with attachments will continue to fail to send. Remove attachments before sending to ensure delivery. We are actively working on a resolution and will update this page as soon as service is restored.

    4. June 20, 2026 at 2:38 AM UTCidentified

      **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.

    5. June 20, 2026 at 12:23 PM UTCresolved

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

    Investigating reports of a system outage

    Started June 4, 2026 at 3:26 PM UTC · 46m

    OutageMajor incident
    1. June 4, 2026 at 3:26 PM UTCinvestigating

      Our monitoring systems have detected a platform degradation. Our Engineering on-call team has responded and are investigating the situation.

    2. June 4, 2026 at 3:40 PM UTCidentified

      The engineering team has identified the cause of the issue and are working to deploy a remediation.

    3. June 4, 2026 at 3:58 PM UTCmonitoring

      The remediation has been deployed. The team are continuing to monitor the system performance.

    4. June 4, 2026 at 4:12 PM UTCresolved

      All systems and services are operating normally.