Uptime Report Research · Zoom status record, as of Nov 12, 2026

Zoom Outage History: 1,027 Incidents Since 2015, and 2026 Is the Busiest Year Yet

Zoom outage history, as of November 12, 2026: Zoom’s status page lists 1,027 incidents since March 2015, and 225 of them fell between January 1 and November 11, 2026, up 53% on the same stretch of 2025. Zoom Contact Center (54) and Zoom Phone (50) now break more often than Meetings (36). The median incident lasts 1 h 29 min.

The pages ranking for this query either show the last few incidents, count a single slice of time, or link back to Zoom. We downloaded the full record instead: all 2,236 entries on Zoom’s History tab, one JSON file per entry, then removed 1,205 scheduled maintenance windows and 4 no-impact notices. What remains is every unplanned incident Zoom has posted, with the components it marked, the status it gave each one, and when it opened and closed. We then checked it against the separate uptime page Zoom runs at uptime.zoom.us, which tells a very different story.

1,027unplanned incidents, 2015 to Nov 12, 2026
225in 2026 to Nov 11, vs 147 in 2025 and 114 in 2024
40ever marked partial or major outage; 1 in 2026
11 of 13months at 100% for Meetings on Zoom’s uptime page

Key findings

  • Zoom posted 225 unplanned incidents from January 1 to November 11, 2026, its highest count for that stretch in the 12 years of the record (147 in 2025, 114 in 2024, 64 in 2020).
  • Voice and customer service products now lead: 92 of the 225 incidents in 2026 touched Zoom Contact Center, Zoom Phone or Zoom Virtual Agent, against 36 for Zoom Meetings.
  • AI Companion components appear on 32 incidents in 2026, up from 22 in the same months of 2025; the first was October 19, 2023.
  • Zoom rarely uses its outage labels: from 2023 to 2026, 7 of 679 incidents reached partial or major outage on any component, while 469 stopped at “degraded performance”.
  • 33% of incidents started between 10 AM and 3 PM US Eastern, and Monday has 196 incidents against 78 on Saturday.
  • Zoom’s uptime page shows Zoom Meetings at 100% in 11 of the last 13 months and flags 2 days in a year, while the status page lists 21 incidents on the core Meetings component over the same period.
  • Only 2 of 1,027 incidents carry a written root cause section on the status page; the newest is the April 16, 2025 zoom.us domain block.

Has Zoom been down recently? The last ten incidents

Date (ET) Zoom’s title Product Worst status Length
Nov 12, 2026 Service Degradation Affecting Microsoft Integrations due to an underlying vendor issue. Developer Platform and SDKs, Mail and Calendar, Website and web portal Degraded performance ongoing
Nov 11, 2026 Service Degradation Affecting Outbound SMS Messages for a subset of users in the US region Zoom Contact Center, Zoom Meetings, Zoom Phone Degraded performance 2 h 24 min
Nov 10, 2026 Service Degradation Affecting Zoom Conference Room Connector Services Endpoints in the AMS region. Room Connector Degraded performance 2 h 35 min
Nov 9, 2026 Service Degradation Affecting a subset of users with ZVA and ZoomMate AI Companion, Zoom Virtual Agent No component status under 1 min
Nov 8, 2026 Service Degradation Affecting Zoom Inbound SMS Service in the AU region Zoom Contact Center, Zoom Phone Degraded performance 1 h
Nov 5, 2026 Service Degradation Affecting Zoom Mail, Calendar and Scheduler. Mail and Calendar Degraded performance 1 h 37 min
Nov 3, 2026 Service Degradation Affecting Outbound MMS Services in the US region Zoom Phone Degraded performance 7 h 51 min
Oct 28, 2026 Service Degradation Affecting the Evaluations Acknowledge Button in Zoom Quality Management in the US Region Zoom Contact Center Degraded performance 16 h 36 min
Oct 23, 2026 Service Degradation Affecting Multiple Zoom Services AI Companion, Team Chat, Zoom Contact Center, Zoom Meetings Degraded performance 46 min
Oct 22, 2026 Service Degradation Affecting Zoom Meetings Services in the US. Zoom Meetings Degraded performance 22 h 19 min

Length runs from the earlier of Zoom’s created and started times to its resolved time. “Ongoing” means the incident was still open at our pull on November 12, 2026. Dates link to Zoom’s incident page.

Zoom posted 18 incidents in the 30 days to Nov 12, 2026. The newest, about Microsoft integrations and blamed on an underlying vendor, was still open when we pulled the data. None of the last ten reached partial or major outage on any component.

Which Zoom services break most: the component leaderboard

