OBSERVABILITY Signal 403
Feedly pins weeklong web slowdown on Mark as Read bug, rolls out Friday fix
↗
Feedly CEO Edwin Khodabakchian told TechCrunch the web app's weeklong performance issues came from a bug in the Mark as Read feature on accounts with many folders, and a fix shipped Friday though the company was still verifying the rollout.
For users running Feedly as a daily triage tool, a week of degraded performance on a paid tier is a concrete reliability event, not a marketing story. The fact that the trigger was a specific interaction (Mark as Read) on folder-heavy accounts suggests the failure scales with usage rather than being a uniform platform regression, which is useful for anyone modeling the blast radius of similar bugs. Only one feed carried the story, so the CEO's framing is the only version on the wire; the underlying iOS app breakage and the unannounced Feedly Classic shutdown are still separate, unconfirmed-by-second-source claims.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Feedly CEO Edwin Khodabakakchian attributed the web app's weeklong slowdown to a bug in the Mark as Read feature affecting accounts with many folders, and said a fix was released Friday with verification still in progress.
Separate from the web slowdown, users on Reddit reported the iOS app failing to load, including on iOS 27 beta, and the CEO said he was not aware of the issue but pledged to investigate.
Feedly Classic was retired two weeks before the report with no notice to existing users, though the CEO said the app had only a few hundred active users at the time of shutdown.
THE READ
What the cluster adds up to.
The technical cause Feedly named is narrow: a bug in the Mark as Read interaction on accounts with a large folder count, with a fix shipped Friday and verification still open. That specificity is more useful to engineers than the CEO's broader reassurance that RSS remains a priority, because it implies the regression scales with a known workload shape (many folders, frequent marking) rather than being a uniform platform slowdown. The fix being in the front end, per the CEO, also narrows the suspected surface area, though no commit, version, or reproduction steps were published in the report. The reliability story is not actually about the bug. Paying users reported the web app running 'extremely' slow and 'unusable' for over a week, and multiple customers said their support requests were ignored, according to the same single feed. That combination, a week of degraded core functionality on a paid tier with no visible status communication, is the operational concern, and the bug attribution does not address the gap between the product's actual state and what subscribers were told. A single source is reporting both the complaints and the company's denial that support was unresponsive
For an engineer or operator evaluating Feedly as a feed-triage dependency, the takeaway is about visibility, not the bug itself. There is no mention in the coverage of a public status page, a postmortem, or a changelog entry for the Friday fix, which is the standard the product would be held to if it were a piece of internal infrastructure. The fact that the company attributed a weeklong regression to a single interaction suggests either a small user impact zone, in which case the communication gap is the real failure, or a larger impact zone that was underestimated because users had no channel to escalate beyond Reddit and support tickets that were not answered.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER