WAVE #1 ? June 11th
6:25am PST ? We?re making some changes to our infrastructure that will allow us to bring feedly back online. However, these things take some time to put into place and it may still be a few more hours before service is restored. Thank you so much for your patience and for sticking with us. Remember, none of your data was compromised or lost in this attack.
15:07pm PST - We have neutralized DDoS attack that began at 2:04am PST last night. You should now be able to access your feedly from both feedly.com, mobile apps and third party applications. Our ops team is closely monitoring the situation in case the attacks resume. It might take a few hours for 40 million feeds we poll to get fully updated. We would like to re-iterate that none of your data was compromised by this attack. I would like to thank the ops team for working through the night to resume the service as quickly as possible. I would also like to thank the community for your amazing support!
16:34pm PST - If you are not able to access feedly.com it is most likely due to the fact that your ISP or computer is caching an old DNS entry. Please refresh your DNS cache or wait for it to expire.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WAVE #2 ? June 12th
7:26am PST: We are currently being targeted by a second DDoS attack and are working with our service providers to mitigate the issue.
10:17am PST: The criminal has launched his second wave of DDoS attack this morning. The ops team has reviewed the attacks and is working on building a second line of defense to neutralize this second attack. To make breaching those defenses harder, we can not communicate as frequently as we would like on the status of our infrastructure changes. But this second wave should be neutralized faster than the first one. We apologize for the inconvenience. Thank you for your support and understanding as we work our way through these waves of attacks.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE : Nextgen Reader and other RSS readers using Feedly will not function during the down time.
6:25am PST ? We?re making some changes to our infrastructure that will allow us to bring feedly back online. However, these things take some time to put into place and it may still be a few more hours before service is restored. Thank you so much for your patience and for sticking with us. Remember, none of your data was compromised or lost in this attack.
15:07pm PST - We have neutralized DDoS attack that began at 2:04am PST last night. You should now be able to access your feedly from both feedly.com, mobile apps and third party applications. Our ops team is closely monitoring the situation in case the attacks resume. It might take a few hours for 40 million feeds we poll to get fully updated. We would like to re-iterate that none of your data was compromised by this attack. I would like to thank the ops team for working through the night to resume the service as quickly as possible. I would also like to thank the community for your amazing support!
16:34pm PST - If you are not able to access feedly.com it is most likely due to the fact that your ISP or computer is caching an old DNS entry. Please refresh your DNS cache or wait for it to expire.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WAVE #2 ? June 12th
7:26am PST: We are currently being targeted by a second DDoS attack and are working with our service providers to mitigate the issue.
10:17am PST: The criminal has launched his second wave of DDoS attack this morning. The ops team has reviewed the attacks and is working on building a second line of defense to neutralize this second attack. To make breaching those defenses harder, we can not communicate as frequently as we would like on the status of our infrastructure changes. But this second wave should be neutralized faster than the first one. We apologize for the inconvenience. Thank you for your support and understanding as we work our way through these waves of attacks.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE : Nextgen Reader and other RSS readers using Feedly will not function during the down time.
Last edited: