Historique des pannes de Pexip

1. 7 octobre 2026 à 12:55 UTCinvestigating

   Nous enquêtons sur les rapports que Microsoft Teams Guest Join appels peuvent ne pas se connecter lorsque composé à partir des appareils matériels Google Meet.

2. 7 octobre 2026 à 13:04 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 7 octobre 2026 à 14:38 UTCresolved

   Cet incident a été résolu.

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

1. 15 septembre 2026 à 12:19 UTCinvestigating

   Les paramètres de Cisco qui sont: Inscription au service Pexip ET mise à jour à 26,9 ou 26,10 Peut ne pas recevoir de présentation de la fin des appels via les services Teams CVI ou Google Meet Gateway. L'envoi de la présentation est signalé au travail, et débloque également la présentation entrante. Nous vous recommandons de ne pas mettre à jour les systèmes Cisco à 26,9 ou 26,10 pendant notre enquête. Veuillez retourner tous les systèmes touchés à 26.8 pendant que nous établissons la cause.

2. 15 septembre 2026 à 13:05 UTCidentified

   Nous avons identifié un changement lié à la façon dont Cisco maintient le canal de présentation en vie et prévoyons une mise à jour pour s'adapter aux changements.

3. 15 septembre 2026 à 15:34 UTCidentified

   Nous avons identifié le problème avec la nouvelle version RoomOS et avons commencé à mettre en place un correctif. Une perturbation mineure est possible pendant le déploiement, et un petit nombre d'appels peuvent être touchés. Pour cette raison, le déploiement se fera en dehors des heures d'ouverture dans chaque région.

4. 16 septembre 2026 à 05:44 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

5. 16 septembre 2026 à 08:18 UTCresolved

   Cet incident a été résolu.

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

1. 20 août 2026 à 02:43 UTCinvestigating

   Pexip subit actuellement des pannes intermittentes pour les pages de documentation du Service (help.pexip.com) et de Infinity (docs.pexip.com). Les pages sont soit lentes à charger, soit insensibles pour certains utilisateurs.

2. 21 août 2026 à 07:35 UTCidentified

   Notre fournisseur de services continue de travailler à résoudre ce problème. La page d'aide de service (help.pexip.com) a été récupérée et est maintenant accessible. La page de documentation Infinity (docs.pexip.com) reste indisponible et nous surveillons activement une résolution.

3. 21 août 2026 à 09:39 UTCmonitoring

   Le problème a été résolu et les pages de documentation sont maintenant à nouveau accessibles.

4. 24 août 2026 à 14:57 UTCresolved

   Cet incident a été résolu.

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

1. 14 août 2026 à 16:35 UTCinvestigating

   Nous enquêtons actuellement sur un problème pour Analytics sur Pexip Control Center. Certaines données d'utilisation pourraient ne pas être disponibles.

2. 21 août 2026 à 07:41 UTCidentified

   Notre équipe continue d'étudier la question touchant l'analyse dans le centre de contrôle de Pexip. Certaines données d'utilisation peuvent encore ne pas être disponibles pendant que le travail est en cours. Nous fournirons une nouvelle mise à jour lorsque nous aurons plus d'informations.

3. 24 août 2026 à 14:58 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 22 septembre 2026 à 12:32 UTCresolved

   Aucun autre problème n'a été signalé ou observé. Cet incident est maintenant résolu.

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

1. 30 juin 2026 à 13:24 UTCinvestigating

   Nous enquêtons sur un problème où les e-mails ne sont pas envoyés par le portail partenaire et le centre de contrôle.

2. 30 juin 2026 à 21:10 UTCmonitoring

   Le problème a été identifié et corrigé.

3. 1 juillet 2026 à 06:54 UTCresolved

   Cet incident a été résolu.

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

1. 10 juin 2026 à 11:23 UTCresolved

   Between Monday 8 June, 15:15 and Wednesday 10 June, 11:00 (UTC), users were unable to create One-Time Rooms (OTR) using the Pexip Service Outlook Add-In. Personal VMRs and previously scheduled One-Time Rooms were not affected. The issue has been resolved and scheduling of One-Time VMRs via the Outlook Add-In is now functioning normally. This incident is being logged retroactively after resolution.

1. 29 mai 2026 à 09:41 UTCinvestigating

   We detected incoming SIP call failures in the Oregon Point of Presence (PoP) and are currently investigating the issue.

