DynStatus

dynect

Bandwidth Provider Maintenance in Palo Alto, CA

Tue, 17 Nov 2009 1625 UTC

On November 25, between 0800-0845 UTC, one of our bandwidth providers will be performing maintenance on their router in our Palo Alto, CA data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers, changes to your US West site definitions are not necessary as this traffic will be routed to other anycast sites.

Dynect DNS and monitoring services at this site will continue to function.

dynect

Bandwidth Provider Maintenance in Newark, NJ

Mon, 16 Nov 2009 2115 UTC

On November 22, between 0400-1200 UTC, our bandwidth providers will be performing maintenance on our connections in our Newark, NJ data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers with US East regional definitions a small percentage of responses may return your global pool. We do not recommend any changes to your GSLB regional settings.

dynect

Bandwidth Provider Maintenance in Palo Alto, CA

Mon, 16 Nov 2009 1940 UTC

On November 19, between 0700-1500 UTC, our bandwidth providers will be performing maintenance on our connections in our Palo Alto, CA data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers with US West regional definitions a small percentage of responses may return your global pool. We do not recommend any changes to your GSLB regional settings.

dynect

Degraded Performance in Chicago

Thu, 05 Nov 2009 1921 UTC

Starting at approximately 1530 UTC today we experienced routing issues with one of our bandwidth providers in our Chicago datacenter. Our Operations staff took measures to work around the issue until it could be resolved. This had an impact on Dynect DNS services as some traffic was routed to datacenters in other regions.

By 1630 UTC, regular service was restored.

dynect

Degraded Performance in Hong Kong

Wed, 04 Nov 2009 1742 UTC

Due to a routing issue with an upstream provider, which began at approximately 1725 UTC, users may notice a degraded performance in DNS resolution and monitoring from our Hong Kong data center. We apologize for any inconvenience, our network operations group is communicating with this provider in order to resolve the issue.

Update: As of 1830 UTC, routing issues upstream have been resolved.

dynect

Bandwidth Provider Maintenance in Palo Alto, CA

Wed, 21 Oct 2009 1526 UTC

On October 30, between 0600-1400 UTC, our bandwidth providers will be performing maintenance on our connections in our Palo Alto, CA data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers with US West regional definitions a small percentage of responses may return your global pool. We do not recommend any changes to your GSLB regional settings.

dynect

Bandwidth Provider Maintenance in Newark, NJ

Fri, 09 Oct 2009 1849 UTC

On October 18, between 0300-1100 UTC, our bandwidth providers will be performing maintenance on our connections in our Newark, NJ data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers, changes to your US East site definitions are not necessary as this traffic will be routed to other anycast sites.

Dynect DNS and monitoring services at this site will continue to function.

dynect

Internet Routing Issues

Fri, 02 Oct 2009 2008 UTC

At approximately 1915 UTC today routing issues involving AS 701 (MCI Communications Services, Inc. d/b/a Verizon Business) resulted in some of our sites being unavailable to part of the Internet. The problem appeared to be localized to the northeastern United States. Due to the diversity of our connections to the Internet and hosting locations, we successfully routed around the outage.

As of approximately 1950 UTC, the issue appears to have been resolved, and connectivity restored.

dynect

Dynect Platform Monitoring Degradation

Sun, 27 Sep 2009 0959 UTC

As of 0900 UTC, we’ve been made aware of degradations of service with our Dynect Platform Monitoring service. Our teams are actively investigating the issue.

Update: During a DDOS, our monitoring agents were unable to properly report their results. This resulted in some monitoring services reporting incorrect results. After mitigation of the attack we were able to resynchronize the monitoring services.

As of 1015 UTC all monitoring services have returned to normal. We apologize for any false negatives that may have been reported during this time.

Update 2: During a DDOS, from approximately 0840 UTC to 0930 UTC DNS responses from 2 of our nameservers were impacted. Our other nameservers were not impacted at all, and responded flawlessly during this time.

All DNS responses are back to normal at this time.

dynect

Statistics Reporting Maintenance Window

Fri, 25 Sep 2009 1438 UTC

On Monday, Sept 28, 2009 from 1330 UTC to 1400 UTC we will performing the final stage of our Statistics and Reporting upgrades. During this maintenance window there will be a brief period of time that graph retrieval via the web interface will be unavailable.

We apologize for any inconvenience.

dynect

Bandwidth Provider Maintenance in Ashburn, VA

Thu, 24 Sep 2009 1912 UTC

On October 1, between 0700-1000 UTC, one of our bandwidth providers will be performing maintenance on their router in our Ashburn, VA data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers, changes to your Ashburn, VA site definitions are not necessary as this provider does not handle anycast traffic.

Dynect DNS and monitoring services at this site will continue to function.

dynect

Bandwidth Provider Maintenance in Palo Alto, CA

Tue, 22 Sep 2009 1459 UTC

On September 28, between 1000-1400 UTC, one of our bandwidth providers will be performing maintenance on their router in our Palo Alto, CA data center. As a result users may experience degraded performance as connections that would normally come in over this provider are routed over other paths. For Dynect traffic management customers, changes to your Palo Alto, CA site definitions are not necessary as this provider does not handle anycast traffic.

Dynect DNS and monitoring services at this site will continue to function.