All incidents, 2015 to 20262026, Jan 1 to Nov 11Zoom MeetingsZoom Meetings: 226 incidents since 2015, 15 at partial or major outage226 (15)Zoom Meetings: 36 incidents in 2026 to November 11, rank 336Zoom PhoneZoom Phone: 203 incidents since 2015, 16 at partial or major outage203 (16)Zoom Phone: 50 incidents in 2026 to November 11, rank 250Website and web portalWebsite and web portal: 137 incidents since 2015, 2 at partial or major outage137 (2)Website and web portal: 19 incidents in 2026 to November 11, rank 619Zoom Contact CenterZoom Contact Center: 107 incidents since 2015, 3 at partial or major outage107 (3)Zoom Contact Center: 54 incidents in 2026 to November 11, rank 154AI CompanionAI Companion: 76 incidents since 2015, 0 at partial or major outage76AI Companion: 32 incidents in 2026 to November 11, rank 432Docs, Notes, Clips and HubDocs, Notes, Clips and Hub: 55 incidents since 2015, 0 at partial or major outage55Docs, Notes, Clips and Hub: 28 incidents in 2026 to November 11, rank 528Zoom WebinarsZoom Webinars: 53 incidents since 2015, 4 at partial or major outage53 (4)Zoom Webinars: 3 incidents in 2026 to November 11, rank 163Developer Platform and SDKsDeveloper Platform and SDKs: 49 incidents since 2015, 2 at partial or major outage49 (2)Developer Platform and SDKs: 12 incidents in 2026 to November 11, rank 912Team ChatTeam Chat: 48 incidents since 2015, 1 at partial or major outage48 (1)Team Chat: 11 incidents in 2026 to November 11, rank 1111Zoom Rooms and WorkspacesZoom Rooms and Workspaces: 36 incidents since 2015, 0 at partial or major outage36Zoom Rooms and Workspaces: 15 incidents in 2026 to November 11, rank 815Room ConnectorRoom Connector: 31 incidents since 2015, 3 at partial or major outage31 (3)Room Connector: 4 incidents in 2026 to November 11, rank 144OtherOther: 30 incidents since 2015, 1 at partial or major outage30 (1)Other: 9 incidents in 2026 to November 11, rank 129Mail and CalendarMail and Calendar: 28 incidents since 2015, 0 at partial or major outage28Mail and Calendar: 12 incidents in 2026 to November 11, rank 1012Zoom Virtual AgentZoom Virtual Agent: 27 incidents since 2015, 0 at partial or major outage27Zoom Virtual Agent: 16 incidents in 2026 to November 11, rank 716Zoom WhiteboardZoom Whiteboard: 24 incidents since 2015, 0 at partial or major outage24Zoom Whiteboard: 7 incidents in 2026 to November 11, rank 137Zoom SupportZoom Support: 17 incidents since 2015, 0 at partial or major outage17Zoom Support: 4 incidents in 2026 to November 11, rank 154Zoom EventsZoom Events: 7 incidents since 2015, 1 at partial or major outage7 (1)Zoom Events: 2 incidents in 2026 to November 11, rank 172

Incidents that name at least one component in each product family. One incident can touch several families, so rows add up to more than 1,027. Red bar and bracketed number: incidents where Zoom set a component in that family to partial or major outage. 198 incidents name no component (2 in 2026); most predate component tagging. AI Companion counts components Zoom names AIC, AI Companion, Zoom AI or ZoomMate, wherever they sit on the page.

Across the whole record, Zoom Meetings leads with 226 incidents, followed by Zoom Phone with 203 and the website and web portal with 137. The 2026 column looks different. Zoom Contact Center has 54 incidents so far this year, against 26 in the same months of 2025, and Zoom Phone 50 against 41. Of the 80 Phone or Contact Center incidents in 2026, 65 name a region in the title or in a regional component, and 44 titles mention calls, SMS, PSTN, carriers, dial-in or audio. Meetings has 36, against 31 a year earlier. Webinars appears on 3 incidents in 2026 and was last named on Oct 13, 2026.

Product family Since 2015 2026 to Nov 11 2025 to Nov 11 Partial or major outage Median length
Zoom Meetings 226 36 31 15 2 h 4 min
Zoom Phone 203 50 41 16 1 h 50 min
Website and web portal 137 19 22 2 2 h 21 min
Zoom Contact Center 107 54 26 3 1 h 7 min
AI Companion 76 32 22 0 1 h 34 min
Docs, Notes, Clips and Hub 55 28 17 0 1 h 5 min
Zoom Webinars 53 3 3 4 1 h 37 min
Developer Platform and SDKs 49 12 5 2 2 h 17 min
Team Chat 48 11 12 1 1 h 47 min
Zoom Rooms and Workspaces 36 15 8 0 1 h 51 min
Room Connector 31 4 3 3 1 h 29 min
Other 30 9 3 1 2 h 12 min
Mail and Calendar 28 12 8 0 1 h 47 min
Zoom Virtual Agent 27 16 8 0 1 h 1 min
Zoom Whiteboard 24 7 6 0 1 h 23 min
Zoom Support 17 4 0 0 1 h 25 min
Zoom Events 7 2 2 1 1 h 45 min

The 15 components Zoom names most often

Component, as Zoom names it Incidents since 2015 2026
Zoom Meetings (core service) 133 17
Zoom Website – Web Portal 60 5
Zoom Video Webinars 46 0
Zoom Website – Zoom Dashboard & Reporting 44 5
Zoom Phone 33 0
Zoom Meetings – Zoom AIC 31 13
Zoom Chat 23 6
Zoom Developer Platform – Marketplace 23 8
Zoom Phone – APAC – Calling (Inbound/Outbound) 23 7
Zoom Website – Integrations/Calendar/Plug-In/Add-In 23 5
Zoom Mail – Mail 23 9
Zoom Clips 23 7
Zoom Rooms 21 10
Zoom Phone – EMEA – Calling (Inbound/Outbound) 20 4
Zoom Website – Web Client 19 0

