DynStatus

dynect

Router Maintenance in London

Tue, 31 Aug 2010 1557 UTC

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.

dynect

Dynect Monitoring Maintenance

Mon, 30 Aug 2010 2041 UTC

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.

dynect

Bandwidth Provider Maintenance in Ashburn, VA

Mon, 30 Aug 2010 1522 UTC

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.

dynect

DDoS in AMS, HKG, and PAO

Sun, 29 Aug 2010 0827 UTC

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.

dynect

Anycast Routing Maintenance

Thu, 26 Aug 2010 1455 UTC

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.

dynect

Phone System Maintenance

Thu, 26 Aug 2010 1428 UTC

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.

dynect

Server Outage in Amsterdam/SPL

Thu, 26 Aug 2010 0917 UTC

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.

dynect

Bandwidth Provider Maintenance in Amsterdam

Fri, 20 Aug 2010 1459 UTC

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.

dynect

On-going Statistics server maintenance

Mon, 16 Aug 2010 1826 UTC

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.

dynect

Router Maintenance in Palo Alto

Thu, 12 Aug 2010 0154 UTC

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.

dynect

Emergency Provider Maintenance in Singapore

Tue, 10 Aug 2010 1709 UTC

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.

dynect

Dynect monitoring disruption

Wed, 21 Jul 2010 1156 UTC

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.

dynect

Power Outage in our Frankfurt Datacenter

Fri, 16 Jul 2010 1317 UTC

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

Dynect Monitoring Disruption

Wed, 14 Jul 2010 1219 UTC

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.

dynect

Bandwidth Provider Maintenance in Frankfurt, Germany

Wed, 07 Jul 2010 1712 UTC

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.

dynect

Bandwidth Provider Maintenance in Ashburn, VA

Wed, 07 Jul 2010 1657 UTC

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.