DropCatch glitch: Everything but the KitchenBowl.com

The domain KitchenBowl.com was a surprise drop from Amazon’s registrar; as an exact match of “kitchen bowl” the domain was used as a social community for foodies to share & discover recipes.

Between 2015 and 2020 the domain and assorted app most likely generated millions of page-views and when the domain dropped inexplicably, bidders went after it once it was caught by DropCatch.

We followed the auction that closed at a whopping $5,673 dollars. One of the participants was the Domain King, Rick Schwartz, who believed he was the winner of the auction for KitchenBowl.com.

The Domain King had placed a max bid of $5,623 dollars and the clock ticked all the way down to zero, indicating he had won the auction.

To Rick’s surprise, that wasn’t the case. A bidder won the auction at $50 dollars more than Rick’s proxy bid; quite understandably, Rick questioned the legitimacy of the process via a series of tweets:

In recent days, we’ve witnessed the same issue on DropCatch and have notified them about an existing glitch.

It seems that the in-browser code and the one running on the DropCatch server get out of sync, losing the bidder’s ranking when a higher bid is made but without signaling an update to the browser.

In other words, unless a bidder forcibly refreshes the browser, something less easy on a mobile device, the browser displays an outdated bid. The timer clocks down to zero, all while fresh bids have taken over the auction’s fate.

Hopefully, DropCatch will fix this issue soon; in the meantime, you might want to get an add-on such as Tab Reloader for Firefox.

Copyright © 2022 DomainGang.com · All Rights Reserved.

Comments

4 Responses to “DropCatch glitch: Everything but the KitchenBowl.com”
  1. BullS says:

    In my humble networking experience, it has to do with “High-Frequency Trading”

    Whose network is the fastest and closest to the Servers, will win the execution.

    This is how High-Frequency Trading works….
    “from the time it receives market information from a stock exchange to the time it sends out a “buy” or “sell” order—to just 85 nanoseconds”

  2. DomainGang says:

    BullS – Good suggestion but this isn’t about dropcatching domains via the Registry, it’s about bids on a platform (like other platforms: Sedo, SnapNames, Pool, NameJet) that fail to display accurate information. Internet connection speeds are barely relevant, code that works as expected is relevant.

  3. BullS says:

    If there are 10 bidders all around the world and one is closes to the Servers, all bid at the same time, all hit the Enter button at the exact nanosecond at 1 second before the closing time,
    who is going to win the bid???

  4. SV says:

    we had issues with DC as well, luckily DC was very understanding, which told me they’re aware of the issues.
    After spending over 1m with them, we stopped actively bidding.

Leave a Reply

Your email address will not be published.

 characters available