Openphone 장애 기록

1. 2026년 7월 27일 PM 4:35 UTCinvestigating

   인바운드 및 아웃바운드 호출은 현재 문제가 있습니다. 엔지니어링 팀은 aware이며 투자입니다.

2. 2026년 7월 27일 PM 6:46 UTCinvestigating

   우리는 여전히 인바운드와 아웃바운드 호출 문제를 경험하고있다. 우리는 가능한 한 빨리 서비스를 복원하기 위해 우리의 공급자와 긴밀하게 협력하고 우리가 더 알고 있기 때문에 업데이트를 공유 할 것입니다.

3. 2026년 7월 27일 PM 7:34 UTCmonitoring

   Inbound/outbound 호출은 부분적으로 복원되지만 일부 사용자는 여전히 문제가 발생할 수 있습니다. 우리는 트래픽을 모니터링하고 업데이트 한 번의 서비스를 완전히 복원합니다.

4. 2026년 7월 27일 PM 8:12 UTCresolved

   Inbound와 outbound 호출은 완전히 복원되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 PM 10:24 UTCidentified

   현재 Salesforce Data Cloud에 새로운 계정 연결을 설정하는 이슈가 있습니다. 기존 고객 통합은 일반적으로 수행됩니다. 우리의 엔지니어링 및 파트너십 팀은 실패를 일으키는 문제를 확인했으며 Salesforce 지원 팀과 협력하여 상황을 해결합니다.

2. 2026년 7월 29일 AM 12:14 UTCresolved

   새로운 Salesforce 연결은 지금 할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 8일 PM 6:29 UTCinvestigating

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

2. 2026년 7월 8일 PM 6:34 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. 2026년 7월 8일 PM 7:14 UTCresolved

   All systems are continuing to operate as expected.

1. 2026년 7월 6일 PM 3:03 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. 2026년 7월 6일 PM 3:46 UTCmonitoring

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

3. 2026년 7월 6일 PM 6:36 UTCresolved

   Call events are fully operational

1. 2026년 6월 26일 PM 7:37 UTCinvestigating

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

2. 2026년 6월 26일 PM 7:40 UTCidentified

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

3. 2026년 6월 26일 PM 7:43 UTCresolved

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

1. 2026년 6월 22일 PM 11:07 UTCinvestigating

   We are investigating reports of issues with inbound SMS messaging.

2. 2026년 6월 22일 PM 11:09 UTCmonitoring

   Service has been restored, we are monitoring the situation.

3. 2026년 6월 22일 PM 11:55 UTCmonitoring

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

4. 2026년 6월 23일 AM 2:41 UTCresolved

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

1. 2026년 6월 19일 PM 5:28 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. 2026년 6월 20일 AM 3:07 UTCresolved

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

1. 2026년 6월 19일 PM 5:08 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. 2026년 6월 20일 AM 2:52 UTCresolved

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

1. 2026년 6월 18일 PM 7:45 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. 2026년 6월 19일 PM 3:40 UTCresolved

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

1. 2026년 6월 18일 PM 6:17 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. 2026년 6월 18일 PM 11:44 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. 2026년 6월 19일 PM 2:54 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. 2026년 6월 20일 AM 2:38 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. 2026년 6월 20일 PM 12:23 UTCresolved

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

1. 2026년 6월 4일 PM 3:26 UTCinvestigating

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

2. 2026년 6월 4일 PM 3:40 UTCidentified

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

3. 2026년 6월 4일 PM 3:58 UTCmonitoring

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

4. 2026년 6월 4일 PM 4:12 UTCresolved

   All systems and services are operating normally.

1. 2026년 6월 1일 PM 6:29 UTCinvestigating

   We are investigating an issue with our Identity provider that is causing authentication issues and is causing some users to be unexpectedly logged out.

2. 2026년 6월 1일 PM 6:37 UTCidentified

   Our infrastructure provider have acknowledged a degradation within their platform and are escalating with their support team.

3. 2026년 6월 1일 PM 6:55 UTCmonitoring

   Performance is recovering; we are continuing to monitor the situation.

4. 2026년 6월 1일 PM 7:23 UTCresolved

   This incident has been resolved.

1. 2026년 5월 26일 PM 4:27 UTCidentified

   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.

2. 2026년 5월 26일 PM 5:09 UTCidentified

   Some inbound messaging may also be impacted.

3. 2026년 5월 26일 PM 6:20 UTCmonitoring

   Messaging is performing normally; the engineering team is continuing to monitor the performance of call activities as they recover.

4. 2026년 5월 26일 PM 9:20 UTCmonitoring

   All systems are operating within expected response times.

5. 2026년 6월 1일 PM 7:08 UTCresolved

   This incident has been resolved.

1. 2026년 5월 21일 PM 4:03 UTCinvestigating

   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.

2. 2026년 5월 21일 PM 4:36 UTCmonitoring

   The engineering team has resolved the issue, all activities & notifications should be fully up to date at this time.

3. 2026년 6월 1일 PM 7:07 UTCresolved

   This incident has been resolved.

1. 2026년 5월 20일 PM 5:22 UTCinvestigating

   We are investigating reports of forced logouts on our desktop applications.

2. 2026년 5월 20일 PM 11:46 UTCmonitoring

   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.

3. 2026년 6월 1일 PM 7:23 UTCresolved

   This incident has been resolved.

1. 2026년 5월 19일 PM 2:38 UTCidentified

   We have identified an issue impacting calling. The team is working to prepare a fix.

2. 2026년 5월 19일 PM 3:30 UTCmonitoring

   Calling has been restored; we are monitoring the situation to ensure stability is maintained.

3. 2026년 5월 19일 PM 7:30 UTCresolved

   All systems are operating normally. We are declaring the incident resolved.

1. 2026년 5월 14일 PM 2:14 UTCinvestigating

   We have received user reports of phone menus failing. On-call engineers have acknowledged and are investigating the situation.

2. 2026년 5월 14일 PM 4:01 UTCmonitoring

   We have identified the issue, and services should be working as normal again. We will continue to monitor.

3. 2026년 5월 15일 PM 2:04 UTCresolved

   All systems continue to operate normally. We declaring the incident resolved.

1. 2026년 4월 22일 PM 1:50 UTCinvestigating

   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.

2. 2026년 4월 22일 PM 3:23 UTCresolved

   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.

1. 2026년 4월 20일 PM 2:46 UTCinvestigating

   We are investigating reports of sporadic issues logging in with the Web and Desktop clients.

2. 2026년 4월 20일 PM 3:13 UTCidentified

   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.

3. 2026년 4월 20일 PM 3:31 UTCresolved

   Service has been updated successfully. We were able to confirm that only members of an Alpha feature cohort were impacted by this bug.

1. 2026년 4월 18일 AM 12:37 UTCinvestigating

   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.

2. 2026년 4월 18일 AM 1:21 UTCresolved

   Services have been successfully deployed. Call disruption was minimized. We again apologize for any adverse impact.