Webex by Cisco Outage History

The Webex Scheduler Add-on for Google Calendar became unavailable for 6.5 hours, preventing users from scheduling Webex meetings directly through their Google Calendar interface. Users could still schedule meetings through their Webex site or use workarounds like typing @webex or @meet in the location field, and existing meetings remained unaffected. Engineering identified and resolved the issue, restoring full service functionality.

Webex experienced a Network Based Recording (NBR) consolidation delay issue that prevented recordings from being processed for over 24 hours after creation, affecting playback and download functionality for Webex Meetings globally and Webex Calling in the EU region. The incident lasted 62.4 hours, during which all recordings created were impacted and unavailable until service restoration. Engineering resolved the issue through mitigation activities, with the EU region being the last to be restored.

Webex Control Hub experienced a 4.7-hour outage where administrators of Webex for Government organizations could not access Analytics data, including Calling Analytics, as the data failed to populate properly. The issue affected the Webex Control Hub and Analytics components, preventing administrators from viewing critical analytics information. Engineering identified and resolved the problem, restoring all services with continued monitoring for stability.

Webex Calling experienced call recording failures for users in the US, Canada, Japan, and EU regions for 2.1 hours. Users with mandatory call recording had their calls disconnected after hearing failure notifications, while other users could continue calls but recordings were unavailable. Engineering identified and resolved the issue, restoring all services.

Webex Contact Center users in the US region experienced intermittent dead air while using the AI Agent feature for 2.8 hours. Engineering identified and resolved the issue through mitigation activities, with services fully restored and monitoring ongoing for stability.

Webex Contact Center experienced an issue affecting real-time reporting, causing administrators in the US region to encounter delays or intermittent failures when retrieving Agent real-time reports within the Analyzer tool. The incident impacted the Webex Contact Center and Reports and Administrative Service components for 52 minutes. Engineering identified and resolved the issue through mitigation activities, restoring full service functionality.

Webex experienced a service incident affecting EU region Contact Center agents who faced failures when responding to calls via WebRTC clients routed through Webex Calling, while Webex Meeting users encountered intermittent meeting join failures. The issue impacted Webex Meetings, Webex Calling, and Webex Contact Center services for 1.3 hours. Engineering identified and resolved the problem through mitigation activities, restoring all affected services.

Webex App experienced a login issue affecting newly created users on version 46.4, preventing them from accessing their accounts. The incident impacted the Webex App's sign-in and sign-up functionality for approximately 9.4 hours. Engineering resolved the issue through mitigation activities, with users able to use version 46.3 as a temporary workaround during the outage.

Webex Contact Center experienced a service degradation affecting AI Agent and AI Assistant interactions in the US and Canada, where users encountered delays, failures, and error messages during their interactions. The incident lasted 2.6 hours before engineering completed mitigation activities and restored services. Cisco continued monitoring to ensure service stability following the resolution.

Webex Web App users experienced a 1.6-hour outage where they could not send or receive 1:1 messages, encountering an error stating "This conversation is closed because the user's account has been deactivated." The issue was isolated to the web application only, with desktop and mobile apps remaining functional as workarounds. Engineering identified and resolved the problem through mitigation activities, restoring full messaging functionality.