Dyn Status Updates. Delivered.

Identified - On October 31, 2016 beginning at 06:00 UTC, one of our upstream transit providers will be performing maintenance on their infrastructure in London, UK. No impact to Dyn Managed DNS Nameserver or peripheral infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths.

Customers with questions or concerns are encouraged to reach out to our Technical Support Team.
Oct 31, 06:00 UTC

Identified - On February 16th, 2016, Dyn was made aware of CVE-2015-7547, a glibc getaddrinfo stack-based buffer overflow vulnerability affecting certain systems. Our security team is currently reviewing systems that may be impacted by this exploit and are systematically addressing these systems as required. You may find more information in the following Google blog entry here: https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html

We do not recommend that customers make any changes in their configuration in response to this issue.
Feb 16, 16:00 UTC

Identified - This Preliminary Findings Report is to provide additional detail in connection with an incident that began on October 21, 2016 at approximately 11:10 UTC and lasted until approximately 17:45 UTC

Dyn is dedicated to delivering the highest quality of service, and as such, we take any customer impacting events very seriously. Below you will find a preliminary analysis of the event. A more in-depth analysis will be distributed in the form of a Root Cause Analysis report at a later date.

Service Affected: Managed DNS

Event cause:
On Friday October 21, 2016 at approximately 11:10 UTC, Dyn came under attack by a large Distributed Denial of Service (DDoS) attack against our Managed DNS infrastructure in the US-East region. Customers affected may have seen regional resolution failures in US-East and intermittent spikes in latency globally. Dyn’s engineers were able to successfully mitigate the attack at approximately 13:20 UTC, and shortly after, the attack subsided. See original status post here: https://www.dynstatus.com/incidents/nlr4yrr162t8.
At roughly 15:50 UTC a second DDoS attack began against the Managed DNS platform. This attack was distributed in a more global fashion. Affected customers may have seen intermittent resolution issues as well as increased global latency. At approximately 17:00 UTC, our engineers were again able to mitigate the attack and service was restored.

At Dyn, we take every incident seriously and work hard to ensure we deliver the service our customers have come to expect. We will continue to evaluate every situation with the goal of improving our systems and processes to deliver the utmost customer experience. Thank you for your continued support.
Oct 21, 22:11 UTC

Identified - The issue has been identified and a fix is being implemented.
Oct 25, 02:05 UTC

Identified - Between 06:43 UTC and 07:30 UTC our engineers worked to mitigate a DDoS against our infrastructure in Palo Alto, California. In addition to issues logging into the Managed DNS and Email Delivery Portals, customers may have experienced intermittent issues using the Managed DNS API, increased DNS query latency and delayed zone propagation during this time.

Our engineers are currently investigating issues with Managed DNS monitoring services as a result of this incident.

Updates will be posted as they are available.
Oct 26, 08:02 UTC