DynStatus

Expired SSL Certificate on DynDNS.com

Our SSL certificate on DynDNS.com is currently expired and we will be replacing the certificate in the next few hours. You can safely log in to make changes to your account or complete any purchases by either confirming a security exception. To verify that you have the correct certificate, the current certificate expired at 9:42pm EDT.

Update: As of 1350 UTC, a new certificate is in place. We apology for any inconvenience this may have caused.

Router Maintenance in London

On 2 September 2010, between 2100-2200 UTC, we will be performing maintenance on our router in London. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Continued Deployment of AAAA Glue Records / IPv6

On September 2 2010, Dyn Inc operations staff will add IPv6 AAAA glue records to the ns3.dyndns.org, ns4.dyndns.org, and ns2.mydyndns.org nameserver delegations. This will enable IPv6 DNS services for our Dynamic DNS, Custom DNS, and Secondary DNS user base. We expect this operation to be completely transparent to operations, and will provide an update when this work is completed.

Dynect Monitoring Maintenance

On Thursday September 2nd, between 1200 UTC and 2000 UTC we will be working on the Dynect Monitoring infrastructure. We will be working on one monitoring site at a time.

Monitoring services will be reconfigured prior to the maintenance and redistributed to the other sites. Customers should see no impact to their monitoring services, although our tests will be coming from different agents throughout the maintenance cycle.

We do not recommend that customers make any configuration changes in preparation for this maintenance.

Update (1930 UTC): We successfully completed the maintenance on the Dynect Monitoring infrastructure. Thanks for your patience.

Bandwidth Provider Maintenance in Ashburn, VA

On 9 September 2010, between 0300-0700 UTC, one of our upstream transit providers will perform maintenance on their infrastructure in Ashburn, VA. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

DDoS against MyDynDNS

Beginning at 0839 UTC, we are experiencing a DDOS against the MyDynDNS nameservers. Customers may be seeing decreased performance on ns3.mydyndns.org, ns4.mydyndns.org, and ns5.mydyndns.org during the attack.

Update: Mitigation is in place to return ns3.mydyndns.org, ns4.mydyndns.org, and ns5.mydyndns.org to normal operation. Due to mitigation steps, users may experience additional latency to these nameservers.

Update: Services were operating again and 100% by 1600 UTC and have remained stable since then.

DDoS in AMS, HKG, and PAO

Beginning at 0839 UTC, we are currently experiencing a DDOS against our Amsterdam, Hong Kong, and Palo Alto datacenters. Customers may be seeing decreased performance on these nameservers during the attack. This may have caused notifications to be sent related to a change in host status. Our monitoring service continues to reconfigure monitoring services between the agents which are available.

UPDATE: As of 1037 UTC, these sites are fully operational again.

Anycast Routing Maintenance

On 30 August 2010, between 1300-2100 UTC, we will be making some changes to the routing behavior of our ns2 anycast nameserver pool in the Asia region to improve localization in that region. This is a precautionary window, no downtime is expected with this activity. We do not recommend that customers make any configuration changes in preparation for this maintenance.

On 31 August 2010, between 1300-2100 UTC, we will be making the same changes to our ns4 anycast nameserver pool.

Update: The ns2 and ns4 anycast nameserver pool maintenance has been completed, and the alterations have improved localization of traffic in the Asia/Pacific region.

Phone System Maintenance

On 26 August 2010, between 2300 and 2330 UTC, we will be performing maintenance on the phone system. During this period, the main number +1 603 668 4998, all fax numbers, and the customer support and Premiere Support numbers will not be reachable. Dynect concierge services will not be available during this period as well.

Phone System Maintenance

On 26 August 2010, between 2300 and 2330 UTC, we will be performing maintenance on the phone system. During this period, the main number +1 603 668 4998, all fax numbers, and the customer support and Premiere Support numbers will not be reachable. Dynect concierge services will not be available during this period as well.

Server Outage in Amsterdam/SPL

