Skip to content

Outage tracker / Zoom

Is Zoom down?

I'm having a problem

Operationalchecked 6 minutes ago

We reached Zoom from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Zoom answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Zoom (since Aug 8, 2026).

Zoom reports an active incident: "Service Degradation Affecting Customer Using Polycom Devices Going Offline" (minor incident, since Sep 25, 2026, 5:45 PM UTC). That is their claim, not our measurement: our probes are currently reaching Zoom, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

Email me the next time we see Zoom go down

Measured by our own probes from ten regions, not Zoom's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East605 msOperational
US-West476 msOperational
Europe446 msOperational
Asia-Pacific154 msOperational
US-Central294 msOperational
Canada223 msOperational
UK410 msOperational
Southeast Asia295 msOperational
Australia904 msOperational
South America187 msOperational
their status pagetheir claim, not our reading

Zoom reports: Minor incident (“Partially Degraded Service”)

from Zoom's own status page, checked Oct 5, 2026, 7:58 PM UTC

Zoom reports an active incident: Service Degradation Affecting Customer Using Polycom Devices Going Offline (minor incident, since Sep 25, 2026, 5:45 PM UTC)

Zoom's status page reports Partially Degraded Service. Our probes are currently reaching Zoom successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Zoom's own component breakdown, as they publish it

  • CalendarOperational
  • SlackOperational
  • Video SDKOperational
  • Voice AgentOperational
  • Voice AgentOperational
  • Voice AgentOperational
  • Voice AgentOperational
  • Voice AgentOperational
  • Voice AgentOperational
  • Web Portal (Admin/Users/Provisioning/Dashboard & Reporting)Operational
  • Web SDKOperational
  • Zoom AICOperational
  • Zoom BlogOperational
  • Zoom ChatOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Contact CenterOperational
  • Zoom Dashboard & ReportingOperational
  • Zoom MeetingsOperational
  • Zoom PhoneOperational
  • Zoom PhoneOperational
  • Zoom PhoneUnder maintenance
  • Zoom PhoneOperational
  • Zoom PhoneOperational
  • Zoom PhoneOperational
  • Zoom PhoneOperational
  • Zoom Revenue AcceleratorOperational
  • Zoom RoomsOperational
  • Zoom Virtual AgentOperational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Calling (Inbound/Outbound)Operational
  • Chat AgentOperational
  • Chat AgentOperational
  • Chat AgentOperational
  • Chat AgentOperational
  • Chat AgentOperational
  • Chat AgentOperational
  • Chat Messaging: Peer To Peer Messaging, History, Channels, Mobile Push NotificationsOperational
  • CoBrowse SDKOperational
  • DealsOperational
  • Download Center & ClientsOperational
  • Knowledge BaseOperational
  • MailOperational
  • Microsoft TeamsOperational
  • REST APIOperational
  • Third Party Contact Center Integration (Five9/Twilio/Talkdesk/inContact/Genesys)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice (Inbound/Outbound)Operational
  • Voice AgentOperational
  • Web Portal (Admin/Users/Provisioning)Operational
  • Zoom Rooms Digital SignageOperational
  • Chat AgentOperational
  • ChatbotOperational
  • Desktop Client (Supervisors/Agents)Operational
  • Devices (Softphones/Deskphones)Operational
  • Devices (Softphones/Deskphones)Operational
  • Devices (Softphones/Deskphones)Operational
  • Devices (Softphones/Deskphones)Operational
  • Devices (Softphones/Deskphones)Operational
  • Devices (Softphones/Deskphones)Operational
  • Email NotificationsOperational
  • Google WorkspaceOperational
  • Integration (API/Webhook)Operational
  • MarketplaceOperational
  • SMS/MMS (Inbound/Outbound)Operational
  • User Profiles and PresenceOperational
  • Video (Inbound/Outbound)Operational
  • Video (Inbound/Outbound)Operational
  • Video (Inbound/Outbound)Operational
  • Video (Inbound/Outbound)Operational
  • Video (Inbound/Outbound)Operational
  • Video (Inbound/Outbound)Operational
  • Zoom AI Services APIOperational
  • Zoom ClipsOperational
  • Zoom SchedulerOperational
  • BYOC - PremisesOperational
  • BYOC - PremisesOperational
  • BYOC - PremisesOperational
  • BYOC - PremisesOperational
  • BYOC - PremisesOperational
  • BYOC - PremisesOperational
  • ConversationsOperational
  • Devices (Softphones/Deskphones)Operational
  • File Transfers: File, Video, Pictures, VoiceOperational
  • Web PortalOperational
  • WebhooksOperational
  • Zoom Workspace ReservationOperational

