- Zoom fell to users for several hours
- The interruption was caused by a “communication error” of Godaddy’s domain
- Spotify and X also had problems, but it was thought that this was not related to
The recent departure from the Zoom has blamed a domain theme of Godaddy, with the Godaddy registration erroneously blocking the zoom domain.us due to a communication error between the Zoom, Markmonitor and Godaddy Registry domain registration.
The result was reduced by the service between 2:55 pm et and 4:12 pm et, with zoom meetings, zoom phone, zoom contact center and the zoom website, all affected.
The videoconference company hastened to add: “There was no product, safety, network failure or service denial (DDOS) attack.”
Zoom Attiga caused by Godaddy’s error
Although Zoom confirmed a “communication error” between Markmonitor and the Godaddy registration caused the interruption, we do not know any details about the events prior to lack of communication.
The two domain and zoom companies worked together to identify and eliminate the “Quickly” block, Zoom added.
Separate descent monitoring pointed out that most complaints related to server connections, and one in five also experiences login problems and a handful of conference calls.
The interruption occurred only a few hours after a generalized interruption that affects the application, the website and the Spotify music transmission services, and a couple of hours before a smaller X interruption that affects the website and the application, however, these problems are probably not related.
Although the services had been restored in less than two hours, some users were advised to download their DNS caches and connect if they were still experiencing problems:
- For Windows, open a system symbol and write “ipconfig /flushdns”
- For Mac, open a terminal window and write “Sudo Dscacheutil -flushcache; Sudo Killall -Hup Mdns share”
Cisco wallet has also carried out a detail analysis of the interruption, pointing out the functionality of DNS and the impact of the incident.
“Identifying a specific failure domain when a service finds problems requires performance visibility throughout the service chain,” said Cisco.
