There were 157 WebEx outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
WebEx not working for you?
WebEx not working for you?
Minor
: WebEx briefly degraded performance
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 10 minutes)
WebEx's commercial service experienced a brief degraded performance as indicated by the status page. The incident began at and was resolved by , lasting approximately 2 hours 10 minutes. The status page showed two updates during the event, with the service moving from Up to Warn and back to Up. No root cause details were provided on the page.
Minor
: WebEx briefly degraded during BroadCloud provisioning
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(3 hours and 25 minutes)
WebEx experienced degraded service starting at , primarily affecting Cisco BroadCloud / Carrier Provisioning. Users attempting to use WebEx could have encountered intermittent access and slower performance during the provisioning window. The BroadCloud / Carrier Provisioning component transitioned back to normal by and full service was restored by . The incident included four official status updates from WebEx.
Minor
: WebEx brief outage impacts Calling devices and Contact Center
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 hours and 5 minutes)
WebEx experienced a brief degraded performance affecting Webex Calling / Devices and Webex Contact Center / Call Delivery on 2025-09-11. The outage began at with Webex Calling / Devices listed as degraded, followed by Webex Contact Center / Call Delivery entering a degraded state at . The Call Delivery service briefly recovered to normal at , and both components returned to full operation by . The total duration was about 5 hours and 5 minutes.
WebEx's status page issued four official updates during the incident, providing visibility into the progression of the issue and restoration across the affected components. The disruption appeared localized to Webex Calling / Devices and Webex Contact Center / Call Delivery, with no broader impact reported. All affected services were returned to normal by the end of the window.
Minor
: Webex Control Hub / Analytics briefly degraded, then recovered
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
Webex Control Hub / Analytics experienced a brief degradation in performance, with services returning to normal after a short interval. The incident began at and was resolved by , lasting 5 minutes. Webex issued two status updates during the incident to acknowledge the degraded state and confirm recovery, with impact limited to the Webex Control Hub / Analytics component.
Minor
: Webex Contact Center brief degradation lasting 30 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(30 minutes)
The Webex Contact Center / Agent Service experienced a brief degradation lasting about 30 minutes. The issue began at when the Webex status page listed the service as warn, and was resolved at when it returned to up. The status page showed two updates during the incident, with users intermittently affected when using contact center features during the window. The impact was limited to Webex Contact Center functionality and did not indicate a wider outage across other Webex services.
WebEx experienced a degraded performance period on the Commercial service starting at and returning to normal at . The degradation lasted approximately 2 hours, during which users may have encountered slower performance or intermittent issues. The status page indicated a transition from normal operation to degraded performance and back, with two status updates issued during the incident and no further component-level details provided.
Minor
: Webex calling services briefly degraded, then restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
The Webex App / Calling Customer Assist and Webex Calling / Calling, Media and Services experienced a brief degraded state beginning at . Users may have encountered issues with calling features and related media services during this period. The outage lasted about 1 hour and 10 minutes and was resolved by . The service provider issued three official status updates during the incident, reflecting the progression from degraded performance to full recovery.
Minor
: WebEx provisioning and devices briefly degraded; services recovered
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 40 minutes)
WebEx experienced a brief degradation affecting provisioning and device services across Webex Calling and related BroadWorks/BroadCloud components. The incident began at and involved four components: Webex Calling / Provisioning, Webex Calling / Devices, Cisco BroadCloud / Carrier Provisioning, and Webex for BroadWorks / Provisioning. Users may have faced delays or issues with provisioning workflows and device configuration during the window. The affected components began recovering, returning to full operation by .
Over the course of the incident, multiple status updates were posted as engineers worked to restore services, and all components returned to normal operation by the end of the event. The outage lasted about 1 hour and 40 minutes, with restoration confirmed by 12:02 UTC.
WebEx reported a brief maintenance window affecting Slido integrations across 13 components, including Slido Video Integrations, the Slido web app (participant and host access), Slido Presentation Integrations, and related APIs (United States and Europe). The maintenance began at and was resolved by , lasting about 45 minutes. Access and functionality for these Slido-related features were temporarily limited during the window. The WebEx status page issued two official updates during the incident, noting the maintenance and restoration, and all affected components returned to normal after the window.
Webex Calling / Cisco Calling Plans experienced a brief degradation lasting about 30 minutes. The incident began at and was resolved by . The Webex status page listed the affected component as degraded (warn) during the window and then returned to up, with two updates issued by Webex during the incident.