Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

status.zoom.us

Post reply on HN
Print view View original

31–40 of 324 posts

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

#31

Post by autoexec »

__float wrote: post #25
autoexec wrote: post #19

Markmonitor and zoom are both terrible companies so I can't feel bad about this

What's wrong with Markmonitor? They don't have nearly the customer base of Zoom (where I can relate to any complaints, I'm sure)

They've earned themselves a reputation for sending false DMCA notices.

https://www.inquisitr.com/markmonitor-sends-false-copyright-...

https://torrentfreak.com/record-labels-defeat-false-dmca-tak...

https://torrentfreak.com/court-dismisses-charters-claims-of-...

https://torrentfreak.com/hbo-wants-google-to-censor-hbo-com-...

https://torrentfreak.com/after-4-years-copyright-holders-sti...

They haven't even always been good to their own clients: https://torrentfreak.com/anti-piracy-lawfirm-defrauded-right...

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

#32

Post by ajdude »

A few years ago I had a .us TLD. I eventually decided that I probably shouldn't be reliant on a country code for my domain, it's the same reason why I don't use .io

I'm not saying that this couldn't have happened with a gTLD But why put your brand at the mercy of a government like that?

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

#33

Post by oefrha »

johncolanduoni wrote: post #13
be_erik wrote: post #9

I was really hoping to find out they were hosting their DNS on GoDaddy. I still want it to be true.

If only it were so, then they would have kind of deserved it. TIL GoDaddy wormed it’s way into administering the .us TLD on behalf of the federal government.

[flagged]

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

#34

Post by LinuxBender »

jltsiren wrote: post #30
LinuxBender wrote: post #3

Earlier quoted context omitted.

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.

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.

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.

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

#35

Post by bombcar »

root_axis wrote: post #27
gjsman-1000 wrote: post #5

Earlier quoted context omitted.

Nah, weird stuff that “shouldn’t” happen almost always happens more often than things that “should” happen.

What? Weird stuff happens less by definition.

Not necessarily. The default could happen 49% of the time, and everything else happens way less than 1%, but is weird.

So 51% of the time it’s weird, but not the same weird.

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

#38

Post by jsheard »

ajdude wrote: post #32

A few years ago I had a .us TLD. I eventually decided that I probably shouldn't be reliant on a country code for my domain, it's the same reason why I don't use .io I'm not saying that this couldn't have happened with a gTLD But why put your brand at the mercy of a government like that?

> it's the same reason why I don't use .io

Dodged a bullet there given that .io is at risk of being discontinued altogether. It hasn't been decided yet, but better to not have that dangling over your head.

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

#39

Post by LinuxBender »

bombcar wrote: post #35
root_axis wrote: post #27

Earlier quoted context omitted.

What? Weird stuff happens less by definition.

Not necessarily. The default could happen 49% of the time, and everything else happens way less than 1%, but is weird. So 51% of the time it’s weird, but not the same weird.

Every place I've been we measured such weirdness outside of the 95'th and 99'th percentile. Anything out of common occurrence beyond the 99'th could be weird or interesting or fascinating. I still wish I could share the incident of a single NIC on a single server taking down an entire data-center, that was both weird and fascinating.

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

#40

Post by dontdoxxme »

jeffbee wrote: post #20
system2 wrote: post #6

Someone in the Zoom company management forgot to update the billing credit card for that domain, I bet you $1000. Happens all the time with our clients.

The entire point of MarkMonitor is that won't happen.

Except while it probably wasn’t a credit card expiry it did result in the domain being suspended. Looks pretty bad for MarkMonitor. They didn’t do the “monitor” part of their name.
Post reply on HN