"Feedly's Weeklong Slowdown and the Quiet Staying Power of RSS"

For a week, the web's largest standalone RSS reader ground to a crawl. Feedly — the service that inherited the throne when Google shut down Reader in 2013 — saw its web app become, in the words of frustrated users on Reddit, "unusably slow." The story is a useful window into a corner of the internet that rarely makes headlines, and into what happens when a mature product tries to grow a second life on top of its first.

The root cause, once the company tracked it down, was disarmingly mundane. Feedly CEO Edwin Khodabakchian told TechCrunch that the front-end team traced the slowdown to the "Mark as Read" action on accounts holding a large number of folders, and that a fix shipped on Friday. There's something almost comforting about that: after a week of user complaints and speculation about whether the company had quietly deprioritized its core product, the culprit was a routine state-management bug, not a strategic betrayal.

But the speculation wasn't unreasonable. Feedly has spent recent years repositioning itself around cyber threat intelligence, selling businesses a way to track emerging threats and tailored intelligence through the same reading surface its 15 million consumers use. When a core app slows down and support requests go unanswered, users naturally ask whether they're the ones being left behind. It's a question every company with a successful legacy product faces the moment it announces a pivot.

The CEO's answer is worth reading closely, because it reframes the whole episode. "Despite the pivot to cyber threat intelligence, fixing the basic RSS functionality is still a priority," he said, "because our CTI community uses the news-reading capability." In other words, the enterprise product isn't a replacement for the RSS reader — it's built directly on top of it. The consumer reader isn't a legacy burden being maintained out of obligation; it's load-bearing infrastructure for the new revenue line.

That's the first insight this story surfaces, and it's more interesting than the bug itself. A well-run pivot often looks less like abandoning the old thing and more like letting the old thing become the platform for the new one. Feedly's threat-intelligence customers are, underneath the enterprise wrapping, reading feeds — the same unread counts, the same folder structure, the same "Mark as Read." The two products share a core, which is precisely why a bug in that core could hurt both.

The technical failure is also a classic. Bulk "Mark as Read" operations on many-folder accounts are a textbook read-state synchronization problem: marking a batch of items read has to fan out updates across every folder's unread counter, and a naive implementation can issue a cascade of writes that turns a single click into a storm of backend work. Anyone who has built a feed aggregator recognizes the shape of this bug — Google Reader itself wrestled with read/unread state consistency at scale for years. The hardest performance problems in mature software are rarely the headline features; they're the mundane chores that quietly accumulated edge cases over a decade.

There's a broader lesson about maintenance and trust in here too. The same week, Feedly retired its Classic mobile app without advance notice because it no longer met iOS and Android requirements — a decision that only affected a few hundred users, but which compounded the impression that the consumer side was an afterthought. The company's fix wasn't just the code change; it was restoring the communication channel. After publication, the issue was added to status.feedly.com so users could see it was a known, actively-researched problem. Small transparency gestures like that do a lot of heavy lifting.

And the whole episode is a reminder of how stubborn RSS has been. A format that predates smartphones and social-media feeds has quietly outlived a parade of supposedly superior alternatives, because it remains one of the last widely-supported ways to read the open web on your own terms — no algorithm deciding what you see, no engagement-maximizing ranking reshuffling your reading list. That user-controlled model is exactly why a weeklong slowdown felt so acute to the people who depend on it.

The most reassuring detail in the whole story may be that Feedly is still here at all. A decade ago, the shutdown of Google Reader was read by many as the death knell for RSS; instead, the audience simply migrated, and a product that exists specifically to serve those readers became the category leader. A weeklong bug and a Friday fix are, in that longer arc, evidence of a platform that is still actively maintained rather than being wound down.

Sources: - TechCrunch: Feedly attributes weeklong slowdown to bug, not its AI pivot - Feedly status page - RSS 2.0 specification