WebEx incident
Webex Calling: Admins will experience failures when attempting to add or delete devices via Webex Control Hub or APIs
WebEx experienced a minor incident on August 10, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Aug 10, 2026, 03:50 AM UTC
Component Status: Commercial / Webex Calling - South America - degraded_performance Commercial / Webex Calling - Canada - degraded_performance Commercial / Webex Calling - N. America (West) - degraded_performance Commercial / Webex Calling - EMEA - degraded_performance Commercial / Webex Calling - ANZ - degraded_performance Commercial / Webex Calling - N. America (East) - degraded_performance Commercial / Webex Calling - APAC - degraded_performance Government / Webex Calling - South America - degraded_performance Government / Webex Calling - Canada - degraded_performance Government / Webex Calling - N. America (West) - degraded_performance Government / Webex Calling - EMEA - degraded_performance Government / Webex Calling - ANZ - degraded_performance Government / Webex Calling - N. America (East) - degraded_performance Government / Webex Calling - APAC - degraded_performance Regions: N. America (West), N. America (East), South America, Canada, EMEA, APAC, ANZ identified - Engineering has identified the issue and is currently working towards service restoration. We will continue to monitor the progress closely and will provide the next update in one hour or sooner should significant progress occur. Thank you for your continued patience as we address this service incident. Aug 10, 03:50 UTC investigating - Engineering is investigating an issue that is causing Webex Calling admins to experience failures when attempting to add or delete calling devices through Webex Control Hub or via APIs. This issue is impacting users globally across both Commercial and Webex for Government environments. At this time, the issue only affects devices that are added using a MAC address. Devices added using an activation code are not impacted and continue to function as expected. We are working towards service restoration and apologize for any inconvenience this may cause. Aug 10, 03:45 UTC