Zoom renamed several components over the years (for example “Zoom Video Webinars”, and the plain “Zoom Meetings” component before it moved into a group). We list names as they appear in each incident, so a renamed component can appear twice. Region is part of the name for Phone, Contact Center and Virtual Agent.

Region shows up in two places. For Phone, Contact Center and Virtual Agent, Zoom splits components by region; across the record, 72 incidents name a Global component, 67 North America, 35 EMEA and 29 APAC. Titles say more: of 398 incidents since January 2025, 206 name a place in the title.

Region in component name Since 2015 2026
Global 72 27
North America 67 33
EMEA 35 12
APAC 29 8
Australia 19 9
Latin America 17 1
Japan 10 5
Hong Kong/China 8 2
Place named in title, 2025 to 2026 Incidents Share
North America 89 22%
Europe/EMEA 35 9%
APAC (other) 26 7%
Middle East 23 6%
Australia 20 5%
Japan 16 4%
India 8 2%
Latin America 2 1%

Title matches use place words such as Europe, EU, EMEA, Japan, Australia, Saudi Arabia, India, US or Canada. An incident can name several places.

When Zoom outages happen: the clock chart

12a: 48 incidents started12a1a: 28 incidents started2a: 42 incidents started3a: 32 incidents started3a4a: 42 incidents started5a: 33 incidents started6a: 36 incidents started6a7a: 29 incidents started8a: 27 incidents started9a: 29 incidents started9a10a: 57 incidents started11a: 74 incidents started12p: 81 incidents started12p1p: 63 incidents started2p: 62 incidents started3p: 47 incidents started3p4p: 57 incidents started5p: 34 incidents started6p: 35 incidents started6p7p: 33 incidents started8p: 36 incidents started9p: 31 incidents started9p10p: 30 incidents started11p: 41 incidents startedUS Eastern8100:00: 36 incidents started00:0001:00: 28 incidents started02:00: 38 incidents started03:00: 32 incidents started03:0004:00: 48 incidents started05:00: 37 incidents started06:00: 39 incidents started06:0007:00: 33 incidents started08:00: 39 incidents started09:00: 36 incidents started09:0010:00: 34 incidents started11:00: 34 incidents started12:00: 25 incidents started12:0013:00: 27 incidents started14:00: 45 incidents started15:00: 71 incidents started15:0016:00: 76 incidents started17:00: 70 incidents started18:00: 69 incidents started18:0019:00: 46 incidents started20:00: 48 incidents started21:00: 52 incidents started21:0022:00: 29 incidents started23:00: 35 incidents startedUTC76

Each wedge is one hour of the day; its length is the number of incidents that started in that hour, 1,027 in all. Start is the earlier of Zoom’s created and started times. Left: US Eastern (America/New_York, with daylight saving). Right: UTC. Midnight at the top.

Zoom incidents follow the US working day. 33% began between 10 AM and 3 PM Eastern, five hours that are 21% of the day, and the peak is 12 PM ET with 81. In UTC the busiest hour is 16:00, and 28% of incidents began between 15:00 and 18:59 UTC. Weekdays from 9 AM to 5 PM Eastern hold 42% of incidents in 24% of the hours in a week. The overnight hours are not empty: 22% started between midnight and 6 AM Eastern, and 24% in 2026. The 2026 peak hour is the same.

MondayMonday: 196 incidents started (US Eastern)196TuesdayTuesday: 175 incidents started (US Eastern)175WednesdayWednesday: 178 incidents started (US Eastern)178ThursdayThursday: 187 incidents started (US Eastern)187FridayFriday: 137 incidents started (US Eastern)137SaturdaySaturday: 78 incidents started (US Eastern)78SundaySunday: 76 incidents started (US Eastern)76

Weekday of start in US Eastern time. Saturday and Sunday together: 15%.

This is when Zoom opened or dated the incident, not when the fault began for every user. Daytime clustering mixes two things we can’t separate from the record: more change and load during the working day, and more people noticing and reporting problems while they are on calls.

Zoom outage history by year and month

