Is Webex Down?
When we last reached Webex directly, it answered and refused us — origin returns HTTP 403 bot challenge. An answer is proof the origin was serving traffic, but it measures our access, not the service, so we publish no percentage.
Last checked · checks run every 6 hours
Official status page: https://status.webex.com
Why there is no uptime figure on this page
The last time we fetched Webex's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether Webex works for you.
A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and Webex's own status feed, which you can weigh yourself.
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. Because Webex blocks our own checks, this feed is the only availability signal we have, and the verdict above reflects it directly.
30-day history
Reachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
A static asset loaded in 17ms. That proves the edge is up, but not that the site works.
A static asset loaded in 1018ms. That proves the edge is up, but not that the site works.
A static asset loaded in 19ms. That proves the edge is up, but not that the site works.
A static asset loaded in 20ms. That proves the edge is up, but not that the site works.
A static asset loaded in 18ms. That proves the edge is up, but not that the site works.
A static asset loaded in 19ms. That proves the edge is up, but not that the site works.
A static asset loaded in 20ms. That proves the edge is up, but not that the site works.
A static asset loaded in 54ms. That proves the edge is up, but not that the site works.
A static asset loaded in 14ms. That proves the edge is up, but not that the site works.
What Webex does
Webex is Cisco's meetings, calling and contact centre platform, used by enterprises, universities and public-sector bodies for video conferencing, desk phones and customer support lines. It is often the sanctioned alternative to consumer tools, so an outage can stop scheduled meetings, inbound telephony and a live support queue at the same moment.
What an outage looks like
Joining a meeting stalls at the connecting stage or drops everyone after a few seconds, and audio connects while video never appears. The desktop app shows messages as sending without delivering them, and Webex Calling handsets register but cannot place calls. Contact centre agents stay logged in while queued calls stop routing, so the queue reads as empty rather than broken.
What to do about it
Check status.webex.com, which is a grid of services against regions covering North America West and East, South America, Canada, EMEA, APAC and ANZ, so confirm your own region rather than the page as a whole. Cisco states the page is used only for widespread active incidents, so smaller faults will not appear there; raise those through Control Hub instead.
Is it down for everyone, or just you?
If this page says Webex is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.
Related services
Webex outage FAQ
Is Webex down or is it my network?
Does a Webex outage in another region affect mine?
Can I still make calls if Webex Meetings is down?
Are recordings and chat history lost during an outage?
Why is nothing showing on the Webex status page?
How we measure this
- We request Webex's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Webex publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when Webex blocks our checks entirely, we report the vendor's own status directly.
Get alerted when Webex goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.
Start Free Monitoring