To me a communication error implies someone followed erroneous instructions without asking the obvious, " ... but isn't this a big business that is still live and why don't I have a legal order in my hand?" In fairness this did happen recently with he.net because a sub-domain was reported but it was done intentionally even if they failed to do even basic due diligence. After Covid I would expect most people would know zoom.us would be in use by a lot of people whereas only specific groups of people would know what he.net is.
I am curious if the process has changed due to laziness and now registrars can just select any number of domains and click a button to place them on hold without management or executive approval. If so that should be in some audit trail and should require confirmation and approval by a senior leader.
Their domain expired because at some level people made some pretty boneheaded mistakes.
Whomever their actual registrar actually was (GoDaddy it seems) stopped pointing the zoom.us nameserver record (NS) at AWS Route 53 which Zoom obviously uses.
% dig +short zoom.us NS
ns-387.awsdns-48.com.
ns-1137.awsdns-14.org.
ns-1772.awsdns-29.co.uk.
ns-888.awsdns-47.net.
.us (and other many TLDs) uses EPP to communicate between registars (MarkMonitor here) and Registry (GoDaddy). It is probably an admin error rather than code[1], some manual approval or other human review workflow for high value domain and someone clicked/filled in the wrong value at GoDaddy or MarkMonitor would be my first guess.
[1] would have been observed and fixed long before today, transfers happen all the time after all
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.
https://www.markmonitor.com/blog/2024-markmonitor-year-in-re...
GoDaddy's involvement really makes me believe that it's a genuine screw up.