JanFebMarAprMayJunJulAugSepOctNovDecYear2015January 2015: 0 incidentsFebruary 2015: 0 incidentsMarch 2015: 1 incidents1April 2015: 4 incidents4May 2015: 2 incidents2June 2015: 0 incidentsJuly 2015: 1 incidents1August 2015: 4 incidents4September 2015: 2 incidents2October 2015: 0 incidentsNovember 2015: 0 incidentsDecember 2015: 0 incidents142016January 2016: 0 incidentsFebruary 2016: 2 incidents2March 2016: 1 incidents1April 2016: 1 incidents1May 2016: 1 incidents1June 2016: 1 incidents1July 2016: 3 incidents3August 2016: 0 incidentsSeptember 2016: 0 incidentsOctober 2016: 0 incidentsNovember 2016: 1 incidents1December 2016: 0 incidents102017January 2017: 0 incidentsFebruary 2017: 1 incidents1March 2017: 0 incidentsApril 2017: 0 incidentsMay 2017: 2 incidents2June 2017: 1 incidents1July 2017: 2 incidents2August 2017: 0 incidentsSeptember 2017: 2 incidents2October 2017: 1 incidents1November 2017: 2 incidents2December 2017: 0 incidents112018January 2018: 0 incidentsFebruary 2018: 5 incidents5March 2018: 4 incidents4April 2018: 0 incidentsMay 2018: 1 incidents1June 2018: 0 incidentsJuly 2018: 0 incidentsAugust 2018: 2 incidents2September 2018: 2 incidents2October 2018: 2 incidents2November 2018: 2 incidents2December 2018: 1 incidents1192019January 2019: 1 incidents1February 2019: 2 incidents2March 2019: 1 incidents1April 2019: 2 incidents2May 2019: 0 incidentsJune 2019: 3 incidents3July 2019: 3 incidents3August 2019: 1 incidents1September 2019: 3 incidents3October 2019: 3 incidents3November 2019: 2 incidents2December 2019: 1 incidents1222020January 2020: 1 incidents1February 2020: 2 incidents2March 2020: 23 incidents23April 2020: 4 incidents4May 2020: 5 incidents5June 2020: 5 incidents5July 2020: 2 incidents2August 2020: 7 incidents7September 2020: 8 incidents8October 2020: 5 incidents5November 2020: 10 incidents10December 2020: 1 incidents1732021January 2021: 9 incidents9February 2021: 4 incidents4March 2021: 10 incidents10April 2021: 5 incidents5May 2021: 8 incidents8June 2021: 10 incidents10July 2021: 7 incidents7August 2021: 7 incidents7September 2021: 12 incidents12October 2021: 4 incidents4November 2021: 6 incidents6December 2021: 15 incidents15972022January 2022: 4 incidents4February 2022: 5 incidents5March 2022: 8 incidents8April 2022: 3 incidents3May 2022: 4 incidents4June 2022: 9 incidents9July 2022: 10 incidents10August 2022: 16 incidents16September 2022: 15 incidents15October 2022: 6 incidents6November 2022: 9 incidents9December 2022: 13 incidents131022023January 2023: 11 incidents11February 2023: 15 incidents15March 2023: 18 incidents18April 2023: 18 incidents18May 2023: 15 incidents15June 2023: 19 incidents19July 2023: 10 incidents10August 2023: 13 incidents13September 2023: 4 incidents4October 2023: 9 incidents9November 2023: 15 incidents15December 2023: 6 incidents61532024January 2024: 14 incidents14February 2024: 13 incidents13March 2024: 14 incidents14April 2024: 10 incidents10May 2024: 14 incidents14June 2024: 13 incidents13July 2024: 11 incidents11August 2024: 10 incidents10September 2024: 10 incidents10October 2024: 5 incidents5November 2024: 9 incidents9December 2024: 5 incidents51282025January 2025: 11 incidents11February 2025: 14 incidents14March 2025: 11 incidents11April 2025: 13 incidents13May 2025: 13 incidents13June 2025: 13 incidents13July 2025: 9 incidents9August 2025: 21 incidents21September 2025: 17 incidents17October 2025: 21 incidents21November 2025: 12 incidents12December 2025: 16 incidents161712026January 2026: 28 incidents28February 2026: 20 incidents20March 2026: 21 incidents21April 2026: 16 incidents16May 2026: 22 incidents22June 2026: 22 incidents22July 2026: 24 incidents24August 2026: 16 incidents16September 2026: 26 incidents26October 2026: 25 incidents25November 2026: 7 incidents (to Nov 12)7December 2026: 0 incidents227

Unplanned incidents by month of start (UTC). November 2026 runs to the 12th. Darker means more incidents.

Year Incidents Jan 1 to Nov 11 Worst status: degraded Partial or major outage Median length Vendor, carrier or third party named
2015 14 14 0 2 2 h 10 min 1
2016 10 9 0 2 1 h 33 min 3
2017 11 11 0 0 3 h 40 min 4
2018 19 16 3 0 8 h 54 min 6
2019 22 19 4 7 1 h 39 min 4
2020 73 64 41 14 2 h 17 min 7
2021 97 77 70 5 2 h 13 min 18
2022 102 84 76 2 1 h 43 min 19
2023 153 138 112 0 1 h 16 min 19
2024 128 114 101 0 1 h 18 min 5
2025 171 147 112 7 1 h 9 min 26
2026* 227 225 144 1 1 h 1 min 31

*2026 is partial. The like-for-like column compares the same calendar stretch each year. The vendor column counts incidents whose updates mention a vendor, carrier, third party or upstream provider.

The count rose from 22 in 2019 to 73 in 2020, then to 153 in 2023 and 171 in 2025. The page lists far fewer entries before 2019 (54 in four years), so treat those years as a thin record rather than a calm one. The 2026 jump is real on Zoom’s own terms: the like-for-like count is 225 against 147. More products also means more components to post about: the status page now has 306 components, and three families on our leaderboard first appear late: AI Companion in October 2023, Docs, Notes and Clips in November 2023 and Virtual Agent in March 2024. Together they account for 71 incidents in 2026.

Zoom rarely marks anything as an outage now

