呼唤停电
Outage严重事件
- investigating
出入境电话目前遇到问题。 工程组了解情况,正在调查中.
- investigating
我们仍然遇到问题 进出呼叫。 我们正在和我们的提供商密切合作,尽快恢复服务,一旦了解更多情况,我们将分享最新消息.
- monitoring
出入呼叫部分恢复,但有些用户可能仍然遇到问题。 继续监控客流量,服务全面恢复后将共享更新.
- resolved
出入境呼叫全面恢复.
自动翻译自官方事件更新。
35 Openphone incidents · 2025年11月 — official updates, affected components, duration and resolution details.
出入境电话目前遇到问题。 工程组了解情况,正在调查中.
我们仍然遇到问题 进出呼叫。 我们正在和我们的提供商密切合作,尽快恢复服务,一旦了解更多情况,我们将分享最新消息.
出入呼叫部分恢复,但有些用户可能仍然遇到问题。 继续监控客流量,服务全面恢复后将共享更新.
出入境呼叫全面恢复.
自动翻译自官方事件更新。
目前我们正面临一个问题,即建立与销售力量数据云的新账户连接。 现有的客户整合工作正在正常进行。 我们的工程和伙伴关系小组已查明造成失败的问题,并正在与销售力量支助小组合作解决这种情况.
现在可以进行新的销售力量连接.
自动翻译自官方事件更新。
Our engineering team is investigating elevated error rates on our platform. We are seeing issues with login and delayed call status.
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.
All systems are continuing to operate as expected.
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.
A fix has been deployed and call activity delays should be fully resolved shortly.
Call events are fully operational
We are investigating increased client error rates sending outbound MMS messages on the platform.
The engineering team have identified the system causing delivery errors and have implemented a remediation while we investigate root cause.
The root cause of the issue has been identified and a permanent fix has been prepared.
We are investigating reports of issues with inbound SMS messaging.
Service has been restored, we are monitoring the situation.
We are continuing to monitor reports of delayed delivery of inbound messages.
All delayed messages have been delivered and systems are performing normally.
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.
Custom file uploads and custom greetings in the call flow are now operational.
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.
Port-in requests and carrier registration submissions are functioning normally.
**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.
**Call recording disclosure** **has been fully restored.** We have confirmed normal operation and consider this incident resolved. Thank you for your patience.
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.
**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.
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.
**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.
** iOS and Android outbound MMS restored** All platforms are now operational
Our monitoring systems have detected a platform degradation. Our Engineering on-call team has responded and are investigating the situation.
The engineering team has identified the cause of the issue and are working to deploy a remediation.
The remediation has been deployed. The team are continuing to monitor the system performance.
All systems and services are operating normally.
We are investigating an issue with our Identity provider that is causing authentication issues and is causing some users to be unexpectedly logged out.
Our infrastructure provider have acknowledged a degradation within their platform and are escalating with their support team.
Performance is recovering; we are continuing to monitor the situation.
This incident has been resolved.
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.
Some inbound messaging may also be impacted.
Messaging is performing normally; the engineering team is continuing to monitor the performance of call activities as they recover.
All systems are operating within expected response times.
This incident has been resolved.
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.
The engineering team has resolved the issue, all activities & notifications should be fully up to date at this time.
This incident has been resolved.
We are investigating reports of forced logouts on our desktop applications.
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.
This incident has been resolved.
We have identified an issue impacting calling. The team is working to prepare a fix.
Calling has been restored; we are monitoring the situation to ensure stability is maintained.
All systems are operating normally. We are declaring the incident resolved.
We have received user reports of phone menus failing. On-call engineers have acknowledged and are investigating the situation.
We have identified the issue, and services should be working as normal again. We will continue to monitor.
All systems continue to operate normally. We declaring the incident resolved.
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.
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.
We are investigating reports of sporadic issues logging in with the Web and Desktop clients.
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.
Service has been updated successfully. We were able to confirm that only members of an Alpha feature cohort were impacted by this bug.
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.
Services have been successfully deployed. Call disruption was minimized. We again apologize for any adverse impact.