Live  /  Webex  /  Incident

Webex: Developer API: Some Cisco-owned Webex bots are currently unable to receive or respond to user messages

Webex · webex.comResolved2026-10-23 15:13 UTC
Public — what happened

Summary

Webex said that some of its Cisco-owned bots, which are automated helpers inside the app, were not responding to user messages, and that people could see failures when trying to get answers from them. The company reported that the problem began at 13:40 UTC on October 23 and affected every region where its Developer API runs. Webex said engineers had identified the issue by 13:49 UTC, reported services restored at 14:46 UTC, and marked the incident resolved at 15:13 UTC after services stayed stable. No cause was given in the text it published.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Webex against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Webex: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Webex report →

More from Webex

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Webex status & history page.

Related: Webex status & history. SquidGrid is not affiliated with Webex.