20192019: 11 of 22 incidents, worst component status no component status2019: 4 of 22 incidents, worst component status degraded performance18%2019: 6 of 22 incidents, worst component status partial outage2019: 1 of 22 incidents, worst component status major outage720202020: 18 of 73 incidents, worst component status no component status2020: 41 of 73 incidents, worst component status degraded performance56%2020: 13 of 73 incidents, worst component status partial outage2020: 1 of 73 incidents, worst component status major outage1420212021: 22 of 97 incidents, worst component status no component status2021: 70 of 97 incidents, worst component status degraded performance72%2021: 3 of 97 incidents, worst component status partial outage2021: 2 of 97 incidents, worst component status major outage520222022: 24 of 102 incidents, worst component status no component status2022: 76 of 102 incidents, worst component status degraded performance75%2022: 2 of 102 incidents, worst component status major outage220232023: 41 of 153 incidents, worst component status no component status2023: 112 of 153 incidents, worst component status degraded performance73%020242024: 27 of 128 incidents, worst component status no component status2024: 101 of 128 incidents, worst component status degraded performance79%020252025: 53 of 171 incidents, worst component status no component status2025: 112 of 171 incidents, worst component status degraded performance65%2025: 6 of 171 incidents, worst component status partial outage620262026: 82 of 227 incidents, worst component status no component status2026: 144 of 227 incidents, worst component status degraded performance63%2026: 1 of 227 incidents, worst component status partial outage1outages

no component status degraded performance partial outage major outage. Red number at right: incidents with a component set to partial or major outage.

Atlassian Statuspage, which runs Zoom’s page, gives each component five states: operational, under maintenance, degraded performance, partial outage and major outage. In 2020 Zoom set a component to partial or major outage on 14 incidents. From 2023 to 2024 it did so on none, and in 2026 on 1: the January 28 WhatsApp integration fault in Contact Center. Even the Dec 16, 2025 multi-region event, which Zoom says hit inbound traffic in data centers in Europe, India, Japan, Saudi Arabia and Australia before North America, was a partial outage. Zoom’s titles changed in step: 160 of 227 titles in 2026 open with “Service Degradation”, against 6 in all of 2025. A monitoring rule that waits for “major outage” on Zoom’s page would have fired 6 times since 2015.

The biggest Zoom outages

Zoom rates each incident none, minor, major or critical. 40 carry major or critical, and only 8 of those are from 2023 on.

Date (ET) Zoom’s rating Zoom’s title Product Length
Jan 28, 2026 Major Partial Outage Affecting WhatsApp Integration Zoom Contact Center 3 h 32 min
Dec 16, 2025 Major Issue with multiple Zoom Services in multiple regions Zoom Contact Center, Zoom Meetings, Zoom Phone 4 h 19 min
Dec 16, 2025 Major Service Degradation Affecting Zoom Outbound SMS in the AU Region Zoom Phone 1 h 3 min
Dec 16, 2025 Major Issue with Zoom Client 6.7 on iOS for subset of Users Zoom Meetings 1 d 1 h
Jul 16, 2025 Major A subset of users are experiencing intermittent connectivity issues with Zoom Phone inbound and outbound calling in the Sydney region. Zoom Phone 1 h 30 min
May 19, 2025 Major Issue with Inbound SMS in Australia Zoom Phone 2 h
Apr 16, 2025 Critical Issue with multiple Zoom Services Website and web portal, Zoom Contact Center, Zoom Meetings, Zoom Phone 4 h 58 min
Mar 5, 2025 Major A subset of users experienced issue with Zoom Meetings and Zoom Phone for Sydney region. none tagged under 1 min
Nov 9, 2022 Critical zoom.com.cn is currently down Zoom Meetings 1 h 10 min
Sep 15, 2022 Critical Issues Starting and Joining Meetings Developer Platform and SDKs, Zoom Meetings 32 min
Dec 14, 2021 Major A subset of users are unable to register and make zoom phone calls Zoom Phone 1 h 10 min
Sep 14, 2021 Critical Events.zoom.us is unavailable Zoom Events 54 min
Aug 23, 2021 Critical Issues with Enhanced API connector Room Connector 45 min
Aug 8, 2021 Major A subset of users in Australia are unable to access zoom. Zoom Meetings 44 min
Feb 2, 2021 Major A subset of users are unable to send or receive Webhooks Developer Platform and SDKs 2 h 17 min
Nov 10, 2020 Major Issue with joining meetings and webinars Zoom Meetings, Zoom Webinars 1 h 2 min
Nov 1, 2020 Major Increased join meeting failures for a subset of customers in Australia Zoom Meetings 1 h 58 min
Oct 5, 2020 Major Issue with Zoom Phone Service Zoom Phone 1 h 42 min
Aug 24, 2020 Major Issue with joining meetings and webinars Website and web portal, Zoom Meetings, Zoom Webinars 4 h 18 min
Aug 16, 2020 Critical Issues making and receiving calls in Zoom Phone Zoom Phone 57 min
Jun 5, 2020 Major Issues sending and receiving Zoom Chat Messages Team Chat 25 min
Jun 3, 2020 Major PSTN connections dropping Zoom Meetings 7 h 6 min
May 26, 2020 Major Cloud Room Connector certificate verification errors Room Connector 17 h 13 min
Apr 22, 2020 Major Issues making and receiving calls in Zoom Phone (Europe) Zoom Phone 34 min
Apr 12, 2020 Major Issues streaming to third-party services Zoom Meetings 5 h 10 min
Mar 18, 2020 Major Issues making and receiving calls in Zoom Phone (US and CAN) Zoom Phone 5 d
Mar 17, 2020 Major Issues making and receiving calls in Zoom Phone (US zones) Zoom Phone 6 h 56 min
Mar 16, 2020 Major Issues making and receiving calls in Zoom Phone Zoom Phone 10 h 51 min
Mar 13, 2020 Major Meeting start and join issues in Europe Zoom Meetings 3 h 53 min
Oct 31, 2019 Major Issue with Zoom Phone Service (US Only) Zoom Phone 1 min
Oct 4, 2019 Major Issues starting meetings and webinars Zoom Meetings, Zoom Webinars 47 min
Jun 4, 2019 Major Issues with Zoom Telephone Services Zoom Meetings 2 h 7 min
Jun 3, 2019 Major Issues with Zoom Phone service for all IPV6 clients Zoom Phone 6 h 36 min
Apr 26, 2019 Major Issues with Zoom Phone service Zoom Phone 1 h 55 min
Apr 12, 2019 Major Issues with Zoom Phone service Zoom Phone 2 h 36 min
Jan 9, 2019 Critical Significant Meeting Platform Outage Other, Room Connector, Zoom Meetings, Zoom Webinars 2 h 11 min
Feb 23, 2016 Major Group Messaging Service Intermittent none tagged 8 h 2 min
Feb 23, 2016 Major Group Messaging Service Intermittent none tagged 1 h 20 min
Sep 28, 2015 Major Zoom web services are unavailable none tagged 26 min
Jul 13, 2015 Major Zoom Web Server none tagged 51 min