2. 29 mai 2026 à 10:05 UTCinvestigating

   As a mitigation step, we have re-routed incoming SIP calls to an alternative location. This change is intended to resolve the impact while we continue investigating the issue in the Oregon PoP.

3. 29 mai 2026 à 11:25 UTCidentified

   We have identified an issue with an unavailable infrastructure component that caused some SIP Teams CVI calls to fail in Oregon and are actively working to resolve the issue.

4. 29 mai 2026 à 11:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 29 mai 2026 à 12:52 UTCresolved

   This incident has been resolved. Incoming SIP call handling has been restored to its normal operating configuration.

1. 20 mai 2026 à 08:24 UTCinvestigating

   We are investigating an issue causing calls to appear with a delay on the Diagnostics Page in Pexip Control Center.

2. 20 mai 2026 à 08:38 UTCmonitoring

   We have implemented a fix to address delayed call visibility on the Diagnostics Page in Pexip Control Center. Some delay may persist while the system clears existing backlog. We are actively monitoring.

3. 20 mai 2026 à 13:27 UTCmonitoring

   Currently diagnostics are unavailable in PCC. We continue to work to bring this feature online.

4. 20 mai 2026 à 13:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20 mai 2026 à 15:09 UTCmonitoring

   The issue affecting the Diagnostics page has been resolved and we are monitoring system behavior. Some delay in data appearing on the Diagnostics page may persist while the system clears the existing backlog.

6. 21 mai 2026 à 07:53 UTCresolved

   This incident has been resolved.

1. 30 avril 2026 à 12:23 UTCidentified

   The issue can be seen on meetings where a Teams recorder bot is present. The unknown participant represents a new version of the Teams recording bot. We are working to block visibility of this new bot in the layout ASAP.

2. 4 mai 2026 à 10:16 UTCidentified

   Further explanation: The unknown teams participant (in some layouts, shown as the "t8" participant avatar) can appear to the Video Conference (CVI) participant, when a "Teams Consumer" user joins the meeting. The "t8" participant represents the Teams Consumer meeting recording bot, and should not be visible to the Video Conference (CVI) participant. There is no impact on meetings when only Teams Enterprise / Commercial / Business users are present.

3. 6 mai 2026 à 11:03 UTCidentified

   We've already seen a reduction in the Teams Consumer recorder bots being added to meetings, and therefore the "t8" unexpected user is now very rarely seen on screen. A fix will be applied to the service within the next few weeks.

4. 15 juin 2026 à 08:05 UTCresolved

   This incident has been resolved.

1. 28 avril 2026 à 16:13 UTCinvestigating

   We are investigating an issue where calls from the Pexip app for iOS to Pexip Service VMRs are ending prematurely. Affected customers should use the My Meeting Video (MMV) iOS app, now available for download at https://apps.apple.com/us/app/pexip-my-meeting-video/id1018923867

2. 30 avril 2026 à 09:05 UTCidentified

   The issue has been identified and a mitigation is being deployed within the service.

3. 30 avril 2026 à 14:54 UTCidentified

   We are continuing to work on a fix for this issue.

4. 30 avril 2026 à 16:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 6 mai 2026 à 11:11 UTCresolved

   The issue is now resolved.

1. 22 avril 2026 à 08:06 UTCinvestigating

   We are currently investigating an issue affecting some Microsoft Teams CVI connections, where calls may intermittently fail.

2. 22 avril 2026 à 08:22 UTCidentified

   Errors from Microsoft Teams have been identified and are tied to Microsoft issue TM1286773. We are coordinating with Microsoft and are monitoring closely.

3. 22 avril 2026 à 11:27 UTCmonitoring

   We have not observed any errors for the past few hours. We will continue to monitor the situation closely.

4. 23 avril 2026 à 08:30 UTCresolved

   No further issues have been observed or reported. This incident has been resolved.

1. 20 avril 2026 à 00:29 UTCinvestigating

   Pexip documentation web pages are currently unavailable due to an outage with a service provider. This outage affects both help.pexip.com and docs.pexip.com web sites. The provider is currently investigating the cause of this outage and working a fix.

2. 20 avril 2026 à 08:09 UTCmonitoring

   Service has been restored for both help.pexip.com and docs.pexip.com documentation pages. We will continue to monitor service availability.

3. 20 avril 2026 à 12:38 UTCresolved

   This incident has been resolved.

1. 17 avril 2026 à 12:32 UTCinvestigating

   The team is currently investigating the issue.

