Skip to main content

Is Feedly Down?

No — Feedly is up
Feedly's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 109 ms

Right now

We could not read Feedly's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

feedly.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
109 ms
Checked

By region

  • Ashburn reachable, 54 ms
  • Chicago reachable, 87 ms
  • Johannesburg reachable, 204 ms
  • London reachable, 65 ms
  • Los Angeles reachable, 125 ms
  • San Jose reachable, 90 ms
  • Singapore reachable, 134 ms
  • Tokyo reachable, 115 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn13 ms1 ms11 ms51 ms
Chicago51 ms2 ms6 ms85 ms
Johannesburg179 ms1 ms7 ms203 ms
London24 ms2 ms11 ms59 ms
Los Angeles94 ms2 ms7 ms122 ms
San Jose25 ms11 ms14 ms77 ms
Singapore76 ms1 ms12 ms132 ms
Tokyo75 ms1 ms5 ms112 ms
We check that feedly.com loads, not every feature behind it. Test it yourself

History

Feedly website availability

Measured by FlareWarden · feedly.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
128ms

Last 30 days

79-day clean streak
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 29 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 31 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 31 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 16 checks
Sep 24 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of feedly.com from multiple regions every 6 hours. Feedly's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 79 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Feedly does

Feedly is a reader that collects articles from RSS feeds, newsletters and websites into one place, organised into folders and saved boards. Researchers, analysts, marketers and security teams use it as a monitoring surface rather than as casual reading, which is why an outage removes a working input for the day rather than an entertainment source.

What an outage looks like

The web and mobile apps load but show no new articles, or the feed list renders empty. Refreshes return errors, saved boards fail to open, and articles marked read reappear unread after a sync. Because Feedly polls its sources on a schedule rather than receiving pushes, an incident often surfaces as a gap in the timeline that only becomes obvious once the service recovers.

What to do about it

Check status.feedly.com, which monitors feedly.com as a single system on a Better Stack page with a seven-day incident history, so it confirms an incident without breaking it down by feature. Sources keep publishing their own feeds while Feedly is unavailable, so a short gap usually fills in when polling resumes. A long one may not, because most feeds only expose their most recent items.

Is it down for everyone, or just you?

If this page says Feedly is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

R
Reddit
W
WordPress
Hootsuite
Hootsuite
Buffer
Buffer

Feedly outage FAQ

Is Feedly down, or is one feed broken?
Check whether everything is quiet or only one source. A single silent feed is usually the publisher's problem: the site moved its feed address, or the feed itself is returning errors. If nothing across all your sources has updated for hours and refreshes error out, that points at Feedly, and status.feedly.com carries a seven-day incident history that will confirm it.
Will I miss articles published during an outage?
Possibly, depending how long it runs. Feedly reads each source's feed on a schedule and most feeds list only their most recent items, so a short incident fills in when polling resumes while a long one can leave a permanent gap. If a particular source matters for the window, check its own site rather than assuming the timeline is complete.
Do the mobile apps work when the website is down?
Not for new content, since both read from the same service. Articles already downloaded to the device stay readable offline, which makes the app look healthier than the platform actually is. Read states set while offline sync when the service returns; if they do not, that is worth raising rather than re-marking hundreds of articles by hand.
Do my sources and boards survive an outage?
Yes. Feeds, folders and boards are stored on the server, and an availability incident stops them being served rather than deleting them, so everything reappears when the service does. If sources are genuinely missing after recovery rather than briefly unavailable, that is an account problem rather than an outage and worth raising with support directly.
Why does the same article keep coming back unread?
That is a sync failure rather than something you did. Read state is held on Feedly's side and pushed from whichever client you used, so when the service is degraded a client can mark an article locally and fail to persist it, letting another device pull the old state back. It settles on its own once the service recovers.

How we measure this

  • We request Feedly's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Feedly publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Feedly itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Feedly goes down

We check Feedly every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required