"The AWS outage has impacted some of our users since last night, disrupting their sleep. That is not the experience we want to provide and I want to apologize for it. We are taking two main actions: 1) We are restoring all the features as AWS comes back. All devices are currently working, with some experiencing data processing delays. 2) We are currently outage-proofing your Pod experience and we will be working tonight-24/7 until that is done."
"Eight Sleep users will be relieved to hear that the company is working to make their products usable during Internet outages. But many are also questioning why Eight Sleep didn't implement local control sooner. This isn't Eight Sleep's first outage, and users can also experience personal Wi-Fi problems. And there's an obvious user benefit to being able to control their bed's elevation and temperature without the Internet or if Eight Sleep ever goes out of business."
"For Eight Sleep, though, making flagship features available without its app while still making enough money isn't easy. Without forcing people to put their Eight Sleep devices online, it would be harder for Eight Sleep to convince people that Autopilot subscriptions should be mandatory. Pod hardware's high prices will deter people from multiple or frequent purchases, making alternative, more, frequent revenue streams key for the 11-year-old company's survival."
Malfunctioning devices and server outages caused users to stay awake for hours and wake up drenched in sweat, with alarms failing during Eight Sleep server downtime. CEO Matteo Franceschetti apologized and said the AWS outage disrupted users, announced restoration of features as AWS recovers, and committed to outage-proofing efforts with round-the-clock work. A local control option was promised by Wednesday at the latest. Users questioned why local control was not implemented earlier given prior outages and personal Wi‑Fi issues. The company faces a tension between providing offline functionality and preserving subscription-driven recurring revenue amid high hardware prices.
Read at Ars Technica
Unable to calculate read time
Collection
[
|
...
]