Historique des pannes de Openphone

1. 27 juillet 2026 à 16:35 UTCinvestigating

   Les appels entrants et sortants connaissent actuellement des problèmes. L'équipe d'ingénierie est au courant et enquête.

2. 27 juillet 2026 à 18:46 UTCinvestigating

   Nous avons encore des problèmes avec les appels entrants et sortants. Nous travaillons en étroite collaboration avec notre fournisseur pour restaurer le service le plus rapidement possible et partagerons les mises à jour dès que nous en saurons plus.

3. 27 juillet 2026 à 19:34 UTCmonitoring

   Les appels entrants ou sortants sont partiellement rétablis, bien que certains utilisateurs puissent encore éprouver des problèmes. Nous continuons à surveiller le trafic et partagerons une mise à jour une fois le service entièrement rétabli.

4. 27 juillet 2026 à 20:12 UTCresolved

   L'appel entrant et sortant a été entièrement rétabli.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 22:24 UTCidentified

   Nous sommes actuellement confrontés à un problème d'établissement de nouvelles connexions de compte à Salesforce Data Cloud. Les intégrations client existantes se produisent normalement. Nos équipes d'ingénierie et de partenariat ont identifié la cause de l'échec et travaillent avec l'équipe de soutien Salesforce pour résoudre la situation.

2. 29 juillet 2026 à 00:14 UTCresolved

   De nouvelles connexions Salesforce peuvent maintenant être réalisées.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 juillet 2026 à 18:29 UTCinvestigating

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

2. 8 juillet 2026 à 18: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. 8 juillet 2026 à 19:14 UTCresolved

   All systems are continuing to operate as expected.

1. 6 juillet 2026 à 15: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. 6 juillet 2026 à 15:46 UTCmonitoring

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

3. 6 juillet 2026 à 18:36 UTCresolved

   Call events are fully operational

1. 26 juin 2026 à 19:37 UTCinvestigating

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

2. 26 juin 2026 à 19:40 UTCidentified

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

3. 26 juin 2026 à 19:43 UTCresolved

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

1. 22 juin 2026 à 23:07 UTCinvestigating

   We are investigating reports of issues with inbound SMS messaging.

2. 22 juin 2026 à 23:09 UTCmonitoring

   Service has been restored, we are monitoring the situation.

3. 22 juin 2026 à 23:55 UTCmonitoring

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

4. 23 juin 2026 à 02:41 UTCresolved

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

1. 19 juin 2026 à 17: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. 20 juin 2026 à 03:07 UTCresolved

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

1. 19 juin 2026 à 17: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. 20 juin 2026 à 02:52 UTCresolved

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

1. 18 juin 2026 à 19: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. 19 juin 2026 à 15: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. 18 juin 2026 à 18: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. 18 juin 2026 à 23: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. 19 juin 2026 à 14: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. 20 juin 2026 à 02: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. 20 juin 2026 à 12:23 UTCresolved

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

1. 4 juin 2026 à 15:26 UTCinvestigating

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

2. 4 juin 2026 à 15:40 UTCidentified

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

3. 4 juin 2026 à 15:58 UTCmonitoring

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

4. 4 juin 2026 à 16:12 UTCresolved

   All systems and services are operating normally.

1. 1 juin 2026 à 18: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. 1 juin 2026 à 18:37 UTCidentified

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

3. 1 juin 2026 à 18:55 UTCmonitoring

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

4. 1 juin 2026 à 19:23 UTCresolved

   This incident has been resolved.

1. 26 mai 2026 à 16: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. 26 mai 2026 à 17:09 UTCidentified

   Some inbound messaging may also be impacted.

3. 26 mai 2026 à 18:20 UTCmonitoring

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

4. 26 mai 2026 à 21:20 UTCmonitoring

   All systems are operating within expected response times.

5. 1 juin 2026 à 19:08 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 à 16: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. 21 mai 2026 à 16:36 UTCmonitoring

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

3. 1 juin 2026 à 19:07 UTCresolved

   This incident has been resolved.

1. 20 mai 2026 à 17:22 UTCinvestigating

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

2. 20 mai 2026 à 23: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. 1 juin 2026 à 19:23 UTCresolved

   This incident has been resolved.

1. 19 mai 2026 à 14:38 UTCidentified

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

2. 19 mai 2026 à 15:30 UTCmonitoring

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

3. 19 mai 2026 à 19:30 UTCresolved

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

1. 14 mai 2026 à 14:14 UTCinvestigating

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

2. 14 mai 2026 à 16:01 UTCmonitoring

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

3. 15 mai 2026 à 14:04 UTCresolved

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

1. 22 avril 2026 à 13: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. 22 avril 2026 à 15: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. 20 avril 2026 à 14:46 UTCinvestigating

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

2. 20 avril 2026 à 15: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. 20 avril 2026 à 15: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. 18 avril 2026 à 00: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. 18 avril 2026 à 01:21 UTCresolved

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