Length is created or started time to resolved time on the status page, which can run past the outage itself while Zoom monitors. Where Zoom wrote its own window, the text below uses it.

April 16, 2025: the zoom.us domain went dark

This is the event most people mean when they search for a Zoom outage. Zoom’s resolution note says customers in the US and international regions could not reach Zoom services because GoDaddy Registry had placed a server block on the zoom.us domain, the result of “a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry”. Zoom says there was “no product, security, network failure, or Distributed Denial of Service (DDoS) attack”. People already in a meeting or phone call stayed connected; starting, joining or scheduling failed because each needed a DNS lookup. Zoom’s note gives 11:25 AM to 1:12 PM PDT. The status entry opened at 12:17 PM PDT and closed at 5:16 PM PDT, and its monitoring updates told users to flush their DNS cache. The fix was a registry lock that stops server block commands on zoom.us. It is the only incident since 2016 with a full written root cause, solution and prevention section on the status page.

December 16, 2025: multiple services in multiple regions

Zoom opened this at 4:34 PM PST on December 16 for inbound traffic problems in several data centers, added North America 18 minutes later, saw a recurrence at 5:12 PM, and at 5:56 PM said “a rollback is underway”. It marked Meetings and Phone as partial outage and Contact Center as degraded, then partial. The entry closed after 4 h 19 min. Zoom’s uptime page lists it against Phone and Contact Center for December 2025, two of the few months it shows below 100% (see below).

January 9, 2019: the oldest critical meeting outage

“Significant Meeting Platform Outage” is rated critical and named 5 components, including Zoom Meetings (core service), Zoom Software, Zoom Video Webinars and Telephone Services. The entry ran 2 h 11 min.

The longest Zoom incidents

Date (ET) Zoom’s title Updates Length
Sep 8, 2019 Issues starting/joining meetings and visiting the Zoom website in China 10 69 d 21 h
Oct 24, 2018 Issues calling in to the Kuwait Toll number 2 37 d 8 h
Aug 14, 2025 A subset of users may experience issues with our underlying carrier in Europe. 33 33 d
May 5, 2020 Issues displaying meeting information in Dashboard 5 26 d 7 h
Jun 17, 2021 A subset of users in Turkey are unable to dial into meetings. 4 22 d 11 h
Feb 12, 2020 Issue in HK dial-in numbers 5 19 d 9 h
Sep 30, 2021 A subset of users in Turkey are unable to dial into meetings using the toll numbers. 3 14 d 13 h
Sep 25, 2026 Service Degradation Affecting Customer Using Polycom Devices Going Offline 25 14 d 10 h
Sep 3, 2020 Cloud Recording Processing Delays 3 13 d 23 h
Feb 15, 2023 A subset of customers in China are intermittently experiencing an issue accessing Zoom. 23 13 d 7 h

Ten longest by status page length. 15 incidents stayed open more than seven days. Long entries are usually narrow (one dial-in country, one carrier, one region), not a global outage.

The longest entries are narrow faults that stayed open. The Sep 8, 2019 China entry ran 69 d 21 h. The August 2025 carrier problem in Europe ran 33 d with 33 updates, the most-updated long incident in the record. Across all incidents, 40% close within an hour and 25% run past four hours. The median in 2026 is 1 h 1 min, against 1 h 29 min for the whole record.

Longest in 2026

Date (ET) Zoom’s title Updates Length
Sep 25, 2026 Service Degradation Affecting Customer Using Polycom Devices Going Offline 25 14 d 10 h
May 26, 2026 Service Degradation Affecting Giphy In Zoom Chat and Zoom In-Meeting Chat. 21 9 d 8 h
May 18, 2026 Service Degradation Affecting Web Zoom Mail and Web Calendar Services. 14 5 d 6 h
Jun 15, 2026 Service Degradation Affecting Zoom Meeting Recordings 5 4 d 12 h
May 12, 2026 Service Degradation Affecting a Subset of Users in Web Mail and Calendar 20 4 d 9 h

