Live

Service Degradation Affecting Outbound SMS due to an underlying carrier issue in the Australia region.

0

Zoom outbound SMS did not work in the Australia region. The incident affected SMS/MMS (Inbound/Outbound), SMS (Inbound/Outbound), Zoom Phone - Australia - SMS/MMS (Inbound/Outbound), and Zoom CX - Australia - SMS (Inbound/Outbound). Zoom reports that the incident is resolved. It lasted 82 minutes.

State

Resolved

Started

Lasted

1 h 22 min

Worst impact

Degraded

Timeline

5 updates
01:1401:3401:5502:1502:36
DegradedNoticeUpdate postedTimes in UTC

Identified

1 h 7 min 82%

Resolved

3 min 4%

Monitoring

12 min 14%

Updates

Times in UTC

As posted by Zoom

Resolved

This incident has been resolved.

Monitoring

The service degradation affecting Outbound SMS due to an underlying carrier issue in the Australia region has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.

Identified

We have successfully identified the root cause affecting Zoom Phone Outbound due to an underlying carrier issue in the Australia region Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made. Thank you for your patience.

Resolved
Identified

We have successfully identified the root cause affecting Zoom Phone Outbound due to an underlying carrier issue in the Australia region Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made. Thank you for your patience.

Affected components

4
SMS/MMS (Inbound/Outbound)SMS (Inbound/Outbound)Zoom Phone - AUSTRALIA - SMS/MMS (Inbound/Outbound)Zoom CX - AUSTRALIA - SMS (Inbound/Outbound)

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

63

Days with an incident

52

Median duration

1 h 21 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days
median 1 h 21 min
90 days agoToday

Other Zoom incidents

All incidents

Follow Zoom

Your coding agent knows when Zoom is down, and tells you when a failure is theirs, not yours. You can also get Zoom incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zoom" and tell me if Zoom has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=zoom
Slack
/feed subscribe https://outages.live/feed.xml?providers=zoom

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane