FAQ

Did PETLIBRO feeders actually miss meals during the August 2026 outage? Yes, and owners documented it. One report described two RFID feeders on the same schedule where only one dispensed at the 5 a.m. breakfast while the other blinked Wi-Fi symbols. Another owner came home from a trip to find their cat behaving differently and realized feedings had been missed, then asked when the outage started so they could count the lost meals. PETLIBRO later said schedules stored locally would continue to run; owners filmed the opposite.

Why did the local scheduling promise fail? That is the exact question in the 313-upvote open letter from August 12: if a feeder was powered, configured, and had a schedule saved locally, how did a server outage prevent that meal from dispensing? The letter asked whether some server-side dependency still executes schedules and demanded a technical explanation. The company never published one. CEO York Wu told The Verge devices were not behaving as expected, and the outage article was updated with a recovery notice, but the mechanism was never explained.

How can I test whether my feeder really works offline? Do a dry run before a trip: unplug your router for 24 hours and watch whether the feeder dispenses at its scheduled times. If it does, the schedule lives on the device and the dispense action does not need the server. If it does not, that machine cannot be your only feeding plan while you are away. Ask the seller two direct questions first: where is the schedule stored, and does the feeder need to contact the server to authorize a meal?

Can a smart feeder be a security risk on my network? One PETLIBRO Granary feeder reportedly started answering DHCP requests on its owner’s home network after the August outage and handed out a wrong gateway address, which made other devices randomly lose internet. Treat pet feeders and cameras like any IoT device: put them on a guest or IoT network, keep firmware updated, and do not assume a feeder has no network privileges beyond its own server.

What feeder should I buy if I want offline reliability? The safest pick in our coverage is the PetSafe Smart Feed, about $120.99 with a 4.0/5 rating on Amazon: the schedule is stored on the device, there is no membership, and support answers. The HoneyGuardian S25 is worth watching as proof that local scheduling works in practice: owners who switched after the outage reported it kept dispensing because it runs on an internal clock that does not need the server.

The short answer: PETLIBRO told owners during the August 2026 server outage that feeders would keep dispensing because schedules were stored locally on the device. They did not. Between August 11 and August 21, owners posted at least 14 separate reports of missed meals, feeders that would not reconnect, a support desk that went silent, and one unit that started handing out wrong network addresses. The 313-upvote open letter asking how a locally saved schedule could fail got no technical answer.

I spent Friday night reading the r/Petlibro threads from those ten days, because our first outage article covered the event itself and the aftermath turned out to be the more useful story. Every complaint traces back to one sentence PETLIBRO repeated during the outage. The gap between that sentence and what owners filmed is this whole article.

What did PETLIBRO promise during the outage?

The short answer: an official statement that went out during the outage said schedules saved on the device would keep running, and owners treated that as a guarantee they could trust.

The statement, quoted in a summary thread on r/LinusTechTips from August 12 with 208 upvotes:

Existing settings and schedules stored locally on your device will continue to operate as programmed.

If you buy a cloud feeder, this is the promise you are actually buying: your cat gets fed even when the company’s servers do not exist. The thread’s author, who works from home, still missed feedings on a schedule that had been configured for years and never changed. The Verge interviewed CEO York Wu, who said devices were “not behaving as expected.” PETLIBRO announced recovery on the evening of August 12; on August 13, devices were still dropping offline.

What did owners film instead?

The short answer: a dual-RFID setup where only one of two feeders dispensed at breakfast, a feeder that reset itself when unlocked, another that could not reconnect until batteries were inserted, and cats waiting at empty bowls.

The clearest evidence is the August 11 report of two RFID feeders on one schedule:

At 5 a.m. breakfast time, you can clearly see only one dispenser illuminating… The other feeder screen blinked with the wifi symbols and did nothing.

Two feeders, same schedule, one meal. That is not a hardware fault in one unit; that is a server dependency deciding which device gets to work.

An owner who was away during the outage came home to find their cat acting differently before they understood why:

I assumed that when you set a schedule, the feeder will run on that schedule using a local memory. I cannot trust Petlibro anymore and will never purchase one of their products again.

His closing question deserves to be quoted: “When did this outage start so I can determine how many meals my cat missed?”

Two other owners documented the failure at the device level. One tried to unlock the first feeder and it reset itself, while the second feeder’s buttons went dead: “They are plugged in, have batteries and are supposed to be rock solid even with power and network outages. They are not.” Another reset both feeders during the outage and one could not be rediscovered until batteries were added — backup batteries became the difference between a working feeder and a brick.

The mood in the subreddit that week is well captured by a 177-upvote sarcasm post:

You learn about how great their customer service is… zero of my dry food feeders will keep my cats alive when they have a outage with their servers. This helps me test my cats fasting abilities - this is the greatest thing to ever happen! Trust me - if it’s not working, it’s a feature!

The 313-upvote question nobody answered

The short answer: an open letter asked, in public, how a powered feeder with a locally saved schedule could miss a meal because of a server outage. It was upvoted 313 times and never got the technical explanation it demanded.

The open letter from August 12 is the most important document from this whole episode:

So if a feeder was powered, properly configured, and had a schedule already saved locally, how did a server outage prevent that meal from dispensing?… Was there still some server-side dependency involved in executing the schedule?… This is about food not being dispensed to animals who were supposed to be fed. That deserves a technical explanation, not just an outage apology.

