Istoricul incidentelor Pexip

1. 7 octombrie 2026 la 12:55 UTCinvestigating

   Investigăm rapoarte conform cărora apelurile Microsoft Teams Enjoin pot eşua în a se conecta atunci când sunt apelate de pe dispozitivele hardware Google Meet.

2. 7 octombrie 2026 la 13:04 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 7 octombrie 2026 la 14:38 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 15 septembrie 2026 la 12:19 UTCinvestigating

   Criterii de evaluare Cisco care sunt: Înregistrat la serviciul Pexip ȘI au fost actualizate la 26.9 sau 26.10 Poate că nu a primit Prezentare de la capătul îndepărtat în apeluri prin intermediul Echipelor CVI sau Google Meet Gateway servicii. Trimiterea prezentării este raportată la locul de muncă și, de asemenea, deblochează prezentarea care urmează. Vă recomandăm să nu actualizaţi sistemele Cisco la 26.9 sau 26.10 în timp ce investigăm. Vă rugăm să rulați orice sisteme afectate înapoi la 26.8 în timp ce vom stabili cauza.

2. 15 septembrie 2026 la 13:05 UTCidentified

   Am identificat o schimbare legată de modul în care Cisco păstrează canalul de prezentare în viață, și sunt de planificare o actualizare pentru a se adapta la modificările.

3. 15 septembrie 2026 la 15:34 UTCidentified

   Am identificat problema cu noua versiune RoomOS și au început rularea o fix. Este posibilă perturbarea minoră în timpul derulării apelurilor și poate fi afectat un număr mic de apeluri. Din acest motiv, lansarea se va desfășura în afara orelor de lucru din fiecare regiune.

4. 16 septembrie 2026 la 05:44 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

5. 16 septembrie 2026 la 08:18 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 02:43 UTCinvestigating

   Pexip se confruntă în prezent cu întreruperi intermitente atât pentru paginile de documentare Service (help.pexip.com) și Infinity (docs.pexip.com). Paginile sunt fie lent pentru a încărca sau nu răspunde pentru unii utilizatori.

2. 21 august 2026 la 07:35 UTCidentified

   Furnizorul nostru de servicii continuă să lucreze la rezolvarea acestei probleme. Pagina de ajutor serviciu (help.pexip.com) a recuperat și este acum accesibil. Pagina de Documentare Infinity (docs.pexip.com) rămâne indisponibilă, iar noi monitorizăm în mod activ o rezoluție.

3. 21 august 2026 la 09:39 UTCmonitoring

   Problema a fost rezolvată, iar paginile de documentare sunt acum accesibile din nou.

4. 24 august 2026 la 14:57 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 14 august 2026 la 16:35 UTCinvestigating

   Investigăm în prezent o problemă pentru Analytics pe Pexip Control Center. Este posibil ca unele date de utilizare să nu fie disponibile.

2. 21 august 2026 la 07:41 UTCidentified

   Echipa noastră continuă să investigheze problema care afectează Analytics în Pexip Control Center. Unele date de utilizare pot fi încă indisponibile în timp ce activitatea este în curs de desfășurare. Vom oferi o actualizare suplimentară odată ce vom avea mai multe informații.

3. 24 august 2026 la 14:58 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 22 septembrie 2026 la 12:32 UTCresolved

   Nu au fost raportate sau observate alte probleme. Acest incident este acum rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iunie 2026 la 13:24 UTCinvestigating

   Investigăm o problemă în care e-mailurile nu sunt trimise de la Portalul Partener şi Centrul de Control.

2. 30 iunie 2026 la 21:10 UTCmonitoring

   Problema a fost identificată și rezolvată.

3. 1 iulie 2026 la 06:54 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iunie 2026 la 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 la 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 la 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 la 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 la 11:33 UTCmonitoring

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

5. 29 mai 2026 la 12:52 UTCresolved

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

1. 20 mai 2026 la 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 la 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 la 13:27 UTCmonitoring

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

4. 20 mai 2026 la 13:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20 mai 2026 la 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 la 07:53 UTCresolved

   This incident has been resolved.

1. 30 aprilie 2026 la 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 la 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 la 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 iunie 2026 la 08:05 UTCresolved

   This incident has been resolved.

1. 28 aprilie 2026 la 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 aprilie 2026 la 09:05 UTCidentified

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

3. 30 aprilie 2026 la 14:54 UTCidentified

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

4. 30 aprilie 2026 la 16:09 UTCmonitoring

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

5. 6 mai 2026 la 11:11 UTCresolved

   The issue is now resolved.

1. 22 aprilie 2026 la 08:06 UTCinvestigating

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

2. 22 aprilie 2026 la 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 aprilie 2026 la 11:27 UTCmonitoring

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

4. 23 aprilie 2026 la 08:30 UTCresolved

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

1. 20 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 12:38 UTCresolved

   This incident has been resolved.

1. 17 aprilie 2026 la 12:32 UTCinvestigating

   The team is currently investigating the issue.

2. 17 aprilie 2026 la 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 aprilie 2026 la 12:45 UTCresolved

   This incident is resolved.

1. 14 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 07:43 UTCresolved

   This incident has been resolved.

1. 14 aprilie 2026 la 15:06 UTCinvestigating

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

2. 14 aprilie 2026 la 16:27 UTCmonitoring

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

3. 14 aprilie 2026 la 22:22 UTCresolved

   This incident has been resolved.

1. 8 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 10:20 UTCmonitoring

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

4. 14 aprilie 2026 la 06:56 UTCresolved

   This incident has been resolved.

1. 30 martie 2026 la 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 martie 2026 la 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 martie 2026 la 14:12 UTCresolved

   This incident has been resolved.

1. 20 martie 2026 la 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 martie 2026 la 08:23 UTCresolved

   We have found the issue and resolved it.

1. 17 martie 2026 la 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 februarie 2026 la 09:00 UTCinvestigating

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

2. 28 februarie 2026 la 09:03 UTCinvestigating

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

3. 28 februarie 2026 la 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 martie 2026 la 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.