←back to thread

Zoom outage caused by accidental 'shutting down' of the zoom.us domain

(status.zoom.us)
634 points RVRX | 2 comments | 17 Apr 25 00:55 UTC | HN request time: 0.631s | source
Show context
RVRX ◴[17 Apr 25 00:55 UTC] No.43711958[source]▶
"This block was the result of a communication error between Zoom’s domain registrar, Markmonitor, and GoDaddy Registry, which resulted in GoDaddy Registry mistakenly shutting down zoom.us domain. "
replies(3): >>43711994 #>>43712118 #>>43712177 #
LinuxBender ◴[17 Apr 25 01:00 UTC] No.43711994[source]▶
Something is fishy about this. A communication error would not result in a domain being placed on hold. On hold is usually the result of a legal order or in the case of the .us TLD a nexus compliance violation. I've transferred thousands of domains from assorted dodgy registrars into MarkMonitor and can not even imagine a scenario where a miscommunication results in a domain being placed on hold.
replies(4): >>43712073 #>>43712287 #>>43712366 #>>43712853 #
1. jltsiren ◴[17 Apr 25 01:48 UTC] No.43712287[source]▶
Correctness doesn't scale. If something has six nines of reliability, you'll probably never see the one-in-million outlier yourself. But if the other side deals with a million requests a month, they are a common occurrence.
replies(1): >>43712320 #
2. LinuxBender ◴[17 Apr 25 01:55 UTC] No.43712320[source]▶
Yeah I'm not saying errors don't happen. I've been called into gazillions of them including many that "should not happen". Those make for the best root cause analysis and after action reports.

Rather this does not sound like a communication error unless they are leaving out a lot of critical details and context or the domain management interface has been de-frictioned and dumbed down too much.