Feedly Outage History
3 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Feedly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 11, 2026 | Some users are experiencing slowness | 1311h 15m | Resolved |
| Aug 17, 2026 | Some users are experiencing slowness | 1806h 3m | Resolved |
| Jun 19, 2026 | Some services are down | 1762h 29m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Feedly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Feedly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Feedly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Feedly outage in this window ran 75d 6h, against a mean recovery of 67d 18h. If you depend on Feedly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.