Flush the cache instructions were posted under zoom.us :)
Zoom outage caused by accidental 'shutting down' of the zoom.us domain
71–80 of 324 posts
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#72Earlier 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.
[flagged]
Well, Zoom also lied about their encryption (or, perhaps more charitably, described it in a misleading way. nah, they just lied) and was directing traffic through chinese servers with no reason for doing it -- it was occurring when all meeting participants and the company paying for the zoom account were outside China -- besides enabling spying.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#73They need to implement secondary and tertiary domains—with diverse registrars and hosting infrastructure—for the Zoom client’s calling home. Maybe even a fallback anycast ip address for service discovery. Given how much companies like mine pay for service, it’s reasonable to expect that level of engineering foresight. But hindsight will do—let’s get it fixed. #HugOps to all employees working overtime and taking care of this.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#74Amazing how many service outages are caused by doing business with GoDaddy.
Also after dividing the number of outages by the number of customers? I'm not a customer (wouldn't buy my domain overseas) and have no solid opinion on GoDaddy besides that I hate the name. I hear the horror stories also. I'm just wondering if this is a knee-jerk reaction
I bought my first domain from GoDaddy in high school. I remember them having the slowest dns portal in the world, and having to call support at least once about something they screwed up. Don't really remember the details, but I remember them causing problems and losing my business within a year. I've used at least 3 other registers since then and never had a single problem.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#75Zoom CEO: Hi, we'd like an SLA credit for the global outage you caused our company. GoDaddy: I am so sorry about that. I can offer you a one-time coupon for $10 off your next purchase or renewal. Would you like me to apply this to your account? --- Most companies just hope an apologetic zoom call is enough to retain your business, and most of the time it works. Not enough has been written about the asymmetry of your…
Can’t have an apologetic zoom call when zoom is down …
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#76It’s always DNS!
It’s not DNS
There’s no way it’s DNS
It was DNSRe: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#77Zoom CEO: Hi, we'd like an SLA credit for the global outage you caused our company. GoDaddy: I am so sorry about that. I can offer you a one-time coupon for $10 off your next purchase or renewal. Would you like me to apply this to your account? --- Most companies just hope an apologetic zoom call is enough to retain your business, and most of the time it works. Not enough has been written about the asymmetry of your…
Why would you use godaddy for a service as large as Zoom? They have been garbage for years. The way they locked out their ACME api for anyone but top tear clients sealed the deal for me. I would never trust them.
Companies as big as zoom are still perfectly capable of having a high level VIP decide "we're going to use GoDaddy because I saw their Superbowl ad".
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#78Zoom CEO: Hi, we'd like an SLA credit for the global outage you caused our company. GoDaddy: I am so sorry about that. I can offer you a one-time coupon for $10 off your next purchase or renewal. Would you like me to apply this to your account? --- Most companies just hope an apologetic zoom call is enough to retain your business, and most of the time it works. Not enough has been written about the asymmetry of your…
Why would you use godaddy for a service as large as Zoom? They have been garbage for years. The way they locked out their ACME api for anyone but top tear clients sealed the deal for me. I would never trust them.
They don't use Godaddy directly. Godaddy is the registry for .us. Zoom's registrar is MarkMonitor, who appear to be at fault for this outage.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#79Earlier quoted context omitted.
I don't think that's a real risk
It wouldn't be the first time a ccTLD has been retired after its country ceased to be, though it would be the most disruptive given how popular it is, hence the uncertainty as to what they'll do this time.
Whatever happens is going to set some really important precedent for sure.
Re: Zoom outage caused by accidental 'shutting down' of the zoom.us domain
#80Zoom CEO: Hi, we'd like an SLA credit for the global outage you caused our company. GoDaddy: I am so sorry about that. I can offer you a one-time coupon for $10 off your next purchase or renewal. Would you like me to apply this to your account? --- Most companies just hope an apologetic zoom call is enough to retain your business, and most of the time it works. Not enough has been written about the asymmetry of your…
Why would you use godaddy for a service as large as Zoom? They have been garbage for years. The way they locked out their ACME api for anyone but top tear clients sealed the deal for me. I would never trust them.
From the linked article
> 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.
Markmonitor is used by some fairly large corps and web properties. It’ll be interesting to find out exactly what this miscommunication was.