On 26 August 2010, around 0858 UTC, some our Anycast servers in Amsterdam began to experience an outage.

DNS queries routed to our SPL datacenter may experience degraded performance as they are re-routed to the nearest anycast datacenter in the region.

Dynect monitoring services from this datacenter have been interrupted while systems and services are being restored. The monitoring from this site was redistributed to other monitoring sites. During this reconfiguration of monitoring services, customers may have received notifications regarding service or host changes.

EDIT: Previous announcement said Seoul, South Korea, but this was really in Amsterdam.

UPDATE: As of 0952 UTC, a power failure in the datacenter has been established as the cause. Technicians are working to bring the site back up as soon as possible.

UPDATE: As of 1800 UTC, Internet Guide and Dynect Monitoring services in SPL are back online. DynTLD and Dynect name services are still pending repair.

UPDATE: As of 21:38 UTC, all services in the SPL datacenter have returned to full functionality.

Router Maintenance in Amsterdam

On 26 August 2010, between 2100-2200 UTC, we will be performing maintenance on our router in Amsterdam. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Bandwidth Provider Maintenance in Amsterdam

On 3 September 2010, between 0100-0200 UTC, one of our upstream transit providers will perform maintenance on their infrastructure in Amsterdam. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Deployment of AAAA Glue Records / IPv6 to ns2.dyndns.org

On Monday, August 23rd 2010, Dyn Inc operations staff will add IPv6 AAAA glue records to the ns2.dyndns.org nameserver delegation. This will enable IPv6 DNS services for our Free Dynamic DNS user base. We expect this operation to be completely transparent to operations, and will provide an update when this work is completed.

Update: We have added a AAAA record to ns2.dyndns.org and are seeing IPv6 DNS traffic at this time. We are going to keep an eye on it and add the AAAA glue records once we decide it’s stable.

Update 2: ns2.dyndns.org now has AAAA glue at the .org nameservers.

Offline DDoS Attack

As of 1410 UTC, offline.mydyndns.org is the target of a distributed denial of service (DDoS) attack. This may have caused issues with DNS, MailHop, WebHop, Web, checkip.dyndns.org, and NIC update services. The Operations team is investigating this attack and in the meantime has temporarily disabled offline.mydyndns.org.

Update: The attack has ended and offline.mydyndns.org is functioning normally.

DDoS against ns1.mydyndns.org

Beginning at approximately 1642 UTC, we began taking a DDoS against the ns1.mydyndns.org nameserver in our Newark, NJ datacenter. Customers may have seen decreased performance on that nameserver during the attack. By 1717 UTC the attack had been mitigated.

On-going Statistics server maintenance

Beginning 2010-08-16, we will be performing periodic data storage maintenance on the servers providing statistical reporting for the Dynect Platform. Users may periodically find that the graphs reporting QPS are unavailable for short periods at a time.

We apologize for any inconvenience, as we work to improve the reports and information available to you for your account.

DDoS Against WebHop

We are currently experiencing a distributed denial of service attack against our WebHop redirection service. All other services are operating normally, but the WebHop service is temporarily unavailable.

Update: The attack has ended and WebHop is functioning normally.

Router Maintenance in Palo Alto

On 13 August 2010, between 2100-2200 UTC, we will be performing maintenance on our router in Palo Alto. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Emergency Provider Maintenance in Singapore

On 10 August 2010, between 0500-0600 UTC, our upstream transit providers will perform maintenance on their infrastructure in Singapore. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in response to this maintenance.

DDOS against mydyndns

We are currently experiencing a DDOS against the ns1.mydyndns.org and ns2.mydyndns.org nameservers. Customers may be seeing decreased performance on these nameservers during the attack.

Update: As of 0505 UTC, MYDYNDNS services are stable. All system are normal at this time.

Hardware failure in London Datacenter

Starting at approx 0800 UTC we had a hardware malfunction in our London Data center. Internet Guide customers may have seen degraded performance in DNS resolution from Europe. Other sites in the area are handling the London traffic.