2. 17 avril 2026 à 12:38 UTCmonitoring

   A small number of Zoom Connect for Teams CVI calls in Europe might have failed to bypass the lobby. A fix has been implemented, and we're monitoring the results.

3. 17 avril 2026 à 12:45 UTCresolved

   This incident is resolved.

1. 14 avril 2026 à 15:18 UTCinvestigating

   We are investigating a packet loss issue occurring between Cisco Webex and Pexip that is affecting calls from Webex-registered endpoints located in India. Participants connecting from their Webex devices may experience degraded call quality in the direction from the device to Pexip.

2. 15 avril 2026 à 09:05 UTCmonitoring

   The previously observed packet loss affecting calls between Webex-registered endpoints in India and Pexip is no longer occurring and has remained stable for a period of time. Based on available data, the issue appears to have been related to factors along the public internet path. We continue to monitor the situation to ensure call quality remains stable.

3. 16 avril 2026 à 07:43 UTCresolved

   This incident has been resolved.

1. 14 avril 2026 à 15:06 UTCinvestigating

   We are investigating an issue where some CVI calls in the US region are failing.

2. 14 avril 2026 à 16:27 UTCmonitoring

   A fix has been applied and we are monitoring the results.

3. 14 avril 2026 à 22:22 UTCresolved

   This incident has been resolved.

1. 8 avril 2026 à 11:11 UTCidentified

   We have identified an issue affecting Pexip Android and iOS mobile app users. In some cases, users are unable to join Pexip hosted one-time Virtual Meeting Rooms (VMRs) directly from the in-app Calendar when the meeting is scheduled via the Pexip Service Outlook Plug-in. New mobile app versions are planned for release in the coming days to address this issue. In the meantime, users can join meetings by selecting the Address option in the app and manually entering [email protected] URI.

2. 13 avril 2026 à 07:14 UTCidentified

   The Android app version 1.1.3 is now available and includes changes that address this issue. We are continuing work on the iOS version.

3. 13 avril 2026 à 10:20 UTCmonitoring

   IOS app version 1.1.4 is now available and includes changes that address this issue.

4. 14 avril 2026 à 06:56 UTCresolved

   This incident has been resolved.

1. 30 mars 2026 à 12:47 UTCinvestigating

   We are currently investigating an issue where Teams SIP Guest Join calls fail to connect when using 15-digit meeting IDs. Users attempting to join these meetings from SIP devices, Zoom, or Google Rooms may fail to connect.

2. 30 mars 2026 à 13:05 UTCmonitoring

   A fix has been implemented for the issue. Teams Guest Join calls with 15-digit meeting IDs should now connect successfully. Customers running the "Pexip Ad Hoc Join for Teams on Cisco endpoints" (https://help.pexip.com/macros/ad-hoc-join-teams.htm) need to update the msteams-macro-settings.js file to ensure the regex supports meeting IDs longer than 14 digits.

3. 30 mars 2026 à 14:12 UTCresolved

   This incident has been resolved.

1. 20 mars 2026 à 07:49 UTCinvestigating

   We have observed an issue where some Zoom Rooms might fail to bypass the Teams lobby. Out Team is looking into it.

2. 20 mars 2026 à 08:23 UTCresolved

   We have found the issue and resolved it.

1. 17 mars 2026 à 12:54 UTCresolved

   Between 12:01 and 12:04 UTC on March 17, some calls within the Pexip Service may have experienced failures. The issue has been resolved and the service is operating normally. We will continue to monitor.

1. 28 février 2026 à 09:00 UTCinvestigating

   We have observed a Cloud OTJ issue affecting some M365 mailboxes. Our Team is looking into it.

2. 28 février 2026 à 09:03 UTCinvestigating

   We have contacted Microsoft to investigate this issue together with them.

3. 28 février 2026 à 16:41 UTCmonitoring

   We have identified an issue affecting some Microsoft 365 tenants. The impact has been traced to a third-party application making mailbox queries through the Microsoft Graph API, which may result in degraded performance or unexpected behavior in Pexip Cloud OTJ. Customers experiencing issues with Cloud OTJ are advised to open a support ticket so our team can review their environment and provide additional details and guidance.

4. 2 mars 2026 à 09:51 UTCresolved

   We have completed our investigation and found no issues within Pexip Cloud OTJ. Some Microsoft 365 tenants may experience degraded performance caused by mailbox activity from third party applications using the Microsoft Graph API. Customers still experiencing Cloud OTJ issues should contact support for further investigation and guidance.