Is Webex down?
Operationalchecked 11 minutes ago
We reached Webex from all 10 regions we check.
As of Oct 5, 2026, 8:05 PM UTC, Webex answered RealUptime's probes in all 10 regions that returned a reading.
Last outage: 2h 47m on Oct 3, 2026 (API, from Europe, UK and Southeast Asia, intermittent).
Webex publishes no status feed we can read, so the only independent reading here is ours on the left.
Webex response time, by region
Is it Webex, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Webex -- it cannot diagnose Webex's own systems.
What we measured, function by function
Webex answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
Get an email when we see Webex go down, and when it is back
Get told when we measure this
We will tell you when our probes stop reaching Webex, and again when they can reach it again. That is our own measurement from ten regions, not Webex's status page. No account, no card.
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 319msstatus code: 401checked: Oct 5, 2026, 7:58 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Webex normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 425msstatus code: 401checked: Oct 5, 2026, 7:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Webex normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 327msstatus code: 401checked: Oct 5, 2026, 7:24 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Webex normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 528msstatus code: 401checked: Oct 5, 2026, 7:37 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Webex normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 1085msstatus code: 401checked: Oct 5, 2026, 7:17 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Webex normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 84msstatus code: 401checked: Oct 5, 2026, 7:56 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Webex normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 235msstatus code: 401checked: Oct 5, 2026, 8:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Webex normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 346msstatus code: 401checked: Oct 5, 2026, 7:56 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Webex normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 990msstatus code: 401checked: Oct 5, 2026, 7:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Webex normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 540msstatus code: 401checked: Oct 5, 2026, 7:30 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Webex normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Webex, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Webex yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Webex since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Webex covering any window you pick, with our measurements and Webex's own claim at the time, side by side.
Full availability history for Webex: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/webex)<a href="https://realuptime.io/outages/webex"><img src="https://realuptime.io/outages/webex/badge.svg?days=30" alt="Webex uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Webex's SLA implies, from our measurement
Below your target
We measured 2h 47m of downtime for Webex over the last 30 days, which is 99.6129% uptime by our reading. A 99.9% target allows 43 minutes over that period.
That is 2h 4m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
This is computed from our own probe measurements, not from Webex's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.