Feedly Traces Weeklong Slowdown to Folder Bug, Not Its AI Pivot
Feedly has blamed a weeklong web app slowdown that left paying subscribers calling the product "unusably slow" on a bug tied to the "Mark as Read" function on accounts with a large number of folders. The company released a fix on Friday, August 14, 2026, according to TechCrunch.
The slowdown lasted more than a week. During that period, paying subscribers reported that support requests went unanswered. Feedly's official status page, last updated August 17, 2026, recorded no incidents for the month of August, a discrepancy between the platform's incident reporting and what users actually experienced.
Feedly says on its website that it is the largest standalone RSS reader worldwide, with 15 million users. RSS (Really Simple Syndication) is a technology that lets you subscribe to news feeds from websites and read them in one place. The company has been pivoting toward AI-powered cyber threat intelligence, offering businesses tools to track emerging security threats and maintain tailored intelligence feeds through its application. CEO Edwin Khodabakchian told TechCrunch that fixing basic RSS functionality remains a priority despite the strategic shift, because the threat intelligence community itself relies on the underlying news-reading capability.
The timing of the slowdown overlapped with other platform changes. On August 5, 2026, Feedly shipped an update labeled "AI updates and bug fixes" that added new ways to work with AI across the platform while addressing crashes, sync issues, and layout bugs, per the company's changelog. Two weeks before the fix landed, Feedly retired its Feedly Classic mobile app. Khodabakchian said the legacy app no longer met certain iOS and Android platform requirements.
That cluster of changes, an AI-focused update, the retirement of a legacy client, and then a performance regression, is the kind of sequence that invites questions about where engineering resources are being directed. Khodabakchian's explicit statement that RSS functionality remains a priority appears aimed at that concern. The bug itself is tied to folder-count scaling on the Mark as Read operation, a straightforward performance issue: the function's processing cost grows with the number of folders a user has set up, so accounts with heavy folder structures are pushed into degraded response times.
The gap between the status page reporting no incidents and users describing the app as "unusably slow" is worth pausing on. Status pages reflect what an engineering team has formally classified and acknowledged, not necessarily what end users experience. When a slowdown is gradual rather than catastrophic, latency creep rather than an outage, it can fall below the threshold that triggers an incident post while still being severe enough to make a product unusable for daily work. For a tool that many of those 15 million users open first thing in the morning to check their feeds, even a week of elevated latency is operationally disruptive.
The threat intelligence angle adds another dimension. Feedly's CTI customers are not casual feed readers; they are security teams for whom feed latency can mean a delay in surfacing an emerging indicator of compromise. Khodabakchian's point that the CTI community uses the RSS layer directly is well taken, because the AI features sit on top of the same ingestion pipeline that the reading experience depends on. A bug in the read-state machinery is, for those users, a bug in the intelligence pipeline.
Feedly shipped the fix on August 14. The status page, updated three days later, still lists no August incidents. Whether the company retroactively updates that record is a matter of its own incident-management policy.
