Skip to content

Outage tracker / Webex

Is Webex down?

I'm having a problem

Vendor reports no incidentWhat Webex reports

Webex reports no incident on its status page.

As of the last successful poll, 2026-10-14 14:25 UTC.

Webex's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Webex pass from all 10 regions we check.

As of Oct 14, 2026, 2:33 PM UTC, RealUptime's checks of Webex passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 14, 2026, 2:33 PM UTC
US-East374 msChecks passing
US-West405 msChecks passing
Europe34 msChecks passing
Asia-Pacific400 msChecks passing
US-Central154 msChecks passing
Canada254 msChecks passing
UK118 msChecks passing
Southeast Asia349 msChecks passing
Australia525 msChecks passing
South America708 msChecks passing
their status pagetheir claim, not our reading

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

Webex response time, by region

US-East
451msp95 · 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-09-15 UTC: p95 801ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 982ms2026-09-20 UTC: p95 791ms2026-09-21 UTC: p95 804ms2026-09-22 UTC: p95 811ms2026-09-23 UTC: p95 815ms2026-09-24 UTC: p95 867ms2026-09-25 UTC: p95 860ms2026-09-26 UTC: p95 793ms2026-09-27 UTC: p95 836ms2026-09-28 UTC: p95 787ms2026-09-29 UTC: p95 898ms2026-09-30 UTC: p95 800ms2026-10-01 UTC: p95 466ms2026-10-02 UTC: p95 445ms2026-10-03 UTC: p95 508ms2026-10-04 UTC: p95 452ms2026-10-05 UTC: p95 482ms2026-10-06 UTC: p95 444ms2026-10-07 UTC: p95 497ms2026-10-08 UTC: p95 449ms2026-10-09 UTC: p95 512ms2026-10-10 UTC: p95 507ms2026-10-11 UTC: p95 437ms2026-10-12 UTC: p95 619ms2026-10-13 UTC: p95 557ms2026-10-14 UTC: p95 451ms
Sep 15Sep 29Oct 14
US-West
456msp95 · 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-09-15 UTC: p95 927ms2026-09-16 UTC: p95 931ms2026-09-17 UTC: p95 918ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 973ms2026-09-20 UTC: p95 936ms2026-09-21 UTC: p95 951ms2026-09-22 UTC: p95 850ms2026-09-23 UTC: p95 862ms2026-09-24 UTC: p95 906ms2026-09-25 UTC: p95 879ms2026-09-26 UTC: p95 841ms2026-09-27 UTC: p95 833ms2026-09-28 UTC: p95 869ms2026-09-29 UTC: p95 812ms2026-09-30 UTC: p95 856ms2026-10-01 UTC: p95 566ms2026-10-02 UTC: p95 420ms2026-10-03 UTC: p95 519ms2026-10-04 UTC: p95 479ms2026-10-05 UTC: p95 472ms2026-10-06 UTC: p95 458ms2026-10-07 UTC: p95 478ms2026-10-08 UTC: p95 433ms2026-10-09 UTC: p95 444ms2026-10-10 UTC: p95 588ms2026-10-11 UTC: p95 576ms2026-10-12 UTC: p95 503ms2026-10-13 UTC: p95 458ms2026-10-14 UTC: p95 456ms
Sep 15Sep 29Oct 14
Europe
185msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 685ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 928ms2026-09-19 UTC: p95 721ms2026-09-20 UTC: p95 920ms2026-09-21 UTC: p95 780ms2026-09-22 UTC: p95 922ms2026-09-23 UTC: p95 698ms2026-09-24 UTC: p95 700ms2026-09-25 UTC: p95 640ms2026-09-26 UTC: p95 691ms2026-09-27 UTC: p95 661ms2026-09-28 UTC: p95 736ms2026-09-29 UTC: p95 645ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 290ms2026-10-02 UTC: p95 323ms2026-10-03 UTC: p95 325ms2026-10-04 UTC: p95 254ms2026-10-05 UTC: p95 142ms2026-10-06 UTC: p95 321ms2026-10-07 UTC: p95 297ms2026-10-08 UTC: p95 309ms2026-10-09 UTC: p95 291ms2026-10-10 UTC: p95 263ms2026-10-11 UTC: p95 277ms2026-10-12 UTC: p95 237ms2026-10-13 UTC: p95 215ms2026-10-14 UTC: p95 185ms
Sep 15Sep 29Oct 14
Asia-Pacific
493msp95 · 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-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 447ms2026-10-02 UTC: p95 637ms2026-10-03 UTC: p95 568ms2026-10-04 UTC: p95 818ms2026-10-05 UTC: p95 528ms2026-10-06 UTC: p95 536ms2026-10-07 UTC: p95 716ms2026-10-08 UTC: p95 587ms2026-10-09 UTC: p95 751ms2026-10-10 UTC: p95 615ms2026-10-11 UTC: p95 575ms2026-10-12 UTC: p95 623ms2026-10-13 UTC: p95 668ms2026-10-14 UTC: p95 493ms
Sep 15Sep 29Oct 14
US-Central
555msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 737ms2026-09-16 UTC: p95 731ms2026-09-17 UTC: p95 756ms2026-09-18 UTC: p95 708ms2026-09-19 UTC: p95 646ms2026-09-20 UTC: p95 644ms2026-09-21 UTC: p95 699ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 888ms2026-09-24 UTC: p95 658ms2026-09-25 UTC: p95 801ms2026-09-26 UTC: p95 804ms2026-09-27 UTC: p95 709ms2026-09-28 UTC: p95 636ms2026-09-29 UTC: p95 689ms2026-09-30 UTC: p95 686ms2026-10-01 UTC: p95 333ms2026-10-02 UTC: p95 283ms2026-10-03 UTC: p95 450ms2026-10-04 UTC: p95 462ms2026-10-05 UTC: p95 469ms2026-10-06 UTC: p95 507ms2026-10-07 UTC: p95 601ms2026-10-08 UTC: p95 602ms2026-10-09 UTC: p95 508ms2026-10-10 UTC: p95 296ms2026-10-11 UTC: p95 427ms2026-10-12 UTC: p95 331ms2026-10-13 UTC: p95 440ms2026-10-14 UTC: p95 555ms
Sep 15Sep 29Oct 14
Canada
411msp95 · 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-15 UTC: p95 1.0s2026-09-16 UTC: p95 998ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 874ms2026-09-28 UTC: p95 994ms2026-09-29 UTC: p95 950ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 661ms2026-10-02 UTC: p95 595ms2026-10-03 UTC: p95 586ms2026-10-04 UTC: p95 430ms2026-10-05 UTC: p95 506ms2026-10-06 UTC: p95 654ms2026-10-07 UTC: p95 637ms2026-10-08 UTC: p95 670ms2026-10-09 UTC: p95 524ms2026-10-10 UTC: p95 554ms2026-10-11 UTC: p95 651ms2026-10-12 UTC: p95 503ms2026-10-13 UTC: p95 608ms2026-10-14 UTC: p95 411ms
Sep 15Sep 29Oct 14
UK
178msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 718ms2026-09-16 UTC: p95 797ms2026-09-17 UTC: p95 911ms2026-09-18 UTC: p95 839ms2026-09-19 UTC: p95 779ms2026-09-20 UTC: p95 793ms2026-09-21 UTC: p95 844ms2026-09-22 UTC: p95 809ms2026-09-23 UTC: p95 894ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 870ms2026-09-26 UTC: p95 938ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 982ms2026-09-30 UTC: p95 772ms2026-10-01 UTC: p95 428ms2026-10-02 UTC: p95 271ms2026-10-03 UTC: p95 300ms2026-10-04 UTC: p95 368ms2026-10-05 UTC: p95 285ms2026-10-06 UTC: p95 333ms2026-10-07 UTC: p95 288ms2026-10-08 UTC: p95 218ms2026-10-09 UTC: p95 212ms2026-10-10 UTC: p95 372ms2026-10-11 UTC: p95 402ms2026-10-12 UTC: p95 445ms2026-10-13 UTC: p95 243ms2026-10-14 UTC: p95 178ms
Sep 15Sep 29Oct 14
Southeast Asia
1.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 2.2s2026-09-27 UTC: p95 2.1s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.0s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 910ms2026-10-13 UTC: p95 912ms2026-10-14 UTC: p95 1.1s
Sep 15Sep 29Oct 14
Australia
857msp95 · 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-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 872ms2026-10-02 UTC: p95 984ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 978ms2026-10-05 UTC: p95 982ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 762ms2026-10-08 UTC: p95 810ms2026-10-09 UTC: p95 914ms2026-10-10 UTC: p95 993ms2026-10-11 UTC: p95 915ms2026-10-12 UTC: p95 760ms2026-10-13 UTC: p95 834ms2026-10-14 UTC: p95 857ms
Sep 15Sep 29Oct 14
South America
917msp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 2.0s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.2s2026-09-18 UTC: p95 2.1s2026-09-19 UTC: p95 2.0s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 2.1s2026-09-23 UTC: p95 2.1s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 2.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 917ms
Sep 15Sep 29Oct 14

Check your own site while you wait on Webex

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Webex reports an incident on its status page, and again when it reports it resolved.

Get an email when Webex reports an incident

Email me when Webex reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Webex's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 374msstatus code: 401checked: Oct 14, 2026, 2:33 PM 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
      Checks passinglatency: 405msstatus code: 401checked: Oct 14, 2026, 2:04 PM 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
      Checks passinglatency: 154msstatus code: 401checked: Oct 14, 2026, 2:28 PM 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
      Checks passinglatency: 254msstatus code: 401checked: Oct 14, 2026, 1:44 PM 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
    Checks passinglatency: 708msstatus code: 401checked: Oct 14, 2026, 2:26 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 34msstatus code: 401checked: Oct 14, 2026, 2:12 PM 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
      Checks passinglatency: 118msstatus code: 401checked: Oct 14, 2026, 2:11 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 400msstatus code: 401checked: Oct 14, 2026, 2:06 PM 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
      Checks passinglatency: 349msstatus code: 401checked: Oct 14, 2026, 1:50 PM 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
      Checks passinglatency: 525msstatus code: 401checked: Oct 14, 2026, 1:35 PM 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 probe events

Webex Contact Center Enterprise: Intermittent Agent Desktops and Console access failures in the US region, 6h 11mdeclared on their status page2026-10-11
Webex Calling: Inbound call failures impacting Cisco Calling Plan users in the Canada region, 2h 34mdeclared on their status page2026-10-10
Webex Contact Center: Callers may experience IVR delays and intermittent failures connecting to agents in the US region, 1h 5mdeclared on their status page2026-10-09
Developer API: Users may be unable to load the My Apps page in Developer Portal, 50mdeclared on their status page2026-10-07
Collaboration Control Hub: Data errors in Workspaces CSV files exported for bulk management, 6h 4mdeclared on their status page2026-10-02
Developer API: Users may be unable to load the My Apps page in Developer Portal, 12h 29mdeclared on their status page2026-10-01
Webex Services: Multiple services degradation in APAC region, 24mdeclared on their status page2026-09-30
Webex Contact Center: Some users may experience dead air or one-way audio, 3h 10mdeclared on their status page2026-09-30

check 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 check readings and Webex's own claim at the time, side by side.

Full check history for Webex: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Webex uptime by RealUptime's checksLive, from this page's own readings.
[![Webex uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Webex down?", https://realuptime.io/outages/webex. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://webexapis.com/v1/people/me
secondary
https://status.webex.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: webexapis.com

RealUptime is not affiliated with Webex; the name identifies what we checked, 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. At least one endpoint we check for Webex is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.