DynStatus

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.

dynect

Anycast Routing Adjustments affecting ns2.pXX.dynect.net

Fri, 02 Jul 2010 2000 UTC

On Thursday, July 8, between 1800 and 2000 UTC, we will perform anycast routing maintenance against our ns2.pXX.dynect.net DNS nodes to turn up new capacity in Dallas, TX and Singapore. During this window, Dyn Inc. operations staff will be activating new anycast routes, adjusting BGP preferences for traffic distribution, and monitoring general network health.

Update (1920 UTC) : We have successfully turned up routing for ns2.pXX.dynect.net in Singapore and Dallas TX.

dynect

Singapore Datacenter Turn Up

Fri, 02 Jul 2010 1945 UTC

On Tuesday, July 6, between 1800 and 2000 UTC, we will perform anycast routing maintenance against our ns4.pXX.dynect.net DNS nodes to turn up our new Singapore datacenter. During this window, Dyn Inc. operations staff will be activating new anycast routes into Singapore, adjusting BGP preferences for traffic distribution, and monitoring general network health.

Customers utilizing Traffic Management, Real-Time Traffic Management, or CDN Manager should note that the Singapore facility will be included in our Asia-Pacific region definitions.

Update (1935 UTC) : We have successfully turned up routing for ns4.pXX.dynect.net in Singapore.

dynect

Dallas, Texas Datacenter Turn Up

Wed, 30 Jun 2010 1224 UTC

On Friday, July 2, between 1800 and 2000 UTC, we will perform anycast routing maintenance against our ns4.pXX.dynect.net DNS nodes to turn up our new Dallas, Texas datacenter. During this window, Dyn Inc. operations staff will be activating new anycast routes into Dallas, adjusting BGP preferences for traffic distribution, and monitoring general network health.

Customers utilizing Traffic Management, Real-Time Traffic Management, or CDN Manager should note that the Dallas, TX facility will be included in our US Central region definitions.

Update (1920 UTC) : We have successfully turned up routing for ns4.pXX.dynect.net in Dallas.

dynect

Newark, NJ Site Removed from Anycast

Mon, 28 Jun 2010 0507 UTC

As of 04:30 UTC, we have removed our Newark, NJ site from our anycast routing due to a large DDoS attack. Routes to ns1.pXX.dynect.net and ns3.pXX.dynect.net have been adjusted so that traffic is routed to the next available datacenter. No impact to services has been observed at this time.

Update: As of 1600 UTC, the Newark, NJ site has been inserted back into our anycast system.

dynect

Dynect monitoring disruption

Sun, 27 Jun 2010 1930 UTC

Beginning at approximately 1654 UTC, a traffic spike at two Dynect Platform datacenters caused degraded performance for monitoring result processing. Routes from our monitoring agents to some destinations were unreachable. This may have caused notifications to be sent related to a change in host status. The situation lasted approximately 40 minutes before subsiding. All services have returned to nominal status.

dynect

Dynect monitoring disruption

Thu, 24 Jun 2010 1527 UTC

Beginning at approximately 1449 UTC, a traffic spike at two Dynect Platform datacenters caused degraded performance for monitoring result processing. Routes from our monitoring agents to some destinations were unreachable. This may have caused notifications to be sent related to a change in host status. The situation lasted approximately 15 minutes before subsiding. All services have returned to nominal status.

dynect

Bandwidth Provider Maintenance in Chicago, IL

Mon, 21 Jun 2010 1517 UTC

On 30 June 2010, between 0500-0600 UTC, one of our upstream transit providers will perform maintenance on their infrastructure in Chicago, IL. 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

Site Maintenance in Amsterdam

Tue, 08 Jun 2010 1804 UTC

On June 10 between 1800 UTC and 1900 we will be performing upgrades for Dynect system operations in our Amsterdam datacenter. During this time, users may experience additional DNS query latency as traffic is routed to other regional sites in our anycast network. We do not recommend that customers make any configuration changes in preparation for this maintenance.