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 Meetings briefly degraded, then restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(20 minutes)
WebEx Meetings / Start/Join Meetings briefly operated in a degraded state, with users potentially experiencing difficulties when starting or joining meetings. The degradation began at and was resolved by , for an approximate duration of 20 minutes. The service issued two status updates during the incident and subsequently returned the component to normal operation.
Minor
: WebEx UCM Cloud Americas Region briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
The Dedicated Instance/UCM Cloud in the WebEx Americas Region briefly entered a degraded state (warn) before returning to normal. The issue began at and was resolved by , lasting about 5 minutes. The WebEx status page recorded two updates during the event, indicating a short-lived regional degradation and quick restoration.
Minor
: WebEx components briefly degraded; all restored by 20:57 UTC
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 55 minutes)
WebEx experienced a brief degraded state affecting three components: WebEx Calling / Call Detail Records (CDR), WebEx Control Hub / Analytics, and WebEx Control Hub / Troubleshooting. The degradation began at . CDR recovered by , while Analytics and Troubleshooting remained degraded until when they returned to normal. The total degraded period lasted roughly 1 hour 55 minutes. WebEx posted status updates as the incident progressed, noting the transitions and confirming recovery by .
Minor
: Webex services briefly degraded across sign-in and devices
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
Webex experienced a brief partial outage affecting three components: Webex App Sign In, Webex Control Hub Sign In, and Webex Cloud Registered Device / Room Systems. The incident began with degraded status for Sign In and devices (starting with 20:57 UTC for Webex Control Hub Sign In and 21:02 UTC for Webex Cloud Registered Device / Room Systems) and escalated to an outage at 21:17 UTC for two components. The Webex App Sign In and Sign Up component also faced issues starting at 21:32 UTC, with all three components recovered by 21:47 UTC. The provider issued five status updates during the incident, outlining progression and resolution. The outage was short but impacted sign-in and device connectivity across Webex services before rapid recovery.
Minor
: WebEx Calendar service degraded for nearly 5 hours
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours and 55 minutes)
The WebEx Hybrid Services / Calendar Service experienced a degraded state beginning at and was restored by , lasting 4 hours and 55 minutes. This affected calendar-related features within WebEx, particularly scheduling and calendar workflows. WebEx issued two status updates during the incident, detailing the degraded calendar service and later confirming restoration; the disruption was contained to the Calendar Service component.
Minor
: Webex Contact Center reports brief degradation
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 45 minutes)
Webex Contact Center / Reports and Administrative Service briefly experienced degraded performance starting at , with the service moving from up to degraded and returning to normal by . The outage lasted approximately 2h 45m and affected reporting and administrative tasks within Webex Contact Center. The provider issued two status updates during the incident. The issue was isolated to this component with no broader regional impact reported.
Minor
: Webex Calendar Service degraded for ~17 hours
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(17 hours and 5 minutes)
Webex Hybrid Services / Calendar Service experienced a period of degraded calendar functionality starting on and ending on , lasting about 17 hours. A user in Melbourne reported issues around , indicating localized impact during the incident.
Webex's status page shows two transitions during the event: the service moved to a degraded state at and returned to normal at . Communication during the incident appeared limited to status updates, with no widespread advisories. The incident appears to have had limited reach based on the available user report and the brief window of degraded performance.
Minor
: Webex Meetings start/join briefly degraded for ~50 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
Webex reported a brief degradation in Webex Meetings start/join functionality on , with service returning to normal at . The incident affected the Webex Meetings / Start/join meetings component and caused intermittent issues when starting or joining meetings. The provider issued two status updates during the incident and the issue was resolved about 50 minutes after it began.
Minor
: Webex Calling and Contact Center Call Delivery briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 30 minutes)
Webex experienced a brief degraded state affecting Webex Calling / Calling and Webex Contact Center / Call Delivery. The issue began at with Webex Calling entering a degraded phase, and by the Call Delivery component also showed degraded status. Both components were restored by . The incident lasted about 1 hour and 30 minutes, with three official status updates issued during the period.
Minor
: WebEx Meetings briefly degraded, then restored
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(15 minutes)
WebEx Meetings / Schedule Meetings experienced a brief degradation affecting scheduling and meeting initiation. The incident began on and was resolved by , lasting roughly 15 minutes. The WebEx status page logged the Webex Meetings / Schedule Meetings component moving from Up to a degraded state and back to Up. The provider issued 2 official updates during the incident, communicating the temporary impact and rapid recovery.