Live

Service Degradation Affecting Outbound MMS Services in the US region

0

Zoom outbound MMS does not work for some users in the US region. The affected components are SMS/MMS Inbound/Outbound and Zoom Phone North America SMS/MMS Inbound/Outbound. Zoom identified an issue with its underlying carrier and works with the carrier partner to resolve it.

State

Identified

Started

Ongoing for

1 h 15 min

Worst impact

Degraded

Timeline

2 updates
17:1817:3717:5618:1418:33
DegradedUpdate postedTimes in UTC

Investigating

11 min 15%

Identified

1 h 3 min 85%

Updates

Times in UTC

As posted by Zoom

Identified

We have identified an issue with our underlying carrier in US region where a subset of users are experiencing issues with outbound MMS services. We are actively working with our carrier partner to resolve the issue. We will provide an update as soon as more information becomes available.

Investigating

We are currently investigating service degradation affecting outbound MMS Services for a subset of users in the US region. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.

Affected components

2
SMS/MMS (Inbound/Outbound)Zoom Phone - NORTH AMERICA - SMS/MMS (Inbound/Outbound)

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

42

Median duration

47 min

This incident

1.6× the median

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

14 days
median 47 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.cc/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.cc/feed.xml?providers=zoom
Slack
/feed subscribe https://outages.cc/feed.xml?providers=zoom

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane