17 ms·
Zoom outage caused by accidental 'shutting down' of the zoom.us domain
- RVRX 1y ago"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. "
- LinuxBender 1y agoSomething 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.
- gjsman-1000 1y agoNah, weird stuff that “shouldn’t” happen almost always happens more often than things that “should” happen.
- LinuxBender 1y agoI hear ya but this would more than likely be something like a really sloppy human error such as following the wrong process vs. a miscommunication otherwise I would expect these outages to be much more frequent. I do remember when a fat-finger at UUNET took out most of the internet long ago but that was a human error and is a bit harder to have the same impact today. 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.
- root_axis 1y agoWhat? Weird stuff happens less by definition.
- bombcar 1y agoNot 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.
- LinuxBender 1y agoEvery 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.
- root_axis 1y agoIf there is a "default" then "everything else" is not weird. The conclusion is "this thing doesn't work most of the time so it wouldn't be weird if it doesn't".
- jltsiren 1y agoCorrectness 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.
- LinuxBender 1y agoYeah 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.
- Spooky23 1y ago[flagged]
- eli 1y agoIsn't the stated reason, a miscommunication with the registrar, far far more likely?
- Spooky23 1y agoIn normal times, absolutely. These aren’t normal times.
- varenc 1y agoWhat's the escalation theory here mean? The US shut it down to damage a company it doesn't like? And 2-4 hours is meaningful? or China did it? Maybe it was shutdown and used as negotiating leverage and brought back when some agreement was reached? GoDaddy's involvement really makes me believe that it's a genuine screw up.
- x0x0 1y agoWell, 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.
- pigbearpig 1y agoCould it have been something as simple as "hey, zoonn.us is violating Zoom's copyright, please block it" and then someone typos "zoom.us".
- gkanai 1y agoCompanies pay MarkMonitor to NOT make these mistakes. So... GoDaddy failed?
- devrand 1y agoYeah I don't understand this. MarkMonitor themselves are a registry, so is the potentially a mistake in migrating from GoDaddy to MarkMonitor?
- jsheard 1y agoGoDaddy operates the .us TLD, so Zoom registered the domain through Markmonitor, who acquired it from GoDaddy, who shit the bed and broke everything.
- electroly 1y agoMarkMonitor is a registrar (one of many). GoDaddy Registry is the .us registry operator (the only one); they actually operate the TLD on behalf of the government. In this capacity they are not operating as another registrar, but as the TLD operator.
- timewizard 1y ago"It would be amiss not to start without a reference to AI, as 2024 saw the movements toward legal definitions and prohibited AI practices with the EU’s AI Act. 2024 also saw more innovative integration of AI into registrars’ service offerings, from “chatbots” to registration process flow to domain name generators. We also witnessed the rise of LLM (or Large Language Models) being used in Brand Protection Services and the identification of abusive registrations. This trend will definitely be increasing in 2025." https://www.markmonitor.com/blog/2024-markmonitor-year-in-review/ https://www.markmonitor.com/blog/2024-markmonitor-year-in-re...
- bo1024 1y agoWhat does “shutting down” the domain even mean? Has to be a DNS thing, right?
- colechristensen 1y agoIt's translated through several layers of people who don't know anything. 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.
- manquer 1y agoGoDaddy is the root registry for all .us ccTLD, MarkMonitor is the actual registar Zoom is working with. The issue seems to be more how GoDaddy assigned to the domain to MarkMonitor not something Zoom itself likely controls (such as NS records) .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
- eli 1y agoIt didn't expire
- megamike 1y agooops rolls eyes
- system2 1y agoSomeone 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.
- jeffbee 1y agoThe entire point of MarkMonitor is that won't happen.
- dontdoxxme 1y agoExcept 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.
- londons_explore 1y agoI wonder how long mark monitor would keep renewing the domain without payment...
- system2 1y agoWell then, someone at MarkMonitor forgot to update the credit card, then. hehe
- adrr 1y agoThey don’t use normal registrations. Anyone with any size is using MarkMonitor and do monthly billing and have a dedicated person. No credit cards.
- nulbyte 1y agoI don't think the domain was up for renewal this year. Even if it were, it wouldn't expire until the 23rd.
- be_erik 1y agoI was really hoping to find out they were hosting their DNS on GoDaddy. I still want it to be true.
- johncolanduoni 1y agoIf 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.
- jsheard 1y agoThat makes two reasons to avoid .us domains, the other being that you're not allowed to redact the WHOIS information on those.
- neodymiumphish 1y agoThis shafted me hard when I registered the domain I used to research and write a company blog post (https://www.guidepointsecurity.com/blog/tunnel-vision-cloudflared-abused-in-the-wild/ https://www.guidepointsecurity.com/blog/tunnel-vision-cloudf...). I’ll never deal with a .us domain again, even if it means missing out on a good text string.
- riffic 1y agowormed it is
- oefrha 1y ago[flagged]
- johnklos 1y agoGoDaddy is the registrar. They (Zoom) host their DNS using Amazon.
- LeoPanthera 1y agoAmazing how many service outages are caused by doing business with GoDaddy.
- deleted 1y ago[deleted]
- lucb1e 1y agoAlso 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
- skylerwiernik 1y agoI 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.
- hypercube33 1y agoI've used about 12 registrar's and dns providers and they are trash top to bottom - literally the worst and most difficult to do everything from basic setup to how they do things just plain weird compared to other hosting providers. They also aren't the cheapest option so other than brand recognition I don't get why people use them.
- kstrauser 1y agoLet’s not get carried away. Network Solutions still exists.
- hinkley 1y agoHere's something you all need to learn about site (or for that matter, tool) reliability: Nobody gives a shit about how many good outcomes between incidents there are. They care about how many good hours happen between incidents, and they care how big the incidents are. So if you make a tool that your coworkers use 5 times as much as the old process, that tool better make things at least 6x more stable or people will start talking about how the process fails 'all the time'. "all the time", as near as I've been able to figure out, after people have been yelling at me, my team, or a team I'm privy to, is not "every day". No, all the time just means that it happens every couple of weeks and one time happened twice in one day, twice in consecutive days, or with two customers in rapid succession. Usually the day they're screaming about. So if you're doing that thing every day all day long, where you used to do it rarely, but you made some progress on making it more frequent, nobody cares that it's every 100th run that fails, when it used to be every 10th. They just see the drama has gotten more frequent (and nowhere near as frequent as their narrative says, but you've already lost that argument)
- RVRX 1y agoThe domain status on the whois record was "serverHold" earlier in the day
- ChrisArchitect 1y agoEarlier: https://news.ycombinator.com/item?id=43709266 https://news.ycombinator.com/item?id=43709266
- autoexec 1y agoMarkmonitor and zoom are both terrible companies so I can't feel bad about this
- __float 1y agoWhat's wrong with Markmonitor? They don't have nearly the customer base of Zoom (where I can relate to any complaints, I'm sure)
- autoexec 1y agoThey've earned themselves a reputation for sending false DMCA notices. https://www.inquisitr.com/markmonitor-sends-false-copyright-infringement-notices-six-strikes-already-failing https://www.inquisitr.com/markmonitor-sends-false-copyright-... https://torrentfreak.com/record-labels-defeat-false-dmca-takedown-claims-in-court-210102/ https://torrentfreak.com/record-labels-defeat-false-dmca-tak... https://torrentfreak.com/court-dismisses-charters-claims-of-false-riaa-dmca-notices-201109/ https://torrentfreak.com/court-dismisses-charters-claims-of-... https://torrentfreak.com/hbo-wants-google-to-censor-hbo-com-130203/ https://torrentfreak.com/hbo-wants-google-to-censor-hbo-com-... https://torrentfreak.com/after-4-years-copyright-holders-still-think-megaupload-is-alive-160417/ 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-rightsholders-out-of-millions-150702/ https://torrentfreak.com/anti-piracy-lawfirm-defrauded-right...
- voxic11 1y agoCan you explain what that last article has to do with MarkMonitor? To me it just sounds like MarkMonitor once bought a company from a law firm which was sued for fraud 5 years after the sale was completed. So it doesn't appear that MarkMonitor was in any way related to the fraud which occurred.
- autoexec 1y agoGood call out! If Schlüter didn't continue doing work for DtecNet after the sale to MarkMonitor then we can't really blame MarkMonitor for the things he was doing 5 years later.
- ajdude 1y agoA 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?
- jsheard 1y ago> 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.
- eli 1y agoI don't think that's a real risk
- jsheard 1y agoIt 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.
- apitman 1y agoWhatever happens is going to set some really important precedent for sure.
- TheDong 1y agoI think '.su' is already that precedent, since it had many active domains, recently had active registration, and ICANN has announced plans to phase it out. https://en.wikipedia.org/wiki/.su https://en.wikipedia.org/wiki/.su See also '.yu' and friends, which have already been deleted.
- 1y ago
- stackskipton 1y agoThis 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.
- lolinder 1y agoIt'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.
- stackskipton 1y agoI 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?
- thayne 1y agoPossibly MarkMoniter failed to renew the domain on time? Or there was a miscommunication around payment that led to the domain expiring?
- selcuka 1y agoRenewal date is April 24, so unlikely. Even if it expired this year they would still have a week to renew.
- stackskipton 1y agoThere are status codes around that which would contain the word renew. serverHold is generally only set by registry when they have some pending action which almost always legal related. You can see a list of Status Codes here: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en https://www.icann.org/resources/pages/epp-status-codes-2014-...
- xyst 1y agoZoom, a multibillion dollar corporation, uses the shit tier of all companies, _GoDaddy_, for their registrar? What a blunder.
- lucb1e 1y agoThat's not the registrar, that's the registry
- londons_explore 1y agoGoDaddy runs the .us TLD. You cannot avoid them if you want that TLD
- Geezus_42 1y agoYou can avoid them by not using the .us TLD.
- stock_toaster 1y agoAnd the 5 years or so since Godaddy bought .us should have been long enough to migrate to another name.
- film42 1y agoZoom 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 SLA credits to your revenue impact for a given vendor outage and how that should guide your build vs buy decision framework.
- mikeocool 1y agoYou probably don’t want to optimize for the SLA credit making up for a significant part of your lost revenue — because that would mean when things are operating normally, you don’t have much of a profit margin. SLA’s are generally more helpful for getting out of long term contracts with unreliable vendors than actually making up for revenue lost during an outage.
- kevincox 1y agoSLA credits are an incentive for the service provider not making up for lost revenue from the outage. If you have 100% SLA credit under 99% availability you can't aford to be less than 99% available and I know that your SLA means something to you, not just an aspirational bullet point.
- Geezus_42 1y agoWhy 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.
- kemals 1y agoThousandEyes analysis of the outage: https://www.thousandeyes.com/blog/zoom-outage-analysis-april-16-2025 https://www.thousandeyes.com/blog/zoom-outage-analysis-april...
- bo1024 1y agoThanks, this is really helpful. I had not even realized that every DNS query for .us (for example) goes through a single root registry before going to the actual nameservers.
- hanikesn 1y agoIt's usually cached
- gwbas1c 1y agoThe article lists a lot of facts, but it doesn't actually explain what happened. IE, it explains what DNS is, but it doesn't explain why the outage happened. Instead, it merely gives a timeline with a lot of context that's useful for someone who's still learning about what DNS is and how it works.
- master_crab 1y agoIt’s always DNS!
- imglorp 1y agoIt’s not DNS There’s no way it’s DNS It was DNS
- bongodongobob 1y agoParadoxically, productivity spiked.
- rajeshvar 1y agoFlush the cache instructions were posted under zoom.us :) https://status.zoom.us/incidents/pw9r9vnq5rvk https://status.zoom.us/incidents/pw9r9vnq5rvk
- gblargg 1y agoI thought it was funny that they posted information about the outage on the same domain that had the outage.
- jetsnoc 1y agoThey 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.
- macintux 1y agoIt certainly was frustrating that the status host was also in the zoom.us domain.
- chrisweekly 1y agoIs it just a coincidence that Spotify and Zoom both had massive outages on the same day?
- Animats 1y agoThat seriously devalues MarkMonitor's services. MarkMonitor claims to be a "an ICANN-accredited registrar and recognized industry leader since 1999". The whole point of paying for MarkMonitor is that they're an expensive service for valuable domains and are not allowed to screw up. GoDaddy should not be involved here at all.
- Maxious 1y agoGoDaddy runs the root dns for .us
- dawnerd 1y agoWait really? I use a .us domain for personal stuff, that.. makes me want to reconsider.
- NewJazz 1y agoAlso .us domains don't have who is privacy.
- gerdesj 1y agoPlease don't keep us in suspense ... who is privacy?
- stwrzn 1y agoThey probably meant "whois privacy"[1] (without the space). Whois is basically a way to get information about a domain name (and many other stuff). Whois privacy just ensures that your address, name and other stuff is not public. [1]https://en.wikipedia.org/wiki/Domain_privacy https://en.wikipedia.org/wiki/Domain_privacy
- imcritic 1y agoThey were probably joking when they asked that question. Your reply doesn't seem sarcastic, so I take it you genuinely r/whoosh'ed (that's a reference to a subreddit about situations where someone is acting clueless).
- financetechbro 1y agoLots of “glad Teams is working at least” commentary today across various meetings. Everyone had a good laugh, as it is usually typical to complaint about the how crappy Teams is. +1 for Teams today
- youworkwepay 1y agoNoDaddy!
- wodenokoto 1y agoWould it be safer to hard-code a static IP than a domain?
- Koffiepoeder 1y agoIp's can (easily) be hijacked by nefarious BGP requests and offer no easy SSL. You could maybe add cert pinning to fix that, but it's quite inflexible. Another added bonus of domains is the potential for subdomains to be used. This could be usful for many purposes: as load balancing/pooling mechanism (fictive example us4.zoom.us) and for compartmentalisation (api.zoom.us).
- udev4096 1y agoWhat do relatively large corporations use for their authoritative nameserver? Do they use PowerDNS, knot, bind, or just use the registrar's nameservers?
- jedberg 1y agoGoogle runs their own, Facebook runs their own, Amazon used AWS, Microsoft uses Azure. Netflix uses AWS. Most likely all are running some version of Bind, or something custom.
- bc569a80a344f9c 1y agoAnd if you’re wondering about the hidden authoritative servers (that the company uses to generate and administer the zones then synced to a global DNS provider such as the ones you listed) two rather popular products for companies that aren’t also cloud providers are Infoblox and BlueCat.
- fortran77 1y agoI remember when Kristen McIntyre owned zoom.com back in the early days as her hobby domain.
- vjaowegn 1y ago[dead]
- iqandjoke 1y agoIt should not cause issue as your company should have BCP on this and can switch to other conferencing service.
- ro_bit 1y ago4 hour catastrophic outage because of a shitty domain registrar makes me wonder if zoom will be switching critical services to a different tld sooner or later as a result of this
- Symbiote 1y agoMaybe they will use multiple domains. See for example that AWS Route53 uses com, org, net and uk domains for the nameservers.
- 18172828286177 1y agoGodaddy is such an incompetent organisation. Should not be allowed to administer anything of importance.
- deleted 1y ago[deleted]
- nom 1y agoIt's easy to blame GoDaddy, but 'miscommunication' takes two. You pay Markmonitor a shitload of money to make sure this doesn't happen. They should have dedicated people at GoDaddy and direct communication channels. This is a significant fuckup on Markmonitor's part, even if GoDaddy did something different than was requested from them.
- Hobadee 1y agoI can guarantee you that miscommunication doesn't always require 2 people. Source: Have been OH SO EVER PRECISCE AND EXACT in my communication with certain idiots, and they still screw it up. Several instances of "put this here carefully", only to return and find it all the way across the room upside-down and broken, come to mind.
- subscribed 1y agoMark Monitor have correctly asked for `serverUpdateProhibited`, GoDaddy changed the code to `serverHold` instead. I don't know why you're trying to spin it as Mark Monitor fault.
- gavinsyancey 1y agoWhere are you getting that from? I don't see that info anywhere on the linked page. Is there more information published elsewhere, or do you have insider knowledge?
- hinkley 1y agoWho knew a company who ran ads with women dressed like Hooters waitresses would turn out to be a fucking clowncar. I mean what are the odds?
- Fokamul 1y agoLol, they use GoDaddy? Aka scammers and racketeers? Aaah .us TLD, too bad they have control over it.
- gameshot911 1y agoNoob here: could this issue have been worked around if you had a personal list of the IP addresses that the domain resolved to?
- natebc 1y agoMost DNS issues can, yes. Your hosts file is going to be thick though, and a pain to keep up to date ;P
- blueflow 1y ago> Your hosts file is going to be thick though, and a pain to keep up to date I'm guessing you already know, but for the others: This is precisely what the DNS protocol was created for.
- Galatians4_16 1y agoThis wouldn't happen if it were distributed or decentralized like pre-MS Skype used to be.
- brongondwana 1y agoThis kind of possibility is why Fastmail purchased fastmail.com and migrated away from our old 'fastmail.fm' domain. .fm was cool, but we ran into a couple of outages on the .fm servers meaning we went offline. No such issues since we've been on .com.
- lrvick 1y agoTo try to convince my employer at the time to drop Zoom, I decided to see how many security vulns I could find in 2-3 hours. Found 12 confirmed bugs in that window using only binwalk and osint. The worst was that I noticed the zoom.us godaddy account password reset email address was the personal gmail account of Eric S Yuan, the CEO. So, I tried to do a password reset on his gmail account. No 2FA, and only needed to answer two reset questions. Hometown, and phone number. Got those from public data and got my reset link, and thus, the ability to control the zoom.us domain name. They were unable to find a single English speaking security team member to explain these bugs to, and it took them 3 months to confirm them and pay me $800 in bug bounties, total, for all 12 bugs. The one bright side is this did convince my employer to drop them.
- jaxefayo 1y agoHow long ago was this? A few years ago they were hiring aggressively for security team members in the US, including a dedicated fuzzing team. I’m guessing this was from early on when Zoom was just getting popular?
- lrvick 1y agoAbout 7 years ago
- deleted 1y ago[deleted]
- popcalc 1y agoYou're admitting to committing a felony?
- MiguelX413 1y agoWhite hat hacking is fine.
- popcalc 1y agoIf you password reset my personal Gmail account I will sic the FBI on your tail without a second thought. Not cool.
- AStonesThrow 1y agoBack in 2008, when my fiancée invited me to visit Catalonia, I was in the market for transatlantic airline tickets. And I'd never flown internationally before, and I applied and obtained a US Passport, and I figured out with my father how to get a Travelex prepaid debit card with Euros loaded, and my fiancée was prodding me anxiously about buying a ticket, and I eventually threw caution to the wind and flew on an airline called "ZOOM". Now "ZOOM" was supposedly based in Canada and they were supposedly giving bargain-basement fares to Americans as well, from select origins to select destinations. All I needed to do was to get to Lindbergh Field (San Diego International) and ZOOM Airlines would fly me to London Gatwick. And their aircraft had cute friendly livery with big "ZOOOOOOOOM" lettering on the side. And the price was totally cheap. Well they did their job fine; I landed in Gatwick, took a train to Heathrow, and flew on Iberia into and back out of Barcelona. Unfortunately, before I departed, my father phoned my fiancée to break the news that "ZOOM Airline" was bankrupt, and all their flights were grounded. They had run out of fuel in Scotland, and nobody would top up the tanks. My return ticket from London to San Diego was worthless. So Dad puts me on a British Airways flight and I got home safe. But from August 2008, or before, I have harbored a visceral animosity towards any foreign actors named "ZOOM".
- auliayaya14 1y agowow
- auliayaya14 1y agohow