DNS Turbulence – FIXED

A few people have reported on twitter, friendfeed and getsatisfactions issues regarding accessing feedly. We are looking into the problem and trying to track down the root cause of what seems to be a DNS issue. Sorry for the inconvenience. We will update this post as soon as the problem is resolved.

Update: July 31st, 12:40 am. This problem seems to only impact a small percentage of the users so we are still not sure if it is caused by an issue by our name registrar or if it is a replication problem. We are working on changing our name registrar. We are going to look at this problem again tomorrow morning. Sorry for the inconvenience and thank you for your patience.

Update: July 31st: 10:10 am. We decided to transfer our registrar and DNS server to your main registrar (the one we currently had to use because we bought the domain from seems to have some broken parts). The turbulence might therefore continue until the domain transfer is complete (they mentioned 1 to 7 days). People have reported 2 work arounds so far: 1) if you use OpenDNS you can temporary switch back to the DNS of your internet provider, 2) if you are technically savy you can manually change you host file with http://www.feedly.com

Update: July 31st: 11:21 am. Transfer completed. DNS server changed. The change should replicate in the next hour or and everything should be back to normal. Special thanks to DNS expert (@davidu) for reaching out!

Update: July 31st: 12:04pm. the new DNS server information have replicated across. OpenDNS is now resolving feedly.com correctly. We should be back into clear skies. Sorry again for the inconvenience and thank you for your patience!

Note: It is important to note that this did not have anything to do with Open DNS. See comment from David.

Author: @feedly

Read more. Know more.

2 thoughts on “DNS Turbulence – FIXED”

  1. It’d be nice to point out that this issue had nothing to do with OpenDNS… Our caches just happen to pick up the failure faster than others. It was just a matter of time before all other DNS servers would lose their NS glue and start timing out requests for feedly.com, too.

Comments are closed.