The owners supplied power, configuration, and a saved schedule. The only variable left is the server. The question was never answered in public. Two units arriving from Amazon that week went straight back in the return box.

One 24-upvote post about the PETLIBRO ONE feeder added the uncomfortable implication: if schedules live on a server, the company can also disable your unit remotely. “At any point, this company could be able to disable the use of your unit at any time remotely.” That is the difference between owning a feeder and renting one.

What happened when owners tried to get help?

The short answer: support replied with nearly identical AI-written apologies, missed its own 48-hour promises for weeks, and one warranty claim filed on August 7 stopped getting answers on August 11.

An August 17 post with 85 upvotes described the pattern precisely:

Petlibro just laughed in our faces with clear AI written apologies and shut down their customer service emails, as if we were writing emails to an AI bot with a script that says ‘Respond in an apologetic manner, but don’t promise a fix.’ It’s the same emails everytime, nearly word for word.

The same owner wrote the sentence that sums up the stakes: “No amount of gaslighting & ignoring emails can promise that your animal will be properly taken care of while you’re away.”

The warranty side is worse. An August 21 report about a Polar wet food feeder described a sliding door that stopped closing reliably — “a major safety hazard if you rely on it to feed your pets while away.” The owner submitted a warranty claim on August 7, uploaded video, sent receipts. Silence since August 11. Follow-ups unanswered. The support phone number (1-855-920-4555) plays “no agents available.” Two tickets, #626959 and #631344, both open.

The same day, another Polar owner reported their second unit spinning continuously, a warranty replacement received one month earlier after the first unit died at two months. The design that was supposed to feed a pet while you travel does not survive a month of normal use for these owners.

One feeder turned into a rogue DHCP server

The short answer: a Granary feeder started answering DHCP requests on its owner’s network after the outage and assigned a wrong gateway address, so other devices randomly lost internet.

This one belongs in a different category. An August 13 report with 34 upvotes:

Since their recent service outage, my Granary smart feeder has been responding to client DHCP requests and giving clients an incorrect gateway address… it has the effect of other devices on my network randomly not having Internet connectivity.

A pet feeder should be a client on your network, not a server. When a feeder starts answering DHCP, it can cut off every device in the house. This part never makes the marketing page: a cloud feeder is network infrastructure, and it misbehaves like one. If you keep any feeder or camera on your main network, move it to a guest or IoT network and check what it is actually doing on the wire.

What does local scheduling actually require?

The short answer: three things: a schedule stored on the device, a clock that keeps time without the internet, and a dispense action that does not ask the server for permission. You can test all three in an afternoon.

• Schedule storage: where does the app write your feeding times? On the device or on the server?
• Timekeeping: does the feeder have an internal clock, or does it ask the server for the time?
• Dispense authorization: when 7 a.m. arrives, does the feeder just rotate, or does it phone home first?

The practical test costs nothing: unplug your router for 24 hours and watch the bowls. If meals arrive, the design is genuinely offline. If they do not, you have your answer before a trip, not during one.

Local scheduling is not a myth. Owners who switched to the HoneyGuardian S25 after the outage reported it kept dispensing because it runs on an internal clock with a 12-hour sync cycle, and its dual dispensing ports do not rely on a baffle to split portions. Support confirmed scheduling continues after a server shutdown. We have not reviewed that unit yet; treat it as evidence that the design exists, not as our recommendation. A feeder with a real local schedule was available this summer. The technology was not the obstacle.

The promise vs the receipts

Four questions to ask before you buy a cloud feeder

This is the list I wish the owners in those threads had been handed before purchase. It takes ten minutes and it catches the whole August pattern.

#	Question	What a trustworthy answer looks like	What a red flag looks like
1	Where does the schedule live?	On the device. The seller can say it plainly	“It’s cloud-synced” or any hedging
2	Does the feeder phone home to dispense?	No. The internal clock triggers meals alone	Server authorization is required at feed time
3	What happens during an outage?	A documented offline mode, tested by owners	Silence, or reassurances with no mechanism
4	What do third-party forums say?	Real incident threads with real dates	Criticism gets deleted or support stops answering

One more check that takes five minutes: search the brand name plus “outage” or “stopped working” and read what comes up. Then search the brand’s own site for the same problems. The owners in these threads learned more about PETLIBRO from each other than from PETLIBRO.

What to buy instead

If you want a feeder that feeds when the internet does not exist, the pick from our PETLIBRO vs PetSafe comparison stands: the PetSafe Smart Feed (about $120.99, 4.0/5 on Amazon) stores its schedule on the device, charges no membership, and its support desk answers. It will not take a video of your cat eating, but it will feed your cat, which is the function that mattered in August. See our feeder reputation showdown and the full PETLIBRO feeder review for the longer version of why.

The broader lesson from this brand’s August applies beyond feeders. The same company’s stainless fountain sliced owners’ fingers during the same month, with warnings added to the app only after the injuries. Two separate failure modes, same playbook: promise first, document later, answer never. We track this brand’s record in our outage timeline article and update it as the story develops.

The schedule was never the question. The trust was. A feeder that needs its own company’s permission to feed your cat is not a feeder; it is a subscription to someone else’s uptime. Test the offline claim before you need it, because the owners in those threads found out the hard way that the promise and the receipts did not match.