These are Zoom's components, named and scored by Zoom. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Zoom's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Zoom response time, by region

US-East
595msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 392ms2026-09-07 UTC: p95 401ms2026-09-08 UTC: p95 388ms2026-09-09 UTC: p95 466ms2026-09-10 UTC: p95 452ms2026-09-11 UTC: p95 519ms2026-09-12 UTC: p95 520ms2026-09-13 UTC: p95 455ms2026-09-14 UTC: p95 539ms2026-09-15 UTC: p95 476ms2026-09-16 UTC: p95 533ms2026-09-17 UTC: p95 485ms2026-09-18 UTC: p95 604ms2026-09-19 UTC: p95 481ms2026-09-20 UTC: p95 549ms2026-09-21 UTC: p95 758ms2026-09-22 UTC: p95 653ms2026-09-23 UTC: p95 787ms2026-09-24 UTC: p95 729ms2026-09-25 UTC: p95 594ms2026-09-26 UTC: p95 736ms2026-09-27 UTC: p95 640ms2026-09-28 UTC: p95 675ms2026-09-29 UTC: p95 584ms2026-09-30 UTC: p95 624ms2026-10-01 UTC: p95 552ms2026-10-02 UTC: p95 780ms2026-10-03 UTC: p95 555ms2026-10-04 UTC: p95 520ms2026-10-05 UTC: p95 595ms
Sep 6Sep 20Oct 5
US-West
635msp95 · 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-06 UTC: p95 757ms2026-09-07 UTC: p95 785ms2026-09-08 UTC: p95 703ms2026-09-09 UTC: p95 483ms2026-09-10 UTC: p95 508ms2026-09-11 UTC: p95 542ms2026-09-12 UTC: p95 560ms2026-09-13 UTC: p95 572ms2026-09-14 UTC: p95 485ms2026-09-15 UTC: p95 844ms2026-09-16 UTC: p95 771ms2026-09-17 UTC: p95 687ms2026-09-18 UTC: p95 875ms2026-09-19 UTC: p95 911ms2026-09-20 UTC: p95 900ms2026-09-21 UTC: p95 706ms2026-09-22 UTC: p95 686ms2026-09-23 UTC: p95 700ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 847ms2026-09-27 UTC: p95 845ms2026-09-28 UTC: p95 825ms2026-09-29 UTC: p95 706ms2026-09-30 UTC: p95 802ms2026-10-01 UTC: p95 587ms2026-10-02 UTC: p95 663ms2026-10-03 UTC: p95 569ms2026-10-04 UTC: p95 501ms2026-10-05 UTC: p95 635ms
Sep 6Sep 20Oct 5
Europe
398msp95 · 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-06 UTC: p95 884ms2026-09-07 UTC: p95 914ms2026-09-08 UTC: p95 878ms2026-09-09 UTC: p95 836ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 924ms2026-09-12 UTC: p95 850ms2026-09-13 UTC: p95 824ms2026-09-14 UTC: p95 871ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 998ms2026-09-17 UTC: p95 572ms2026-09-18 UTC: p95 621ms2026-09-19 UTC: p95 635ms2026-09-20 UTC: p95 554ms2026-09-21 UTC: p95 576ms2026-09-22 UTC: p95 600ms2026-09-23 UTC: p95 573ms2026-09-24 UTC: p95 679ms2026-09-25 UTC: p95 556ms2026-09-26 UTC: p95 690ms2026-09-27 UTC: p95 595ms2026-09-28 UTC: p95 606ms2026-09-29 UTC: p95 691ms2026-09-30 UTC: p95 881ms2026-10-01 UTC: p95 614ms2026-10-02 UTC: p95 391ms2026-10-03 UTC: p95 981ms2026-10-04 UTC: p95 651ms2026-10-05 UTC: p95 398ms
Sep 6Sep 20Oct 5
Asia-Pacific
644msp95 · 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-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 773ms2026-09-18 UTC: p95 914ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 839ms2026-09-21 UTC: p95 735ms2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 907ms2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 858ms2026-10-02 UTC: p95 950ms2026-10-03 UTC: p95 950ms2026-10-04 UTC: p95 965ms2026-10-05 UTC: p95 644ms
Sep 6Sep 20Oct 5
US-Central
307msp95 · 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-06 UTC: p95 552ms2026-09-07 UTC: p95 827ms2026-09-08 UTC: p95 844ms2026-09-09 UTC: p95 896ms2026-09-10 UTC: p95 828ms2026-09-11 UTC: p95 756ms2026-09-12 UTC: p95 865ms2026-09-13 UTC: p95 827ms2026-09-14 UTC: p95 838ms2026-09-15 UTC: p95 824ms2026-09-16 UTC: p95 794ms2026-09-17 UTC: p95 847ms2026-09-18 UTC: p95 841ms2026-09-19 UTC: p95 859ms2026-09-20 UTC: p95 834ms2026-09-21 UTC: p95 802ms2026-09-22 UTC: p95 752ms2026-09-23 UTC: p95 640ms2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 895ms2026-09-26 UTC: p95 861ms2026-09-27 UTC: p95 849ms2026-09-28 UTC: p95 901ms2026-09-29 UTC: p95 498ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 673ms2026-10-02 UTC: p95 776ms2026-10-03 UTC: p95 362ms2026-10-04 UTC: p95 467ms2026-10-05 UTC: p95 307ms
Sep 6Sep 20Oct 5
Canada
419msp95 · 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-06 UTC: p95 572ms2026-09-07 UTC: p95 524ms2026-09-08 UTC: p95 653ms2026-09-09 UTC: p95 849ms2026-09-10 UTC: p95 880ms2026-09-11 UTC: p95 910ms2026-09-12 UTC: p95 851ms2026-09-13 UTC: p95 863ms2026-09-14 UTC: p95 903ms2026-09-15 UTC: p95 880ms2026-09-16 UTC: p95 776ms2026-09-17 UTC: p95 667ms2026-09-18 UTC: p95 828ms2026-09-19 UTC: p95 849ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 808ms2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 672ms2026-09-28 UTC: p95 696ms2026-09-29 UTC: p95 735ms2026-09-30 UTC: p95 651ms2026-10-01 UTC: p95 499ms2026-10-02 UTC: p95 582ms2026-10-03 UTC: p95 649ms2026-10-04 UTC: p95 701ms2026-10-05 UTC: p95 419ms
Sep 6Sep 20Oct 5
UK
684msp95 · 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-06 UTC: p95 527ms2026-09-07 UTC: p95 422ms2026-09-08 UTC: p95 537ms2026-09-09 UTC: p95 375ms2026-09-10 UTC: p95 665ms2026-09-11 UTC: p95 670ms2026-09-12 UTC: p95 698ms2026-09-13 UTC: p95 550ms2026-09-14 UTC: p95 602ms2026-09-15 UTC: p95 623ms2026-09-16 UTC: p95 572ms2026-09-17 UTC: p95 402ms2026-09-18 UTC: p95 427ms2026-09-19 UTC: p95 554ms2026-09-20 UTC: p95 549ms2026-09-21 UTC: p95 547ms2026-09-22 UTC: p95 547ms2026-09-23 UTC: p95 511ms2026-09-24 UTC: p95 553ms2026-09-25 UTC: p95 540ms2026-09-26 UTC: p95 605ms2026-09-27 UTC: p95 468ms2026-09-28 UTC: p95 392ms2026-09-29 UTC: p95 703ms2026-09-30 UTC: p95 665ms2026-10-01 UTC: p95 481ms2026-10-02 UTC: p95 353ms2026-10-03 UTC: p95 505ms2026-10-04 UTC: p95 946ms2026-10-05 UTC: p95 684ms
Sep 6Sep 20Oct 5
Southeast Asia
537msp95 · 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-06 UTC: p95 2.0s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 661ms2026-10-02 UTC: p95 848ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 537ms
Sep 6Sep 20Oct 5
Australia
942msp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 2.3s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 730ms2026-09-28 UTC: p95 820ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 925ms2026-10-04 UTC: p95 650ms2026-10-05 UTC: p95 942ms
Sep 6Sep 20Oct 5
South America
339msp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 980ms2026-09-08 UTC: p95 925ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 949ms2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 918ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 641ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 339ms
Sep 6Sep 20Oct 5

