Major outages and post-mortemsBackground
Zoom goes down for nearly two hours on April 16, 2025 after its domain is blocked at the registry
From 2:25 to 4:12 p.m. EDT on April 16, 2025, the zoom.us domain stopped working because GoDaddy Registry placed a block on it. GoDaddy Registry said a communication error between Zoom’s registrar, Markmonitor, and the registry caused the shutdown, and that there was no product, security or network failure. Meetings, Zoom Phone and Zoom’s website failed for users on every kind of connection, so restarting a home router would not have helped. Published October 6, 2026.
- Event date
- Published here
- Updated
- Source
- GoDaddy Registry
Background itemThis happened 538 days before we published it (more than 90). It is here as context for the guides it links, not as breaking news. Check the source for anything that has changed since.
What changed
On the afternoon of April 16, 2025, Zoom stopped working for users around the world. The cause was not Zoom’s servers or anyone’s internet connection. It was the domain name zoom.us itself.
GoDaddy Registry, which runs the .us domain registry, said the zoom.us domain “was not available due to a server block by GoDaddy Registry.” It said the block came from “a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry,” which led the registry to shut the domain down by mistake. The three companies found and removed the block, and GoDaddy Registry said there was no product, security or network failure at any of them.
The Register reported that Zoom’s first status message said it was “investigating domain name resolution issues on the zoom.us domain that is affecting multiple services,” and that meetings, Zoom’s website and its phone service were affected.
When
- Outage: 2:25 p.m. to 4:12 p.m. EDT on April 16, 2025, per GoDaddy Registry. That is about an hour and 47 minutes, in the middle of the US workday.
Who is affected and what it means for you
Anyone who needed Zoom that afternoon, on any connection. When a domain stops resolving, apps and browsers can’t find the servers behind it, so to the user it looks exactly like the internet is down for that one service.
This is a useful case to remember because it fools the usual checks. Restarting the router, switching to a phone hotspot or failing over to a backup internet line would all have reached the same broken name. Other websites kept loading, which was the clue.
On Starlink, people sometimes suspect DNS settings or CGNAT when a single service fails. Changing DNS servers would not have fixed this either, because the registry block removed the domain at its source.
What you can do now
- When one service fails and others work, check that service’s status first. Zoom’s status page was affected too, so also check a news site or your team chat.
- Keep a non-Zoom fallback for important meetings: a phone number for the organizer, or a second meeting tool your team already uses.
- Don’t spend backup data chasing a service outage. A backup line helps when your own link is down, not when the service is.
- Our video calls guide and troubleshooting page cover the call problems that are on your side.
What stays the same
- Nothing about Starlink or home connections was involved.
- Zoom’s bandwidth needs and call settings didn’t change.
What we don’t know yet
- How many users and meetings were affected. The sources we read give no count.
- GoDaddy Registry and Markmonitor said they would work to prevent a repeat, but we did not find a detailed public write-up of what they changed.
- The Register’s duration (about 90 minutes) differs slightly from GoDaddy Registry’s times; we use the registry’s.
This item is background: it happened more than 90 days before we published this page.
Source
zoom.us Outage (GoDaddy Registry)
Also cited
Related guides on this site
Correction log
No corrections since publication. Spotted an error? See corrections for how to tell us; changes are logged here with the date.