A Petlibro feeder outage disrupted the company’s app and remote controls this week, and some owners reported that scheduled meals were missed, incomplete or late. Petlibro says saved feeding schedules are stored on the devices and should run without an internet command, but it is reviewing cases where customers said that did not happen.
The distinction matters for people using the machines while away from home. A remote command such as the app’s “Feed Now” button depends on the app connection, according to Petlibro CEO York Wu. A previously configured schedule is supposed to be executed by the feeder itself, even when the network path to Petlibro’s servers is unavailable.
Ars Technica reported that Wu attributed the incident to the way Petlibro’s app communicates with devices through the company’s online servers. The evidence available does not establish why some owners reported failed schedules, which feeder models were involved, how many customers were affected, or whether any animals were harmed.
Did Petlibro feeders keep feeding pets during the outage?
Petlibro’s answer is that they should have. Wu told The Verge that schedules are programmed directly onto the feeder and should continue without an internet instruction. Product pages for the company’s Granary 2 and One RFID models similarly say scheduled meals continue during offline or network-error conditions.
That claim conflicts with reports from users cited by Ars Technica. Some said their devices skipped scheduled feedings altogether; others said meals were dispensed only inconsistently or later than planned. Petlibro acknowledged reports that devices had not behaved as expected and said it was examining those incidents one by one.
Those accounts are customer reports, not independently verified findings. They do, however, undercut any easy assumption that a local schedule necessarily insulated every feeder from an outage in the connected service.
What Petlibro says happened
Petlibro first acknowledged the disruption at 5 a.m. PT Tuesday, saying some users were unable to access the app or control devices remotely. At 7 p.m. PT, the company said it had identified an issue affecting app access and responsiveness and had begun recovery work and system validation.
At 7 p.m. PT Wednesday, Petlibro said app services had been fully restored and were operating normally. Ars Technica also reported that some users continued to say they were having trouble after that update, so the restoration status remains a company statement rather than an independent all-clear.
Petlibro warned that records created during the disruption might not be recoverable. The potentially missing data includes device-operation history, feeding and litter-box records, notifications, cloud videos and highlight clips. That does not prove a missed meal, but it could make it harder for an owner to reconstruct what a device did while the service was down.
For a smart feeder, the practical fault line is clear: remote monitoring and manual app controls can fail with the service, while scheduled feeding is intended to survive locally. This incident leaves an unresolved question about why some customers say that separation failed in practice.
This story draws on original reporting from Ars Technica.