DDOS against mydyndns

Beginning at approximately 1040 UTC, we began taking a DDOS against the ns1.mydyndns.org nameserver in our Newark, NJ datacenter. Customers may be seeing decreased performance on that nameserver during the attack.

Update: As of 1205 UTC, MYDYNDNS services are stable. Our operations team is working with our providers to isolate the sources of the attack. All system are normal at this time.

Dynect monitoring disruption

Beginning at approximately 1040 UTC, traffic spikes at our Newark, NJ site are causing some monitoring degradation. This may have caused notifications to be sent related to a change in host status. Our monitoring service continues to reconfigure monitoring services between the agents which are available.

Update: As of 1200 UTC all Dynect monitoring services have stabilized.

Emergency Maintenance on the DYNDNS.ORG Infrastructure

During the course of the day, we will be working on the DYNDNS.ORG infrastructure.
Customers may experience delays as services will go in and leave maintenance.

We appreciate your understanding.

Update (1615 UTC): We successfully completed the maintenance on the DYNDNS.ORG infrastructure. All services are stable.
Thanks for your patience.

Emergency Maintenance on the MYDYNDNS Infrastructure

During the course of the day, we will be working on the MYDYNDNS infrastructure.
Customers may experience delays as services will go and leave maintenance.

We appreciate your understanding.

Update (1900 UTC): We successfully completed the maintenance on the MYDYNDNS infrastructure. All services are stable.
Thanks for your patience.

Attack on nsX.mydyndns.org DNS Servers

We currently fighting a complex attack against the nsX.mydyndns.org nameservers. More updates to follow.
Update: As of Sun Jul 18 1330 UTC, MYDYNDNS services are stable. Our operations team is working with our providers to isolate the sources of the attack. All system are normal at this time.

Power Outage in our Frankfurt Datacenter

Beginning at approximately 10:59 UTC there was a power failure in our Frankfurt datacenter that affected our redundant power supplies causing our services in this site to be unavailable for periods of 10 to 55 minutes.

DNS queries destined for our FRA nameservers may have experienced degraded performance as they were re-routed to the nearest anycast datacenter in the region.

Dynect monitoring services from this datacenter were interrupted for approximate 55 minutes during this outage and while systems and services were restored following power recovery. The monitoring from this site was redistributed to other monitoring sites. During this reconfiguration of monitoring services, customers may have received notifications regarding service or host changes.

Dynect Monitoring Disruption

Beginning at approximately 1130 UTC traffic spikes on the Dyn Inc network are causing some monitoring degradation at various sites. This may have caused notifications to be sent related to a change in host status. Our monitoring service continues to reconfigure monitoring services between the agents which are available.

Update: As of 1225 UTC all Dynect monitoring services have stabilized.

DDOS against mydyndns

Beginning at approximately 1130 UTC we began taking a DDOS against the mydyndns nameservers in all of our datacenters.

Our operations team is working to mitigate this attack. Customers may see decreased performance on various nameservers while we work to address this elevated traffic.

Update: As of 1400 UTC, MYDYNDNS services are stable. Our operations team is working with our providers to isolate the sources of the attack. All system are normal at this time.

Bandwidth Provider Maintenance in Frankfurt, Germany

On 21 July 2010, between 0400-0500 UTC, one of our upstream transit providers will perform maintenance on their infrastructure in Frankfurt, Germany. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Update: This maintenance has been rescheduled to 23 July 2010 between 0400-0500 UTC.

Bandwidth Provider Maintenance in Ashburn, VA

On 20 July 2010, between 0900-1000 UTC, one of our upstream transit providers will perform maintenance on their infrastructure in Ashburn, VA. No impact to Dynect Nameserver or Peripheral Infrastructure is expected, although some users may experience additional DNS query latency as traffic is routed to other paths. We do not recommend that customers make any configuration changes in preparation for this maintenance.

Update: This maintenance has been rescheduled to 23 July 2010 between 0900-1000 UTC.