Zoom’s uptime page versus its status page

uptime.zoom.us ranked first in Google for this query in our search check. It shows 13 months of availability for 11 services and a 365-day strip of daily status. Its own text says “The global metrics shown on this page reflect service uptime for all Zoom users and do not indicate a service disruption for any particular customer account or individual user”. We matched each of its 11 services to the status page components that carry the same product name, over the same year (Nov 13, 2025 to Nov 12, 2026).

Service on uptime.zoom.us Status page incidents Days with a status incident Days flagged on uptime page Months at 100% Months below 100%
Zoom Contact Center 64 58 6 11 of 13 Dec 2025: 99.9171%, Sep 2026: 99.9803%
Zoom Phone 60 53 4 11 of 13 Dec 2025: 99.9418%, Sep 2026: 99.9914%
Zoom Meetings 21 19 2 11 of 13 Dec 2025: 99.9507%, Sep 2026: 99.9914%
Zoom Virtual Agent 17 17 0 13 of 13 100% every month
Zoom Whiteboard 8 8 0 13 of 13 100% every month
Cloud Room Connector 4 4 0 13 of 13 100% every month
Zoom Webinars 4 4 0 13 of 13 100% every month
Meetings Audio 2 2 0 13 of 13 100% every month
Zoom Events 2 2 0 13 of 13 100% every month
Workforce Management 1 1 0 13 of 13 100% every month
Video SDK 0 0 0 13 of 13 100% every month

Status page incidents: incidents that name a matching component (for Meetings, the core “Zoom Meetings” component only; Meetings Audio maps to dial-in, dial-out, SIP and PSTN components). Day counts use Pacific time, the zone the uptime page uses. Months run November 2025 to November 2026.

Only two months move for any service: December 2025 and September 2026. Meetings shows 99.9507% for December 2025, which is about 22 minutes of downtime by our arithmetic, and 99.9914% for September 2026, about 4 minutes. Every other month is 100%, even though the status page lists 21 incidents on the core Meetings component in that year. The gap is in the method, not necessarily the record: Zoom calls these global figures for all users, and its daily strip grades days by a “user impact ratio”, so a fault in one region or one feature can leave a month at 100%. The uptime page also cites one event, “Issue with US08 ZCC cluster” on September 4, 2026, that has no matching entry on the status page. For a client in the affected region, the status page is the better record of what happened. Zoom also raised Workplace Pro’s annual rate 6.3% to $14.16 a user a month in early 2026, as our Zoom price increase 2026 ledger shows.

How this compares with other Zoom outage trackers

The counts depend on the definition. StatusGator says there were 265 Zoom outages since January 2025; Zoom’s own list has 398 unplanned incidents in that span. UptimeRobot gives an average resolved outage of 5h 43m across 17 incidents over five years. Across all 1,026 resolved incidents on Zoom’s page, the mean is 13 h 4 min and the median 1 h 29 min, so a short sample and a mean pulled up by long entries can both mislead. Downdetector counts user reports, a separate signal that can move before Zoom posts.

For incidents that started January 1 to October 31, 2026 (UTC), this pull finds 220 Zoom incidents and only 1 at partial or major outage. Zoom posts more incidents than most SaaS status pages we track while labeling almost none of them an outage, so counting by label alone would understate how often something breaks. Slack goes further and has labeled nothing an outage since November 2025, as our Slack outage history shows.

What this means for MSPs

Watch components, not labels

Subscribe to the components your clients use, by region, and alert on any change from operational. The page’s own settings show email, SMS, webhook and Slack subscriptions all switched on. Filtering on “major outage” would have caught 6 incidents in eleven years, and filtering on incident impact “major” or “critical” catches 8 since 2023. “Degraded performance” is what Zoom uses for most real faults, including regional call failures.

Plan for voice, not just meetings

If a client runs Zoom Phone or Contact Center, those are where 2026 incidents concentrate: 50 and 54 so far. 65 of those 80 name a region, and 31 started between 8 PM and 6 AM Eastern, when a US help desk may be thin. Keep a fallback route for inbound calls (a carrier-level forward or a second number), and check that emergency calling is tested, since Zoom Phone lists Emergency Calling as its own component in each of its seven regional groups. For Microsoft shops, the same discipline applies to Teams; our Microsoft 365 outage tracker covers that side.

Don’t quote the uptime page in an incident review

A client who lost calls for three hours in one region will not recognize a month at 100%. Use the status page incident, its times and its component list, and keep your own log. Ask Zoom for a root cause document when an event hits you: the status page has only 2 written root cause sections in 1,027 incidents, and the April 2025 note shows what a full one looks like.

Domain and DNS are part of uptime

April 2025 was not a Zoom software fault but a registry action on its domain. Check that your own clients’ key domains have registry lock where the registrar supports it, and keep a non-Zoom bridge (a phone bridge or another meeting platform) in the incident plan for when the meeting tool itself is the outage.

Search every Zoom incident

Date (ET) Zoom’s title Product Worst status Length


Frequently asked questions

Was there a Zoom outage today?

As of November 12, 2026, the latest entry on Zoom’s status page is “Service Degradation Affecting Microsoft Integrations due to an underlying vendor issue.”, opened Nov 12, 2026 at 2:24 PM ET and still open when we pulled the data. Zoom posted 18 incidents in the 30 days to Nov 12, 2026. The last one Zoom marked as a partial or major outage was January 28, 2026: Partial Outage Affecting WhatsApp Integration.

