Skip to main content

Is Feedly Down?

No — Feedly is up

Reachable from all 8 checked regions

Average response time: 57ms

Last checked · checks run every 6 hours

Official status page: https://status.feedly.com

Feedly uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 18 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

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

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
49ms
DNS 0ms TCP 2ms TLS 12ms TTFB 45ms
iad
49ms
DNS 0ms TCP 2ms TLS 7ms TTFB 46ms
jnb
24ms
DNS 0ms TCP 0ms TLS 6ms TTFB 22ms
lax
41ms
DNS 0ms TCP 1ms TLS 9ms TTFB 39ms
lhr
36ms
DNS 0ms TCP 2ms TLS 9ms TTFB 33ms
nrt
40ms
DNS 0ms TCP 1ms TLS 10ms TTFB 37ms
ord
39ms
DNS 0ms TCP 2ms TLS 8ms TTFB 34ms
sin
179ms
DNS 0ms TCP 37ms TLS 43ms TTFB 137ms

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 all 18 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 — 8 of them answered the most recent check.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Feedly goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required