←back to thread

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

(status.zoom.us)
634 points RVRX | 1 comments | 17 Apr 25 00:55 UTC | HN request time: 0s | source
Show context
stackskipton ◴[17 Apr 25 01:55 UTC] No.43712323[source]▶
This smells like something happened with MarkMonitor, they accidently flagged zoom.us as brand spoofing and filed copyright complaint with GoDaddy who runs .us TLD. GoDaddy suspended the domain per the complaint.
replies(3): >>43712353 #>>43712476 #>>43712844 #
lolinder ◴[17 Apr 25 02:01 UTC] No.43712353[source]▶
It's possible, but MarkMonitor is Zoom's registrar, so there are plenty of other ways for a miscommunication between MarkMonitor and GoDaddy to cause this. Copyright complaints would be a more reasonable theory if MarkMonitor were mentioned and didn't have any other involvement.
replies(1): >>43712442 #
stackskipton ◴[17 Apr 25 02:15 UTC] No.43712442[source]▶
I guess but if MarkMonitor accidently suspended it, it would be ClientHold but it was widely reported it was showing as ServerHold.

ServerHold is used with Registry (GoDaddy in this case) is disabling vs ClientHold is when registrar is pulling the plug (MarkMonitor)

So what would have MarkMonitor said to GoDaddy to cause them to ServerHold a domain?

replies(2): >>43712914 #>>43713818 #
1. altairprime ◴[17 Apr 25 06:49 UTC] No.43713818{3}[source]▶
At one point on a trip to Hawaii I was detained in my room by hotel security for fifteen minutes after requesting a room key to replace the one I lost.

It turns out that they had typo’d 12 into the request type field instead of 1, and type 12 was “Covid lockdown protocol with security enforcement” leftover from 2020 and latent in their systems.

Depending on MarkMonitor have chosen to integrate with each other to handle the sort of trademark management that is MarkMonitor’s premium offering, either or both parties could have simply been off-by-one or typo’d in a transaction to cause this. It’s absolutely plausible to create a confusing nightmare outcome with a one-byte error. (And we’re having quite incredible cosmic rays today, so I hope they’re using ECC RAM!)