История сбоев Pexip

1. 20 августа 2026 г. в 02:43 UTCinvestigating

   В настоящее время Pexip испытывает периодические сбои как на страницах документации Сервиса (help.pexip.com), так и на страницах документации Infinity (docs.pexip.com). Страницы загружаются медленно или не реагируют на некоторых пользователей.

2. 21 августа 2026 г. в 07:35 UTCidentified

   Наш поставщик услуг продолжает работать над решением этой проблемы. Страница службы поддержки (help.pexip.com) восстановлена и теперь доступна. Страница Документации Бесконечности (docs.pexip.com) остается недоступной, и мы активно следим за разрешением.

3. 21 августа 2026 г. в 09:39 UTCmonitoring

   Вопрос решен, и страницы документации теперь снова доступны.

4. 24 августа 2026 г. в 14:57 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 14 августа 2026 г. в 16:35 UTCinvestigating

   В настоящее время мы изучаем проблему для аналитики в центре управления Pexip. Некоторые данные об использовании могут быть недоступны.

2. 21 августа 2026 г. в 07:41 UTCidentified

   Our team is continuing to investigate the issue affecting Analytics in Pexip Control Center. Some usage data may still be unavailable while work is ongoing. We will provide a further update once we have more information.

3. 24 августа 2026 г. в 14:58 UTCmonitoring

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

Автоматический перевод официального обновления инцидента.

1. 30 июня 2026 г. в 13:24 UTCinvestigating

   Мы расследуем проблему, когда электронные письма не отправляются из Партнерского портала и Центра управления.

2. 30 июня 2026 г. в 21:10 UTCmonitoring

   Проблема была выявлена и решена.

3. 1 июля 2026 г. в 06:54 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 10 июня 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 мая 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 мая 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 мая 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 мая 2026 г. в 11:33 UTCmonitoring

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

5. 29 мая 2026 г. в 12:52 UTCresolved

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

1. 20 мая 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 мая 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 мая 2026 г. в 13:27 UTCmonitoring

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

4. 20 мая 2026 г. в 13:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20 мая 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 мая 2026 г. в 07:53 UTCresolved

   This incident has been resolved.

1. 30 апреля 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 мая 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 мая 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 июня 2026 г. в 08:05 UTCresolved

   This incident has been resolved.

1. 28 апреля 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 апреля 2026 г. в 09:05 UTCidentified

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

3. 30 апреля 2026 г. в 14:54 UTCidentified

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

4. 30 апреля 2026 г. в 16:09 UTCmonitoring

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

5. 6 мая 2026 г. в 11:11 UTCresolved

   The issue is now resolved.

1. 22 апреля 2026 г. в 08:06 UTCinvestigating

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

2. 22 апреля 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 апреля 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 апреля 2026 г. в 08:30 UTCresolved

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

1. 20 апреля 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 апреля 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 апреля 2026 г. в 12:38 UTCresolved

   This incident has been resolved.

1. 17 апреля 2026 г. в 12:32 UTCinvestigating

   The team is currently investigating the issue.

2. 17 апреля 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 апреля 2026 г. в 12:45 UTCresolved

   This incident is resolved.

1. 14 апреля 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 апреля 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 апреля 2026 г. в 07:43 UTCresolved

   This incident has been resolved.

1. 14 апреля 2026 г. в 15:06 UTCinvestigating

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

2. 14 апреля 2026 г. в 16:27 UTCmonitoring

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

3. 14 апреля 2026 г. в 22:22 UTCresolved

   This incident has been resolved.

1. 8 апреля 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 апреля 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 апреля 2026 г. в 10:20 UTCmonitoring

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

4. 14 апреля 2026 г. в 06:56 UTCresolved

   This incident has been resolved.

1. 30 марта 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 марта 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 марта 2026 г. в 14:12 UTCresolved

   This incident has been resolved.

1. 20 марта 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 марта 2026 г. в 08:23 UTCresolved

   We have found the issue and resolved it.

1. 17 марта 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 февраля 2026 г. в 09:00 UTCinvestigating

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

2. 28 февраля 2026 г. в 09:03 UTCinvestigating

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

3. 28 февраля 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 марта 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.

1. 30 января 2026 г. в 08:54 UTCinvestigating

   We are investigating an issue where packet loss statistics are not available on the Pexip Control Center Diagnostic page.

2. 30 января 2026 г. в 09:17 UTCidentified

   The issue has been identified, and we are working on deploying a fix.

3. 30 января 2026 г. в 10:27 UTCmonitoring

   The fix has been deployed. Packet loss statistics are now available for newly finished calls, and we are monitoring the results.

4. 30 января 2026 г. в 15:06 UTCresolved

   This incident has been resolved.

1. 21 января 2026 г. в 07:52 UTCresolved

   On 20 January 2026, between 09:55 and 20:25 UTC, HP/Poly endpoints registered to the Pexip Service may have experienced issues accessing the LDAP phonebook directory. The issue was identified as being related to a recent planned service update. The change was subsequently reverted, and normal functionality was restored.