Petlibro is facing user anger after a smart pet feeder outage left customers unable to control devices through the company’s companion app, according to Ars Technica. The company is owned by Shenzhen, China-headquartered Shenzhen Libro Technology Co., and Ars reports that founder and CEO York Wu has now provided a fuller explanation of what went wrong. Ars reports that Petlibro first acknowledged the outage at 5 am PT on Tuesday, then said at 7 pm PT Wednesday that the outage had been resolved. Some users online disputed that status at the time, and Ars says some people claimed they were still having problems as of August 13. Wu attributed the failure to cloud server issues. According to Ars, he said a backlog of data requests overloaded system memory and brought down device service. After Petlibro restarted the cloud service, the backlog returned and the system failed again, forcing the team into broader troubleshooting before it identified and patched the underlying issue. The customer impact was not limited to cosmetic app features. Ars reports that the app could no longer connect to devices, making device communication unavailable. App-related services including on-demand actions, operation history, records, notifications, and videos were also down. Ars quotes Wu as saying that a “critical error” affected app login and control at 5:20 am PT on Tuesday, August 11. App functionality was restored around 6:20 am PT, but 23 minutes later incoming requests overwhelmed connection capacity and the system failed again. Basic functionality returned at 8:04 am PT, after which Petlibro began restoring other services; when app loading slowed about an hour later, the company scaled back functionality. The recovery timeline extended into Wednesday night. Ars reports that Wu said Petlibro’s development team found a cache issue, disabled service to address it, and implemented a solution at 11:43 pm PT Wednesday. Wu said the company continued watching performance as devices reconnected and did not exit crisis mode until it had seen a full demand cycle. The unresolved question is whether the feeders’ core scheduled feeding function actually survived the cloud failure. Petlibro says scheduled feedings perform offline, according to Ars. Users reported otherwise, and Ars’s headline notes that some accused the company of “gaslighting” users over the discrepancy. With only the provided material, that dispute cannot be resolved; the safe read is that the company and some customers are describing different outcomes from the same incident. Petlibro’s incident communications are also contested. Ars reports that some users said they did not receive emails and were unaware of the technical problems for a period, with one Reddit user criticizing the company’s customer service. Wu said Petlibro sent five emails to active customers with connected devices, posted four updates each to Reddit and Instagram, and created a status page that the company plans to keep online. Petlibro says it has increased demand capacity and is preparing an audit protocol to examine backend inconsistencies, according to Ars. For now, the incident is a reminder that cloud-connected consumer hardware can fail in ways that customers experience as physical-world reliability problems, not just app downtime. Who benefits: Vendors that can demonstrate reliable local scheduling, clear incident status, and post-incident transparency stand to look stronger by comparison. Customers benefit if Petlibro’s reported capacity increase and backend audit reduce repeat failures. Who's exposed: Petlibro is exposed to reputational damage if users believe the company minimized or contradicted their experience. Any connected-device operator relying on cloud control for physical routines faces similar scrutiny when backend failures affect real-world outcomes.