← HonkWatch.com

Is Zoom Events down in Mozambique?

Planned maintenance at Zoom Events

People in Mozambique: 0 reports in the last hour Official page: Planned maintenance, checked 2 min ago Our checks: loads from 35 of 35 places
Zoom Events has planned maintenance. Maintenance: Zoom Chat Backend Update: October, 2026 (No Operational Impact). Updated 7 Nov, 20:36 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Zoom's status page)

Maintenance

  • Zoom Chat Backend Update: October, 2026 (No Operational Impact) (under way) 16 Oct, 16:00 UTC to 14 Nov, 16:00 UTC. Affects Zoom Chat · Details Latest update (16 Oct, 16:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Zoom FileServer Release: November 03, 2026 (No Operational Impact) (under way) 4 Nov, 05:00 UTC to 14 Nov, 10:00 UTC. Affects Zoom Meetings, Zoom Chat, Zoom Contact Center, Zoom Phone · Details Latest update (4 Nov, 05:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Zoom Team Chat Update (under way) 5 Nov, 16:00 UTC to 20 Nov, 16:00 UTC. Affects Zoom Chat · Details Latest update (5 Nov, 16:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
Show 7 more maintenance windows
  • Scheduled Zoom Software Quarterly Lifecycle Update (11/7/2026) (planned) 8 Nov, 00:00 UTC to 8 Nov, 01:00 UTC. Affects Download Center & Clients · Details Latest update (8 Oct, 00:15 UTC): As a reminder approximately 30 days ahead of the upcoming enforcement, Zoom will be enforcing a new global minimum version this November 7. This affects the following products: ◦ VDI plugin ◦ Zoom Phone Local Survivability (ZPLS) module ◦ Meeting SDK (Web) For more information, such as specific vers
  • Zoom Phone Maintenance - EU01 - FRA2 Data Center: November 09, 2026 (planned) 9 Nov, 17:00 UTC to 12 Nov, 07:30 UTC. Affects Zoom Phone · Details Latest update (5 Oct 2026, 09:35 UTC): Zoom will perform service maintenance at our EU01-FRA2 Data Center starting at 9:00 AM Pacific on November 09, 2026. Zoom Phone users registered to the those sip zones will be automatically registered in the AMS2 sip zone sequentially. During the maintenance window, a brief disconnection may be expe
  • Zoom Conference Room Connector DNS Changes in Saudi Arabia Region: November 13, 2026 (No Operational Impact) (planned) 14 Nov, 03:30 UTC to 14 Nov, 19:30 UTC. Affects Zoom Conference Room Connector · Details Latest update (16 Oct, 18:15 UTC): As part of ongoing service enhancements for the Cloud Room Connector (CRC) service, Zoom will be updating DNS records for SIP/H.323 and IP endpoints in Saudi Arabia region . Effective Date: November 14, 2026 Action Required To avoid service disruption, we recommend reviewing your CRC endpoint config
  • Zoom Conference Room Connector DNS Changes: November 14, 2026 (No Operational Impact) (planned) 14 Nov, 03:30 UTC to 14 Nov, 19:30 UTC. Affects Zoom Conference Room Connector · Details Latest update (23 Oct, 08:37 UTC): We will be undergoing scheduled maintenance during this time.
  • Zoom Phone Maintenance - SA01 - KSA1 Data Center: November 16, 2026 (planned) 16 Nov, 17:00 UTC to 19 Nov, 05:30 UTC. Affects Zoom Phone · Details Latest update (19 Oct, 09:49 UTC): Zoom will perform service maintenance at our SA01-KSA1 Data Center starting at 9:00 AM Pacific on November 16, 2026. Zoom Phone users registered to the those sip zones will be automatically registered in the SA01-RUH1 sip zone sequentially. During the maintenance window, a brief disconnection may be
  • Zoom Phone Maintenance (Sydney Data Center): November 20, 2026 (planned) 20 Nov, 10:00 UTC to 20 Nov, 18:00 UTC. Affects Zoom Phone · Details Latest update (29 Oct, 15:07 UTC): Zoom will perform service maintenance at our SYD1 Data Center starting at 2:00 AM Pacific (or 9:00 PM Sydney) on November 20, 2026. Zoom Phone users registered to those sip zones will be automatically registered in the MEL1 sip zone sequentially. During the maintenance window, a brief disconnection
  • Zoom Phone India Maintenance (Hyderabad Data Center): November 20, 2026 (planned) 20 Nov, 12:00 UTC to 21 Nov, 18:00 UTC. Affects Zoom Phone · Details Latest update (2 Nov, 05:23 UTC): Zoom Phone users registered to the India (Hyderabad) Data Center will be automatically registered in an alternative Data Center (Mumbai) starting at 20th November 2026 04:00 AM PST (5:30 PM IST on 20th November 2026). During the maintenance window, a brief disconnection may be experienced and notifi

We keep the first 10 of 13 maintenance windows; the rest are on Zoom's status page.

In Zoom's own words, as we read them every 2.5 minutes, last 2 min ago. Read Zoom's status page

Reports from people in Mozambique

Last 24 hours · Mozambique · times in UTC

0 reports

No community reports in the last 24 hours from Mozambique. Having trouble? Add your report.

Status page: maintenance, 6 Nov, 05:11 to now 024 00:0006:0012:0018:00 20:45-20:50 UTC: 33 of 33 places loaded it, typical 570 ms20:50-20:55 UTC: 35 of 35 places loaded it, typical 616 ms20:55-21:00 UTC: 34 of 34 places loaded it, typical 599 ms21:00-21:05 UTC: 19 of 19 places loaded it, typical 539 ms21:05-21:10 UTC: 31 of 31 places loaded it, typical 619 ms21:10-21:15 UTC: 33 of 33 places loaded it, typical 608 ms21:15-21:20 UTC: 30 of 30 places loaded it, typical 669 ms21:20-21:25 UTC: 35 of 35 places loaded it, typical 668 ms21:25-21:30 UTC: 30 of 30 places loaded it, typical 668 ms21:30-21:35 UTC: 33 of 33 places loaded it, typical 670 ms21:35-21:40 UTC: 35 of 35 places loaded it, typical 608 ms21:40-21:45 UTC: 34 of 34 places loaded it, typical 603 ms21:45-21:50 UTC: 25 of 25 places loaded it, typical 558 ms21:50-21:55 UTC: 27 of 27 places loaded it, typical 601 ms21:55-22:00 UTC: 32 of 32 places loaded it, typical 676 ms22:00-22:05 UTC: 35 of 35 places loaded it, typical 619 ms22:05-22:10 UTC: 29 of 29 places loaded it, typical 643 ms22:10-22:15 UTC: 34 of 34 places loaded it, typical 637 ms22:15-22:20 UTC: 35 of 35 places loaded it, typical 664 ms22:20-22:25 UTC: 33 of 33 places loaded it, typical 590 ms22:25-22:30 UTC: 27 of 27 places loaded it, typical 538 ms22:30-22:35 UTC: 35 of 35 places loaded it, typical 689 ms22:35-22:45 UTC: 34 of 34 places loaded it, typical 629 to 663 ms22:45-22:55 UTC: 35 of 35 places loaded it, typical 578 to 598 ms22:55-23:00 UTC: 32 of 32 places loaded it, typical 599 ms23:00-23:10 UTC: 35 of 35 places loaded it, typical 615 to 708 ms23:10-23:15 UTC: 32 of 32 places loaded it, typical 643 ms23:15-23:20 UTC: 33 of 33 places loaded it, typical 521 ms23:20-23:25 UTC: 35 of 35 places loaded it, typical 600 ms23:25-23:30 UTC: 34 of 34 places loaded it, typical 632 ms23:30-23:35 UTC: 35 of 35 places loaded it, typical 608 ms23:35-23:50 UTC: 34 of 34 places loaded it, typical 588 to 611 ms23:50-23:55 UTC: 34 of 35 places loaded it, typical 578 ms23:55-00:00 UTC: 34 of 34 places loaded it, typical 582 ms00:00-00:10 UTC: 35 of 35 places loaded it, typical 580 to 605 ms00:10-00:15 UTC: 34 of 34 places loaded it, typical 611 ms00:15-00:20 UTC: 34 of 35 places loaded it, typical 595 ms00:20-00:30 UTC: 34 of 34 places loaded it, typical 634 to 639 ms00:30-00:40 UTC: 35 of 35 places loaded it, typical 583 to 595 ms00:40-00:45 UTC: 33 of 33 places loaded it, typical 584 ms00:45-00:55 UTC: 35 of 35 places loaded it, typical 579 to 604 ms00:55-01:00 UTC: 34 of 34 places loaded it, typical 613 ms01:00-01:10 UTC: 35 of 35 places loaded it, typical 562 to 588 ms01:10-01:15 UTC: 32 of 32 places loaded it, typical 660 ms01:15-01:25 UTC: 35 of 35 places loaded it, typical 590 to 599 ms01:25-01:30 UTC: 34 of 34 places loaded it, typical 641 ms01:30-01:40 UTC: 35 of 35 places loaded it, typical 566 to 609 ms01:40-01:50 UTC: 34 of 34 places loaded it, typical 583 to 645 ms01:50-01:55 UTC: 35 of 35 places loaded it, typical 578 ms01:55-02:00 UTC: 34 of 34 places loaded it, typical 572 ms02:00-02:10 UTC: 35 of 35 places loaded it, typical 601 to 609 ms02:10-02:15 UTC: 33 of 33 places loaded it, typical 557 ms02:15-02:25 UTC: 35 of 35 places loaded it, typical 598 to 608 ms02:25-02:30 UTC: 33 of 33 places loaded it, typical 619 ms02:30-02:40 UTC: 35 of 35 places loaded it, typical 577 to 595 ms02:40-02:45 UTC: 34 of 34 places loaded it, typical 614 ms02:45-02:55 UTC: 35 of 35 places loaded it, typical 549 to 604 ms02:55-03:05 UTC: 34 of 34 places loaded it, typical 592 to 679 ms03:05-03:10 UTC: 35 of 35 places loaded it, typical 575 ms03:10-03:15 UTC: 34 of 34 places loaded it, typical 585 ms03:15-03:25 UTC: 35 of 35 places loaded it, typical 606 to 611 ms03:25-03:30 UTC: 34 of 34 places loaded it, typical 591 ms03:30-03:40 UTC: 35 of 35 places loaded it, typical 606 to 644 ms03:40-03:45 UTC: 34 of 34 places loaded it, typical 592 ms03:45-03:55 UTC: 35 of 35 places loaded it, typical 567 to 639 ms03:55-04:05 UTC: 34 of 34 places loaded it, typical 640 to 681 ms04:05-04:10 UTC: 35 of 35 places loaded it, typical 605 ms04:10-04:15 UTC: 34 of 34 places loaded it, typical 588 ms04:15-04:25 UTC: 35 of 35 places loaded it, typical 579 to 582 ms04:25-04:30 UTC: 34 of 34 places loaded it, typical 610 ms04:30-04:40 UTC: 35 of 35 places loaded it, typical 577 to 606 ms04:40-04:50 UTC: 34 of 34 places loaded it, typical 560 to 670 ms04:50-04:55 UTC: 35 of 35 places loaded it, typical 582 ms04:55-05:00 UTC: 33 of 33 places loaded it, typical 603 ms05:00-05:10 UTC: 35 of 35 places loaded it, typical 612 to 628 ms05:10-05:15 UTC: 34 of 34 places loaded it, typical 589 ms05:15-05:25 UTC: 35 of 35 places loaded it, typical 577 to 606 ms05:25-05:35 UTC: 34 of 34 places loaded it, typical 574 to 583 ms05:35-05:40 UTC: 35 of 35 places loaded it, typical 577 ms05:40-05:45 UTC: 34 of 34 places loaded it, typical 564 ms05:45-05:55 UTC: 35 of 35 places loaded it, typical 569 to 611 ms05:55-06:00 UTC: 34 of 34 places loaded it, typical 588 ms06:00-06:10 UTC: 35 of 35 places loaded it, typical 561 to 579 ms06:10-06:15 UTC: 34 of 34 places loaded it, typical 619 ms06:15-06:20 UTC: 35 of 35 places loaded it, typical 576 ms06:20-06:30 UTC: 34 of 34 places loaded it, typical 599 to 601 ms06:30-06:40 UTC: 35 of 35 places loaded it, typical 568 to 571 ms06:40-06:45 UTC: 34 of 34 places loaded it, typical 589 ms06:45-06:50 UTC: 35 of 35 places loaded it, typical 603 ms06:50-07:00 UTC: 34 of 34 places loaded it, typical 566 to 569 ms07:00-07:05 UTC: 35 of 35 places loaded it, typical 599 ms07:05-07:15 UTC: 34 of 34 places loaded it, typical 591 to 620 ms07:15-07:25 UTC: 35 of 35 places loaded it, typical 571 to 596 ms07:25-07:30 UTC: 34 of 34 places loaded it, typical 597 ms07:30-07:35 UTC: 35 of 35 places loaded it, typical 607 ms07:35-07:45 UTC: 34 of 34 places loaded it, typical 572 to 590 ms07:45-07:55 UTC: 35 of 35 places loaded it, typical 564 to 584 ms07:55-08:00 UTC: 34 of 34 places loaded it, typical 579 ms08:00-08:10 UTC: 35 of 35 places loaded it, typical 570 to 593 ms08:10-08:20 UTC: 34 of 34 places loaded it, typical 588 to 629 ms08:20-08:25 UTC: 35 of 35 places loaded it, typical 571 ms08:25-08:30 UTC: 34 of 34 places loaded it, typical 568 ms08:30-08:40 UTC: 35 of 35 places loaded it, typical 569 to 590 ms08:40-08:45 UTC: 34 of 34 places loaded it, typical 577 ms08:45-08:55 UTC: 35 of 35 places loaded it, typical 576 to 592 ms08:55-09:00 UTC: 34 of 34 places loaded it, typical 609 ms09:00-09:10 UTC: 35 of 35 places loaded it, typical 564 to 605 ms09:10-09:15 UTC: 34 of 34 places loaded it, typical 636 ms09:15-09:20 UTC: 31 of 31 places loaded it, typical 607 ms09:20-09:25 UTC: 35 of 35 places loaded it, typical 576 ms09:25-09:35 UTC: 34 of 34 places loaded it, typical 580 to 590 ms09:35-09:40 UTC: 35 of 35 places loaded it, typical 573 ms09:40-09:45 UTC: 34 of 34 places loaded it, typical 590 ms09:45-09:50 UTC: 35 of 35 places loaded it, typical 550 ms09:50-10:00 UTC: 34 of 34 places loaded it, typical 568 to 574 ms10:00-10:10 UTC: 35 of 35 places loaded it, typical 576 to 578 ms10:10-10:15 UTC: 34 of 34 places loaded it, typical 597 ms10:15-10:20 UTC: 21 of 21 places loaded it, typical 535 ms10:20-10:25 UTC: 35 of 35 places loaded it, typical 558 ms10:25-10:30 UTC: 34 of 34 places loaded it, typical 635 ms10:30-10:40 UTC: 35 of 35 places loaded it, typical 562 to 575 ms10:40-10:50 UTC: 34 of 34 places loaded it, typical 561 to 570 ms10:50-10:55 UTC: 35 of 35 places loaded it, typical 587 ms10:55-11:00 UTC: 34 of 34 places loaded it, typical 593 ms11:00-11:10 UTC: 35 of 35 places loaded it, typical 562 to 572 ms11:10-11:20 UTC: 34 of 34 places loaded it, typical 566 to 593 ms11:20-11:25 UTC: 35 of 35 places loaded it, typical 573 ms11:25-11:35 UTC: 34 of 34 places loaded it, typical 588 to 592 ms11:35-11:40 UTC: 21 of 21 places loaded it, typical 545 ms11:40-11:55 UTC: 35 of 35 places loaded it, typical 584 to 609 ms11:55-12:05 UTC: 34 of 34 places loaded it, typical 586 to 590 ms12:05-12:10 UTC: 35 of 35 places loaded it, typical 586 ms12:10-12:15 UTC: 34 of 34 places loaded it, typical 573 ms12:15-12:25 UTC: 35 of 35 places loaded it, typical 563 to 574 ms12:25-12:35 UTC: 34 of 34 places loaded it, typical 556 to 571 ms12:35-12:40 UTC: 35 of 35 places loaded it, typical 581 ms12:40-12:45 UTC: 34 of 34 places loaded it, typical 594 ms12:45-12:50 UTC: 35 of 35 places loaded it, typical 579 ms12:50-13:00 UTC: 34 of 34 places loaded it, typical 567 to 591 ms13:00-13:10 UTC: 35 of 35 places loaded it, typical 573 to 589 ms13:10-13:20 UTC: 34 of 34 places loaded it, typical 557 to 590 ms13:20-13:25 UTC: 35 of 35 places loaded it, typical 596 ms13:25-13:30 UTC: 34 of 34 places loaded it, typical 581 ms13:30-13:40 UTC: 35 of 35 places loaded it, typical 547 to 573 ms13:40-13:45 UTC: 34 of 34 places loaded it, typical 597 ms13:45-13:55 UTC: 35 of 35 places loaded it, typical 577 to 654 ms13:55-14:00 UTC: 34 of 34 places loaded it, typical 603 ms14:00-14:10 UTC: 35 of 35 places loaded it, typical 561 to 607 ms14:10-14:15 UTC: 33 of 33 places loaded it, typical 607 ms14:15-14:25 UTC: 35 of 35 places loaded it, typical 543 to 558 ms14:25-14:30 UTC: 34 of 34 places loaded it, typical 574 ms14:30-14:40 UTC: 35 of 35 places loaded it, typical 566 to 617 ms14:40-14:45 UTC: 34 of 34 places loaded it, typical 589 ms14:45-14:50 UTC: 35 of 35 places loaded it, typical 588 ms14:50-15:00 UTC: 34 of 34 places loaded it, typical 568 to 596 ms15:00-15:10 UTC: 35 of 35 places loaded it, typical 547 to 572 ms15:10-15:15 UTC: 34 of 34 places loaded it, typical 611 ms15:15-15:25 UTC: 35 of 35 places loaded it, typical 562 to 581 ms15:25-15:30 UTC: 33 of 33 places loaded it, typical 585 ms15:30-15:35 UTC: 34 of 34 places loaded it, typical 599 ms15:35-15:40 UTC: 35 of 35 places loaded it, typical 582 ms15:40-15:45 UTC: 34 of 34 places loaded it, typical 600 ms15:45-15:55 UTC: 35 of 35 places loaded it, typical 606 to 612 ms15:55-16:05 UTC: 34 of 34 places loaded it, typical 574 to 601 ms16:05-16:10 UTC: 35 of 35 places loaded it, typical 574 ms16:10-16:15 UTC: 34 of 34 places loaded it, typical 641 ms16:15-16:25 UTC: 35 of 35 places loaded it, typical 577 to 622 ms16:25-16:35 UTC: 34 of 34 places loaded it, typical 603 to 642 ms16:35-16:40 UTC: 35 of 35 places loaded it, typical 596 ms16:40-16:45 UTC: 34 of 34 places loaded it, typical 623 ms16:45-16:50 UTC: 35 of 35 places loaded it, typical 620 ms16:50-17:00 UTC: 34 of 34 places loaded it, typical 607 to 611 ms17:00-17:05 UTC: 35 of 35 places loaded it, typical 590 ms17:05-17:15 UTC: 34 of 34 places loaded it, typical 564 to 625 ms17:15-17:20 UTC: 35 of 35 places loaded it, typical 583 ms17:20-17:30 UTC: 34 of 34 places loaded it, typical 612 to 637 ms17:30-17:40 UTC: 35 of 35 places loaded it, typical 588 to 617 ms17:40-17:45 UTC: 33 of 33 places loaded it, typical 660 ms17:45-17:55 UTC: 35 of 35 places loaded it, typical 581 to 610 ms17:55-18:00 UTC: 34 of 34 places loaded it, typical 591 ms18:00-18:10 UTC: 35 of 35 places loaded it, typical 608 to 659 ms18:10-18:15 UTC: 34 of 34 places loaded it, typical 597 ms18:15-18:20 UTC: 35 of 35 places loaded it, typical 577 ms18:20-18:30 UTC: 34 of 34 places loaded it, typical 607 to 633 ms18:30-18:40 UTC: 35 of 35 places loaded it, typical 591 to 598 ms18:40-18:45 UTC: 34 of 34 places loaded it, typical 601 ms18:45-18:50 UTC: 35 of 35 places loaded it, typical 583 ms18:50-19:00 UTC: 34 of 34 places loaded it, typical 600 to 623 ms19:00-19:05 UTC: 35 of 35 places loaded it, typical 621 ms19:05-19:10 UTC: 31 of 31 places loaded it, typical 587 ms19:10-19:15 UTC: 34 of 34 places loaded it, typical 593 ms19:15-19:20 UTC: 35 of 35 places loaded it, typical 616 ms19:20-19:30 UTC: 34 of 34 places loaded it, typical 593 to 599 ms19:30-19:40 UTC: 35 of 35 places loaded it, typical 572 to 615 ms19:40-19:45 UTC: 34 of 34 places loaded it, typical 582 ms19:45-19:55 UTC: 35 of 35 places loaded it, typical 596 to 608 ms19:55-20:00 UTC: 32 of 32 places loaded it, typical 599 ms20:00-20:10 UTC: 35 of 35 places loaded it, typical 571 to 604 ms20:10-20:15 UTC: 34 of 34 places loaded it, typical 590 ms20:15-20:20 UTC: 33 of 33 places loaded it, typical 567 ms20:20-20:25 UTC: 35 of 35 places loaded it, typical 600 ms20:25-20:35 UTC: 34 of 34 places loaded it, typical 598 to 636 ms20:35-20:40 UTC: 21 of 21 places loaded it, typical 577 ms Typical response time of the places that loaded it, at most 708 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Zoom Events's status page showed a partial outage, a major outage or maintenance, as we read it every 2.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded zoom.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Mozambique only.

Latest checks, 20:35-20:40 UTC: 21 of 21 places loaded it, typical 577 ms.

Report totals as of 7 Nov, 20:38 UTC

Report a problem with Zoom Events

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Mozambique

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Mozambique. The report chart above is filtered to Mozambique.

Our own checks of zoom.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Johannesburg: loaded in 959 ms Hong Kong: loaded in 857 ms Amsterdam: loaded in 468 ms Warsaw: loaded in 524 ms Singapore: loaded in 1009 ms Jakarta: loaded in 975 ms São Paulo: loaded in 577 ms Dallas: loaded in 495 ms Santiago: loaded in 662 ms Port Louis: loaded in 1360 ms London: loaded in 426 ms Cape Town: loaded in 1041 ms Madrid: loaded in 501 ms Hamina: loaded in 546 ms New York: loaded in 110 ms Seoul: loaded in 907 ms Toronto: loaded in 170 ms Los Angeles: loaded in 660 ms Osaka: loaded in 827 ms Lauterbourg: loaded in 490 ms New Jersey: loaded in 144 ms Doha: loaded in 1228 ms Atlanta: loaded in 149 ms Sydney: loaded in 928 ms Bangalore: loaded in 1092 ms Melbourne: loaded in 976 ms St. Louis: loaded in 277 ms Tokyo: loaded in 718 ms Mumbai: loaded in 892 ms Delhi: loaded in 1125 ms Portsmouth: loaded in 439 ms Querétaro: loaded in 306 ms Seattle: loaded in 374 ms Frankfurt: loaded in 440 ms Tel Aviv: loaded in 620 ms
  • JohannesburgReachable959 ms, 2 min ago
  • Hong KongReachable857 ms, 3 min ago
  • AmsterdamReachable468 ms, 3 min ago
  • WarsawReachable524 ms, 3 min ago
  • SingaporeReachable1009 ms, 3 min ago
  • JakartaReachable975 ms, 3 min ago
  • São PauloReachable577 ms, 3 min ago
  • DallasReachable495 ms, 3 min ago
  • SantiagoReachable662 ms, 3 min ago
  • Port LouisReachable1360 ms, 3 min ago
  • LondonReachable426 ms, 3 min ago
  • Cape TownReachable1041 ms, 3 min ago
  • MadridReachable501 ms, 3 min ago
  • HaminaReachable546 ms, 3 min ago
  • New YorkReachable110 ms, 3 min ago
  • SeoulReachable907 ms, 3 min ago
  • TorontoReachable170 ms, 3 min ago
  • Los AngelesReachable660 ms, 3 min ago
  • OsakaReachable827 ms, 4 min ago
  • LauterbourgReachable490 ms, 4 min ago
  • New JerseyReachable144 ms, 4 min ago
  • DohaReachable1228 ms, 4 min ago
  • AtlantaReachable149 ms, 4 min ago
  • SydneyReachable928 ms, 4 min ago
  • BangaloreReachable1092 ms, 4 min ago
  • MelbourneReachable976 ms, 4 min ago
  • St. LouisReachable277 ms, 4 min ago
  • TokyoReachable718 ms, 4 min ago
  • MumbaiReachable892 ms, 4 min ago
  • DelhiReachable1125 ms, 4 min ago
  • PortsmouthReachable439 ms, 4 min ago
  • QuerétaroReachable306 ms, 4 min ago
  • SeattleReachable374 ms, 4 min ago
  • FrankfurtReachable440 ms, 4 min ago
  • Tel AvivReachable620 ms, 4 min ago

This is separate from the status page: we request zoom.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Zoom Events

Zoom

All 306 listed parts are working.

Incidents and maintenance

Maintenance

  • Zoom Chat Backend Update: October, 2026 (No Operational Impact) (now) 16 Oct, 16:00 UTC to 14 Nov, 16:00 UTC. Affects Zoom Chat · Details
  • Zoom FileServer Release: November 03, 2026 (No Operational Impact) (now) 4 Nov, 05:00 UTC to 14 Nov, 10:00 UTC. Affects Zoom Meetings, Zoom Chat, Zoom Contact Center, Zoom Phone · Details
  • Zoom Team Chat Update (now) 5 Nov, 16:00 UTC to 20 Nov, 16:00 UTC. Affects Zoom Chat · Details
  • Scheduled Zoom Software Quarterly Lifecycle Update (11/7/2026) (planned) 8 Nov, 00:00 UTC to 8 Nov, 01:00 UTC. Affects Download Center & Clients · Details
  • Zoom Phone Maintenance - EU01 - FRA2 Data Center: November 09, 2026 (planned) 9 Nov, 17:00 UTC to 12 Nov, 07:30 UTC. Affects Zoom Phone · Details
  • Zoom Conference Room Connector DNS Changes in Saudi Arabia Region: November 13, 2026 (No Operational Impact) (planned) 14 Nov, 03:30 UTC to 14 Nov, 19:30 UTC. Affects Zoom Conference Room Connector · Details
  • Zoom Conference Room Connector DNS Changes: November 14, 2026 (No Operational Impact) (planned) 14 Nov, 03:30 UTC to 14 Nov, 19:30 UTC. Affects Zoom Conference Room Connector · Details
  • Zoom Phone Maintenance - SA01 - KSA1 Data Center: November 16, 2026 (planned) 16 Nov, 17:00 UTC to 19 Nov, 05:30 UTC. Affects Zoom Phone · Details
  • Zoom Phone Maintenance (Sydney Data Center): November 20, 2026 (planned) 20 Nov, 10:00 UTC to 20 Nov, 18:00 UTC. Affects Zoom Phone · Details
  • Zoom Phone India Maintenance (Hyderabad Data Center): November 20, 2026 (planned) 20 Nov, 12:00 UTC to 21 Nov, 18:00 UTC. Affects Zoom Phone · Details
Outage history

Last problem: 6 Nov, 03:35 UTC, partial outage for 1 h 37 min (Open incident: Service Degradation Affecting Zoom Mail, Calendar and Scheduler.).

Last 9030 days

92.61% of the time without a reported outage, since 2 Nov

Of the last 90 days, 3 had a partial or major outage, 3 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

6 Nov, 03:35 UTCPartial outage1 h 37 minOpen incident: Service Degradation Affecting Zoom Mail, Calendar and Scheduler.
3 Nov, 17:21 UTCPartial outage7 h 51 minOpen incident: Service Degradation Affecting Outbound MMS Services in the US region
What can I try?

Having trouble with Zoom Events?

  1. Compare reports from Mozambique and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Zoom Events down, or is it just me?

Zoom Events is doing planned maintenance, so some parts may not work right now. It is probably not just you.

How do we know?

We read the official Zoom Events status page and load zoom.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Video and meetings

Each card shows that service's own status, not Zoom Events's. A problem listed here does not mean Zoom Events has one.

See the live outage feed for Mozambique · Find another service