DynStatus

More EveryDNS DDoS

Thu, 04 Feb 2010 2134 UTC

We’ve noticed a large DDoS attack targeting EveryDNS this afternoon. While we do not operate the infrastructure or network that powers EveryDNS, we are working hard with them to get back up and running. We are moving towards creating a parallel infrastructure to make EveryDNS more reliable (why we acquired them, in the first place), but have yet to do so. If you are affected by the outage and want to transfer things over to DynDNS.com, please create a DynDNS.com account and contact support@dyndns.com to set things up.

Bandwidth Provider Maintenance in Newark, NJ

Mon, 01 Feb 2010 1605 UTC

On February 9, between 1900-2100 UTC, one of our bandwidth providers will be performing maintenance on their router 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 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.

Webhop Outage

Sat, 30 Jan 2010 1238 UTC

As of 1033 UTC, Webhop was the target of a distributed denial of service (DDoS) attack. This did not cause any issues with DNS, Web, checkip.dyndns.org, and NIC update services. The Operations team has resolved the problem. Service returned at 1237 UTC.

Site maintenance in Newark, NJ - Canceled

Tue, 26 Jan 2010 1616 UTC

On January 28, between 1900 and 2000 UTC, we will be performing site maintenance at our Newark, NJ data center. In order to avoid any interruptions to the Dynect monitoring and DNS services, and DynTLD DNS services, we will be removing this site from the Dynect and DynTLD anycast pools during this period. DNS and monitoring services will continue to be served from the other locations across our network. For Dynect traffic management customers, changes to your Newark site definitions are not necessary as this traffic will be routed to other anycast sites.

Update: maintenance for this site has been canceled.

Bandwidth Provider Maintenance in Ashburn, VA

Fri, 22 Jan 2010 1641 UTC

On February 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 US East 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.

Degraded DNS Resolution from Hong Kong

Fri, 22 Jan 2010 0138 UTC

Due to a routing issue with an upstream provider, which began at approximately 2335 UTC, users may notice a degraded performance in DNS resolution 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 0240 UTC, routing issues upstream have been resolved.

Degraded Performance in Hong Kong

Fri, 22 Jan 2010 0135 UTC

Due to an issue with an upstream provider, which began at approximately 2335 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 0240 UTC, routing issues upstream have been resolved.

EveryDNS Outages (As Observed)

Sat, 16 Jan 2010 2324 UTC

For the last hour, we have been tracking reports of EveryDNS outages. While we do not operate the infrastructure or network that powers EveryDNS, we are in contact with them and working to get back in order. If you are affected by the outage and want to transfer things over to DynDNS.com, please create a DynDNS.com account and contact support@dyndns.com to get things going.

OpenSRS outage

Thu, 14 Jan 2010 2219 UTC

Beginning at approximately 2206 UTC, we started receiving errors via our interface with OpenSRS covering the following TLDs: .mobi, .com.cn, .net.cn, .org.cn, .biz, .org.uk, .me.uk, .info, .tv, and .name. Currently, there is no estimated time to repair. Changes and registrations to domains under those domains are currently unavailable.

Update: As of 2300 UTC, all services are back to normal.

Emergency Bandwidth Provider Maintenance in London

Tue, 12 Jan 2010 2212 UTC

On January 13, between 0200-0500 UTC, one of our bandwidth providers will be performing maintenance on their router in our London 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.

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

Emergency Hardware Maintenance in Ashburn, Newark, Chicago and Frankfurt

Thu, 07 Jan 2010 2221 UTC

Beginning at 1300 UTC through 1500 UTC on Sunday January 10, 2010 will be performing emergency hardware maintenance in our Ashburn, Newark, Chicago and Frankfurt data centers.

Spring Server customers in Chicago and Frankfurt will experience a brief outage of less than 10 minutes where their server instances will be unavailable.

During this maintenance window, there will be a period of approximately 10-15 minutes where the DynDNS.com website, Dynamic DNS updates, and MailHop services will be unavailable.

The Dynect Platform management portal, SOAP API, monitoring notifications and DNS modifications will be unavailable for up to 15 minutes during this time period.

DNS query resolution will continue to be served from our anycast network. Dynect monitoring activities will continue, and any necessary reporting will be delayed for this short period.

We apologize for any inconvenience.

Emergency Hardware Maintenance in Multiple Sites

Thu, 07 Jan 2010 2220 UTC

Beginning at 1530 UTC through 1630 UTC on January 8, 2010 we will performing emergency hardware maintenance in our London, Amsterdam, Hong Kong and Palo Alto data centers. At no time will more than one data center be effected.

Dynect users may experience degraded performance as queries destined for these locations are routed elsewhere on our Anycast network.

Dynect monitoring will not be affected as the monitoring from these sites will be temporarily performed from other monitoring locations.

Bandwidth Provider Maintenance in Amsterdam 2

Tue, 29 Dec 2009 1534 UTC

On December 30, between 0200-0300 UTC, one of our bandwidth providers will be performing maintenance on their router in our Amsterdam 2 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 EU Central 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.

Update: This maintenance has been postponed until January 8, 0200-0300 UTC.

E-mail Based Password Resets Disabled

Fri, 18 Dec 2009 1926 UTC

Due to increased security concerns, Dyn Inc. is taking proactive steps to further secure its Dynect Platform. As of this morning, we have disabled access to our e-mail based password reset system, to prevent compromise of customer login credentials via e-mail systems. In the event you lose your Dynect Platform login credentials, please contact our 24×7 Dynect Concierge team immediately for assistance.

Dynect Platform Systems Fully Functional

Fri, 18 Dec 2009 1439 UTC Between 4AM UTC and 7AM UTC December 18, 2009 the Dynect Platform was fully operational and the network was operating normally. Further inquiries regarding the Dynect Platform may be directed to concierge@dynect.com.

Monitoring Service disruption

Mon, 14 Dec 2009 1758 UTC

Beginning at approximately 17:00 UTC, and ending at 17:07 UTC we experienced a traffic spike in 5 of our data centers. During this time, Dynect monitoring services from these particular locations were affected. 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.

Our operations team is evaluating the situation. At this time all services are fully functional.

We apologize for any inconvenience.