Product1 distinct publisher3 min readUpdated
The largest standalone RSS reader ran unusably slow for over a week while its homepage sold AI threat intelligence. Its CEO blames Mark as Read, and heard about a broken iOS app from a reporter.
The Product Desk · Product desk

Compiled by The Product DeskSomething wrong?How this is made
Feedly, which claims 15 million users and inherited much of the audience Google left behind when it closed Google Reader in 2013, spent more than a week with a web app that paying subscribers described as unusably slow [1][3]. Chief executive Edwin Khodabakchian told TechCrunch the cause was a bug, specifically the "Mark as Read" action on accounts with a lot of folders, and that a fix shipped Friday, with the team still confirming whether it resolved the problem for everyone [10].
Taken alone, that is an ordinary regression. What makes it worth an operator's attention is the shape of everything around it. Users on Reddit reported the app running extremely slowly to the point of being unusable [5]. Separately, the iOS app, including on the iOS 27 beta, was not loading at all [6]. Separately again, the classic version of Feedly's mobile app was shut down with no warning to the people still using it [7]. Khodabakchian said Classic was retired two weeks ago because it no longer met some iOS and Android requirements, that it had a few hundred active users, and that the team did not notify them before the final shutdown [11]. A few hundred out of 15 million is roughly 0.002 percent of the advertised base [15], which is exactly the size of cohort that gets dropped quietly when nobody owns the communication step.
The most telling detail is not the slowdown. Multiple customers on Reddit said their support requests had been ignored, which is why TechCrunch contacted the company [2][13]. Asked about the broken iOS app, Khodabakchian said he was not aware of the issue, promised to investigate and fix it quickly, and said Feedly still actively invests in its main iOS and Android apps [12]. A chief executive learning about a non-loading mobile client from a reporter is a reporting-path failure, not a front-end one. The bug explanation may well be correct and still not explain a week.
The context the company disputes is the pivot. Feedly has been moving toward AI, selling businesses a way to track emerging threats and receive tailored intelligence, and that is the product on its homepage now [8]. Khodabakchian's position is that core RSS still matters precisely because of the new business: "Despite the pivot to cyber threat intelligence, fixing the basic RSS functionality is still a priority because our CTI community uses the news-reading capability," he said, adding that the goal is to keep the news reader fast and streamlined [9]. That is a defensible strategy on paper. It also means the reader is now maintained as a dependency of the enterprise product rather than as the product, and dependencies get the attention their consumers demand, not the attention their users deserve.
The market gives Feedly room to absorb this. RSS readers have always been a relatively small category, with most consumers following news through dedicated apps such as Apple News, through Google News and the open web, and through social posts [14], and Feedly is larger than Inoreader, NetNewsWire and Reeder [4]. Room to absorb a bad week is not the same as room to absorb a reputation for silence.
Three things to watch. Whether Friday's fix holds for all accounts, which the company itself had not confirmed [10]. Whether the iOS loading failure gets fixed on the timeline promised [12]. And whether the next sunset of a small legacy cohort comes with notice, since the last one did not [11].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Feedly, the largest standalone RSS reader worldwide, experienced technical issues for over a week, with paying users upset that the web app had been "unusably slow."
Some Feedly users reported that the company ignored their support requests.
Feedly, heir to the market Google ceded when it closed Google Reader in 2013, is among the most successful RSS newsreaders globally with 15 million users, according to its website.
Feedly is larger than competitive products including the web-based Inoreader and desktop apps such as NetNewsWire and Reeder.
Users on Reddit reported the Feedly app running "extremely" slow, making it "unusable."
The classic version of Feedly's mobile app, preferred by a small subset of customers, was shut down without warning weeks ago.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single-outlet reporting with on-record vendor confirmation
One publisher, one article, but the load-bearing facts are confirmed on the record by Feedly's CEO: the web app bug, the Friday fix, the Classic retirement without user notification, and unawareness of the iOS failure. The user-side evidence is crowd-sourced Reddit reports that the article does not quantify or independently reproduce, and no telemetry, status page, or second publisher corroborates the outage window.
Large self-reported base, thin verified usage detail
The only usage figures are vendor-supplied: 15 million users on Feedly's website and a few hundred active Feedly Classic users per the CEO. Those establish that a large installed base exists and that the retired legacy client was negligible within it, but there is no paid-subscriber count, no measure of how many users the slowdown touched, and no independent data on the enterprise CTI product's uptake beyond its placement on the homepage.
Vendor reassurance runs ahead of what the same article shows
The company's framing - RSS is still a priority, the goal is a fast and streamlined reader, one bug explains the slowdown - is overstated relative to the evidence in the same piece: paying users went a week without usable service, support tickets were unanswered, a legacy client was killed without notice, the CEO had not heard about a non-loading iOS app until a reporter asked, and the Friday fix is unconfirmed. The gap is moderate rather than severe because the vendor does concede specifics and did ship a fix.
Vendor speaking to protect a pivot narrative
The primary voice is the CEO of the company under criticism, responding to a reporter's inquiry while the firm's homepage sells an AI cyber threat intelligence product to businesses. He has a direct interest in framing a week of degradation as an isolated bug and in reassuring the RSS base that the pivot has not abandoned them - visible in the argument that RSS matters because the CTI community uses it. The publisher's incentive is a timely consumer-tech accountability story; the user-side voices are anonymous Reddit posters with no disclosed stake.
Facts as reported are solid; scope and resolution are not
Confidence is moderate: the discrete, on-record items are reliable, and the story is fresh. But everything about magnitude is unsettled - how many of the 15 million users were affected, whether the Friday fix worked, whether the iOS failure was addressed - and a single publisher with no follow-up leaves no way to test the vendor's account.
invest
Tiny corp wants Etched's numbers. Jane Street led $700M at $21B without publishing any1 distinct publisher
build
Vivodyne is spending venture money on wet-lab throughput, not bigger models2 distinct publishers
build
California's heavy-truck permits start a mileage clock, not a driverless freight service1 distinct publisher
product
Sonic Fire Tech raised $15M to outrun a three-year code clock1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 17, 2026