Is it Zoom, 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 Zoom -- it cannot diagnose Zoom's own systems.

What we measured, function by function

Zoom 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 web 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.

  • WebprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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: 605msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Zoom normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 476msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Zoom normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 294msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Zoom normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 223msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Zoom normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 187msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Zoom normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 446msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Zoom normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 410msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Zoom 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: 154msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Zoom normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 295msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Zoom normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 904msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Zoom 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 Zoom, 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 started counting reports for Zoom on September 14, 2026.

Recent outages

Service Degradation Affecting Zoom Rooms Management and Workspaces Management in SA01., 1h 22mdeclared on their status page2026-10-04
Service Degradation Affected Inbound and Outbound Calls of Zoom Phone and Contact Center in North America Region, 15mdeclared on their status page2026-10-04
Service degradation affecting Developer Documentation Website, 1h 55mdeclared on their status page2026-10-03
Service Degradation Affected Incoming and Outgoing Calls of Zoom Contact Center, Virtual Agents, Mail, Calendar, Meetings, Cloud Meeting Recordings, Webinars and Events, 1h 45mdeclared on their status page2026-10-01
Service Degradation Affecting Zoom for Google Workspace Add-On, 4h 29mdeclared on their status page2026-10-01
Service Degradation Affecting Zoom Phone in the EU01 cluster., 14mdeclared on their status page2026-09-30
Service Degradation Affecting Zoom Canvas, My Notes, Sheets, In App Purchases, Billing Hub, and Clips., 1h 20mdeclared on their status page2026-09-28
Service Degradation Affecting Customer Using Polycom Devices Going Offlinedeclared on their status page2026-09-25

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Zoom since August 8, 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 Zoom covering any window you pick, with our measurements and Zoom's own claim at the time, side by side.

Full availability history for Zoom: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Zoom uptime measured by RealUptimeLive, from this page's own readings.
[![Zoom uptime measured by RealUptime](https://realuptime.io/outages/zoom/badge.svg?days=30)](https://realuptime.io/outages/zoom)
<a href="https://realuptime.io/outages/zoom"><img src="https://realuptime.io/outages/zoom/badge.svg?days=30" alt="Zoom 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 Zoom's SLA implies, from our measurement

At or above your target

We measured none of downtime for Zoom over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 Zoom'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://www.zoom.com/
secondaryfunctional: auth surface
https://api.zoom.us/v2/users
secondary
https://www.zoomstatus.com/
RealUptime is not affiliated with Zoom; the name identifies what we measured, and nothing here speaks for Zoom's own team. We send a single web request to Zoom from 10 regions on our own schedule and time the response. We do not see inside Zoom's systems, do not use an account or real transaction, and are not the same signal Zoom's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Zoom is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.