Is there any way to see Zoom outage history?

Yes. Zoom’s status page at status.zoom.us (it redirects to zoomstatus.com) has a History tab that goes back to March 2015, three months per page, and uptime.zoom.us shows monthly availability for 11 services over the last 13 months. The searchable table on this page combines all 1,027 incidents in one list, with product, worst status and length.

How often does Zoom go down?

Zoom posted 225 incidents from January 1 to November 11, 2026, about 22 a month, up from 147 in the same part of 2025 and 114 in 2024. Most are partial: 226 of 227 incidents in 2026 never went past degraded performance on any component, and 1 reached partial or major outage.

What was the biggest Zoom outage?

By reach, April 16, 2025. Zoom’s root cause note says GoDaddy Registry blocked the zoom.us domain after a communication error with Zoom’s registrar, Markmonitor, so people could not start, join or schedule meetings. Zoom’s note gives 11:25 AM to 1:12 PM PDT. It is one of 7 incidents Zoom has rated critical since 2015.

Which Zoom service has the most outages?

Over the whole record, Zoom Meetings: 226 incidents name a Meetings component. In 2026 the order changed: Zoom Contact Center leads with 54, Zoom Phone has 50, and Meetings 36. AI Companion components appear on 32 incidents in 2026, against 22 in the same months of 2025.

What time of day do Zoom outages happen?

Incidents cluster in the US working day. 33% started between 10 AM and 3 PM Eastern, and the busiest hour is 12 PM ET (81 incidents), while in UTC the busiest hour is 16:00. Weekends hold 15% of incidents. These are times Zoom opened the incident or says it started, not when users first noticed.

Download the data. zoom-status-incidents-2015-2026.csv (CSV). Licensed under CC BY 4.0: free to reuse with attribution to The Uptime Report.

Free to cite and republish with a link.

Methodology

Source. Zoom’s public status page, www.zoomstatus.com (status.zoom.us redirects there), an Atlassian Statuspage site created January 26, 2015. We read the History tab’s JSON, /history.json?page=1 to page=48, which lists 2,236 entries, then fetched /incidents/<code>.json for every one, in sequence with a pause between requests, on November 12, 2026. The site’s robots.txt disallows only /api/ and /embed/; we used neither. We also fetched uptime.zoom.us and the two JSON files its own script loads (/getMonthlyData, /getResultList).

What counts. One incident is one status page entry. We dropped 1,205 entries that are scheduled maintenance (impact “maintenance” or a scheduled time) and 4 notices with impact “none” whose titles announce updates, maintenance or new numbers. 1,027 remain. Every code on the History pages was fetched; none returned an error.

Time and length. Start is the earlier of Zoom’s created_at and started_at; end is resolved_at. Hour-of-day and weekday use that start, in UTC and in America/New_York. Length can include monitoring time after the fault, and Zoom sometimes backdates started_at, so read single values with care.

Products and status. Each affected component name in each update is mapped to a product family by keyword: Webinar, Whiteboard and AI Companion components (AIC, AI Companion, Zoom AI, ZoomMate) count as their own families wherever they sit on the page; Phone, Contact Center and Virtual Agent include every region; Meetings includes dial-in, recording and streaming components. Worst status is the most severe state Zoom set on any component during the incident. Partial or major outage means a component reached partial_outage or major_outage, or the incident impact was major or critical, the same rule as our SaaS comparison.

Limits. This measures what Zoom chose to publish, not real availability, and not any one customer’s experience. The record before 2019 is thin. Components were renamed over time. We ran no probes of Zoom. Titles are Zoom’s words; the compiled table is ours.

Not advice. Nothing here is contract or legal advice.

Cite as: The Uptime Report. "Zoom Outage History: 1,027 Incidents Since 2015, and 2026 Is the Busiest Year Yet." November 2026. https://theuptimereport.com/zoom-outage-history/

References

  1. Zoom Status, incident history (History JSON pages 1 to 48 and per-incident JSON). Accessed November 2026.
  2. status.zoom.us (redirects to zoomstatus.com). Accessed November 2026.
  3. Zoom Uptime, with its monthly and daily data files. Accessed November 2026.
  4. Zoom Status, “Issue with multiple Zoom Services”, April 16, 2025, with root cause note. Accessed November 2026.
  5. Zoom Status, “Issue with multiple Zoom Services in multiple regions”, December 16, 2025. Accessed November 2026.
  6. Zoom Terms of Service. Accessed November 2026.
  7. Atlassian Statuspage, component status and incident impact. Accessed November 2026.
  8. StatusGator, Zoom outage history, UptimeRobot, Zoom status, IncidentHub and OnlineOrNot (comparison only). Accessed November 2026.

Research library

More original data reports from The Uptime Report. Every report includes its methodology and a free CSV download. Browse all research

Threats and breaches

Infrastructure and uptime

Regulation and disclosure

Workforce and pay

MSP market and spending

Comments

One response to “Zoom Outage History: 1,027 Incidents Since 2015, and 2026 Is the Busiest Year Yet”

  1. […] Zoom Outage HistoryEvery Zoom incident since 2015 […]

Leave a Reply

Your email address will not be published. Required fields are marked *