Skip to content

Outage tracker / Webex

Is Webex down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Webex from all 10 regions we check.

Reachability verified

No outage recorded in the 14 days we have measured Webex (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East489 msOperational
US-West402 msOperational
Europe387 msOperational
Asia-Pacific747 msOperational
US-Central460 msOperational
Canada997 msOperational
UK517 msOperational
Southeast Asia1118 msOperational
Australia1548 msOperational
South America1112 msOperational
their status pagetheir claim, not our reading

Webex publishes no status feed we can read, so the only independent reading here is ours on the left.

Webex response time, by region

US-East
611msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.3s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 819ms2026-09-05 UTC: p95 611ms
Aug 7Aug 21Sep 5
US-West
444msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 428ms2026-08-23 UTC: p95 991ms2026-08-24 UTC: p95 946ms2026-08-25 UTC: p95 931ms2026-08-26 UTC: p95 895ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 444ms
Aug 7Aug 21Sep 5
Europe
450msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 971ms2026-08-23 UTC: p95 621ms2026-08-24 UTC: p95 783ms2026-08-25 UTC: p95 879ms2026-08-26 UTC: p95 671ms2026-08-27 UTC: p95 778ms2026-08-28 UTC: p95 940ms2026-08-29 UTC: p95 587ms2026-08-30 UTC: p95 626ms2026-08-31 UTC: p95 603ms2026-09-01 UTC: p95 718ms2026-09-02 UTC: p95 865ms2026-09-03 UTC: p95 629ms2026-09-04 UTC: p95 664ms2026-09-05 UTC: p95 450ms
Aug 7Aug 21Sep 5
Asia-Pacific
889msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.2s2026-08-23 UTC: p95 1.4s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 889ms
Aug 7Aug 21Sep 5
US-Central
450msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 600ms2026-09-04 UTC: p95 773ms2026-09-05 UTC: p95 450ms
Aug 7Aug 21Sep 5
Canada
992msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 992ms
Aug 7Aug 21Sep 5
UK
508msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 786ms2026-09-04 UTC: p95 696ms2026-09-05 UTC: p95 508ms
Aug 7Aug 21Sep 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.2s
Aug 7Aug 21Sep 5
Australia
1.5sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.7s2026-09-05 UTC: p95 1.5s
Aug 7Aug 21Sep 5
South America
1.6sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2s2026-09-04 UTC: p95 1.6s2026-09-05 UTC: p95 1.6s
Aug 7Aug 21Sep 5

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 are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 489msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 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-West
      Operationallatency: 402msstatus code: 200checked: Sep 5, 2026, 1:38 AM UTC
      0 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-Central
      Operationallatency: 460msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
      0 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.
    • Canada
      Operationallatency: 997msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 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 America
    Operationallatency: 1112msstatus code: 200checked: Sep 5, 2026, 1:43 AM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 387msstatus code: 200checked: Sep 5, 2026, 1:44 AM UTC
      0 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.
    • UK
      Operationallatency: 517msstatus code: 200checked: Sep 5, 2026, 1:42 AM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 747msstatus code: 200checked: Sep 5, 2026, 1:54 AM UTC
      0 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 Asia
      Operationallatency: 1118msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC
      0 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.
    • Australia
      Operationallatency: 1548msstatus code: 200checked: Sep 5, 2026, 1:47 AM UTC
      0 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

No outages on record yet for Webex.

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 servers

Tell me when this goes down

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Webex uptime measured by RealUptimeLive, from this page's own readings.
[![Webex uptime measured by RealUptime](https://realuptime.io/outages/webex/badge.svg?days=30)](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

At or above your target

We measured none of downtime for Webex over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

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.

What we check

primary
https://status.webex.com/api/v2/status.json
RealUptime is not affiliated with Webex; the name identifies what we measured, and nothing here speaks for Webex's own team. We send a single web request to Webex from 10 regions on our own schedule and time the response. We do not see inside Webex's systems, do not use an account or real transaction, and are not the same signal Webex's own team has access to. Treat this as one external data point, not a verdict. What we check for Webex proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.