3 Companies Hit By DDoS AttacksIncidents Caused Significant Website Downtime
Three companies - Deezer, Evernote and Feedly - have been hit by distributed-denial-of-service attacks in recent days, resulting in significant site downtime for each of the organizations. It's unclear if the attacks were related.
Deezer, an online music streaming service, says it was impacted by a large-scale DDoS attack on June 7 via a botnet, which resulted in the company's website being down for several hours.
"Be assured your personal information was, and will remain, completely secure," Daniel Marhely, the company's founder, says in a blog post. "The DDoS attack did not target any user information and only affected availability of the service."
Deezer continued to face further DDoS attempts later in the day on June 7 and again on June 8. "We're continuing to investigate and are working hard on countering this type of attack in the future, by strengthening our security systems and servers," Marhely says. As of 12 p.m. ET June 11, the site was functioning normally.
News aggregator Feedly on June 11 said cybercriminals were attacking the site with a DDoS attack, using the incident as an attempt to extort money from the organization. "We refused to give in and are working without network providers to mitigate the attack as best as we can," the company says in a blog post. "We are working in parallel with other victims of the same group and with law enforcement."
As a result of the incident, Feedly is changing its infrastructure to ensure the site stays online. "However, these things take some time to put into place and it may still be a few more hours before service is restored," the company says. As of 12:40 p.m. ET June 11, the site was accessible.
Evernote, an online note-taking service, reported on its Twitter account June 10 that it was working to neutralize a DDoS attack. Later in the day, the company said the website was running again, but warned that users may experience "a hiccup or two" over the next 24 hours. As of 12 p.m. ET June 11, the website was working properly.