A significant outage on April 16 affected Zoom for almost two hours due to a DNS issue initiated by GoDaddy. The problem, which started at 11:25 PDT, prevented users from accessing zoom.us and its services, disrupting ongoing video meetings. Cisco's ThousandEyes identified that a failure in top-level domain nameservers resulted in the cascading problem. While Zoom managed to restore service by 13:55 PDT, users had to follow technical instructions to flush their DNS caches. The final update highlighted that the issue stemmed from a server block by GoDaddy Registry due to a communication error.
We are investigating domain name resolution issues on the zoom.us domain that is affecting multiple services.
The issue had a cascading effect that impacted Zoom's services, particularly their main webpage, zoom.com.
On April 16, between 2:25 P.M. ET and 4:12 P.M. ET, the domain zoom.us was not available due to a server block by GoDaddy Registry.
Zoom's instructions for restoring services on Macs instructed users to type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Collection
[
|
...
]