Randy Pitchford says a Pixel Watch 5 leaked underwater near St. Martin

Gearbox CEO Randy Pitchford says a friend found what appears to be a Google Pixel Watch 5 underwater near the island of St. Martin, then shared details publicly. Pitchford posted on X that “a friend” “inadvertently stumbled upon what appears to be a Pixel Watch 5, which Google has yet to announce,” and added that the watch was underwater when it was discovered during scuba diving.

In the post, Pitchford wrote: “A friend of mine found this watch a few days ago ~underwater~ when he was scuba diving near the island of St. Martin,” and that “the reverse of the watch indicates that it is a Google Pixel 5, which has not yet been released.” He also said the watch “seems to be fine” except for an empty battery, and shared it because his friend “seems to believe I am connected in the tech industry.” The post included images of the front and reverse, including “Google Pixel Watch 5” written around the underside. Pitchford later updated that he is “now in touch with the owner” and “we’ve arranged for its return.”

So, yes, the premise sounds like a sketch. But leaks happen, and the mechanics here are worth noticing, especially if you run product, security, legal, or investor communications. Games and tech products can leak in strange ways, and this one is basically the extreme version of “someone left a dev unit in the wild.” Pitchford is not claiming this is a deliberate marketing move. Instead, the story hinges on an accident: an underwater discovery plus identifiable hardware markings.

If the device is real, the bigger story is what it implies about the watch’s design and test readiness. As PC Gamer notes via GSMArena, the image reveals multiple specs consistent with a Pixel Watch. Those include IP68 ingress protection, a heart rate sensor, UWB chip, pulse sensor, spO2 and skin temperature tracking. IP68 is the kind of line that normally lives in spec sheets, not on ocean floors. That makes the “underwater” angle feel less like pure internet theater and more like a practical proof point for water resistance.

Still, because the watch was unannounced, the leak immediately creates a tension that every product company knows well: the distance between internal testing and public reality. Even a single identifiable unit, once posted, compresses weeks or months of planning into hours of public speculation. People inevitably asked whether Pitchford made it up. PC Gamer frames the skepticism as understandable, noting that finding an unannounced smartwatch in the ocean off a Caribbean island is “an extremely unlikely event.” But the practical details in the photos, plus the follow-up return effort, are the counterweight that keeps the story from feeling entirely hollow.

Pitchford’s own update matters here. He said he got in touch with the owner and arranged for the watch’s return, and he signed off by telling people: “If you find something that isn’t yours, pay it forward and try to return it to its rightful owner.” That is not the kind of language you use for a casual hoax that requires long-term commitments to a return. It also adds a real-world compliance angle: if you are handling leaked hardware or seized units, the chain of custody and responsible handling can determine whether something becomes a legal headache or a reputational moment.

For decision-makers, the second-order implications are not “watch leaks are funny.” They are about process. How do unannounced devices get to places where they can be lost? How often do internal carriers, testers, employees, and contractors travel with prototypes, and what controls exist when devices are outside secured facilities? Even if the original incident was an accident, the outcome shows how quickly a prototype can become public intelligence through social platforms.

Regulatory and compliance framing is also relevant, even without formal filings in this story. IP claims like IP68 are typically scrutinized in product contexts, and health-related sensors such as spO2 and skin temperature tracking sit in a category where regulators and consumer expectations can be sensitive. If a prototype’s specs are visible early, it can shape narratives before official documentation lands. It can also influence competitor assumptions about roadmap priorities, packaging of features, and timing. That is not “someone spilled secrets.” It is the market practicing inference at full speed.

Meanwhile, executives in adjacent industries should note the broader pattern. The leak story is in gaming adjacent circles because Pitchford is a high-profile tech figure, but the underlying lesson is cross-industry: secrecy is a system, not a statement. One lost device plus a recognizable underside label plus public images equals accelerated disclosure, whether the disclosure was intended or not. And because the watch appears to be “fine” aside from having an empty battery, the event also underscores how durable prototypes are designed to be, sometimes beyond what most people imagine.

As for why anyone would test water resistance near Saint Martin, the article calls it “a mystery,” and leaves that as speculation. The more important take is simpler: product teams design for extremes, and extremes are exactly where accidents happen. If you are on a board, running a product org, or managing investor comms, the strategic stake is clear. Every unannounced device is a potential information leak. Every leak becomes a test of your response discipline. And sometimes, the most consequential disclosure starts underwater.