DynStatus

Credit Card Processing Issues

Our credit card processing service is currently down. It is unclear at this time what the exact nature of the issue is. We will update you when we have more information.

While it is down, credit card authorizations are failing. Please try your purchases again later. We are sorry for any inconvenience.

Update: There has been a fire at the main datacenter of our credit card processor. They are working to restore service. We have made adjustments to place orders on hold until our credit card processor can accept transactions again.

Update: We have disabled DynDNS service expirations and auto-renewals until this issue has been resolved. We are unable to prevent domain expirations at the registry, but if you have a domain registered through us that is expiring in the next 24 hours, please contact support and we will manually renew it for you.

Update: Our credit card processor is back on line and orders are processing again. We have processed any orders that were placed on hold and appreciate your patience. Regular processing for auto-renewals had been enabled. We are leaving expirations for DynDNS services disabled until Monday so that our users who may have had trouble renewing services this morning will have time to get back online over the holiday weekend.

MailHop Outbound Issue

Some customers have reported an issue with MailHop Outbound. These customers are receiving notification that they have gone over quota, when it appears that they have not. We are currently investigating this situation and working hard to resolve it as soon as possible. We apologize for any inconvenience this may cause.

This issue has been resolved. We again apologize for the inconvenience this may have caused.

Corporate Mail Server Maintenance

Between 1400 UTC June 27 and 2000 UTC June 28, we will be performing various upgrades to our corporate mail servers. Throughout this maintenance, there may be brief periods of time during which delivery of mail to employees of Dynamic Networks Services could be slightly delayed.

Maintenance on Tata Upstream Connections

We will be performing maintenance on our Tata Communications (AS6453) connections today, to enable full dual stack IPv4/IPv6 connectivity to all Dyn Inc PoPs. To complete this, Dyn Inc will be adjusting IPv4 routing between PoPs to ensure no outages occur. This may result in short events as we adjust routing, however, no outages are expected.

Update: Routing maintenance at our PoPs is complete as of 1955 UTC.

Amsterdam site offline for maintenance

One of our Amsterdam sites is currently down for unplanned maintenance. All DNS traffic has been rerouted to our other anycast nodes so there has been no interruption to services.

Update: As of 2000 UTC, our Amsterdam site is back in our anycast pool and is answering queries.

Corporate Mail Server Maintenance

Beginning at 0100 UTC on June 25, we will be performing upgrades to our corporate mail servers. We expect this maintenance window to last for no more than two hours. Actual downtime for our mail servers will be approximately one hour. During this time, mail to employees of Dynamic Networks Services will be accepted and queued, but delivery will be delayed.

Scheduled DynDNS database maintenance

On Thursday, June 25, 2009, between 0000 and 0030 UTC, we will be performing routine maintenance on the primary database server for DynDNS.com. The actual outage will be brief and not occur during the entire window. During this time, attempts to login to the website may fail or be delayed.

Update: This maintenance work is complete as of 0030 UTC.

ns3.pXX.dynect.net Routing Maintenance

On Friday, June 19, 2009, between 1200 and 2000 UTC, we will perform routing maintenance on the ns3.pXX.dynect.net nodes. This maintenance window will afford us the opportunity to adjust anycast routing for these nodes, which will result in increased global coverage and decreased latency. No outages of ns3.pXX.dynect.net are expected, although there may be slight deviations in latency as routing re-converges.

Update: This maintenance work is complete as of 2000 UTC

Emergency DynDNS.com Database Maintenance

At approximately 1620 UTC, we experienced a failure of our database server in our Newark datacenter. This problem led to a brief outage of our DynDNS.com website and nicupdate services. All other services were unaffected. This problem has been repaired and all services are online.

We apologize for any inconvenience this has caused.

Emergency Database Maintenance

At approximately 0513 UTC, we experienced a failure of our primary database server in our Newark datacenter. This problem led to an outage of our DynDNS.com website and nicupdate services. All other services were unaffected. This problem has been repaired and all services are online.

We apologize for any inconvenience this has caused.

Corporate Mail Server Maintenance

Beginning at approximately 0000 UTC on Jun 11, we will be performing upgrades to our corporate mail servers. We expect this maintenance window to last for several hours. During this time, mail to employees of Dynamic Networks Services will be accepted and queued, but delivery will be delayed.

For DynDNS.com users, mail to support@dyndns.com and PS cases will continue to work normally.

Anycast Node Maintenance Notice

On Wednesday, June 10, 2009 between 0600 and 1000 UTC our US west coast anycast node will be offline due to maintenance activity by our colocation provider. All anycasted traffic will be rerouted to another site during the maintenance, and no interruption of service is expected.

New Anycast Node & Dynect Traffic Manager Site Maintenance Scheduled

On Monday, June 8, 2009 from 14:00 – 15:00 UTC we will perform maintenance on the Dynect Nameserver Infrastructure. This work is being scheduled to bring up an additional anycast DNS node in Newark, NJ. During this window ns1.pXX.dynect.net may not answer DNS queries for short periods of time while our engineers adjust our anycast routes to bring the new node online. We do not expect any degradation of service as DNS queries will be answered by our other redundant nodes (ns2.pXX.dynect.net, ns3.pXX.dynect.net and ns4.pXX.dynect.net).

The node is now monitoring Dynect Failover, Load Balance and Traffic Management Services. In addition, the site is available now in the Dynect Traffic Management system for configuration. Users may pre-configure Balancing Rules for the Newark, NJ site prior to our bringing this node on line to take immediate advantage of this new node on the US East Coast. Otherwise, we will serve your Global definition rule as we do for any un-configured rulesets.

While we expect this maintenance to be transparent to your operations, we wish to properly inform you of this work. All work during this time is fully scripted per our standard operating procedures.

DynDNS.com Account Login Difficulty

Some users are currently experiencing difficulty logging in to their accounts to make changes and purchase services at DynDNS.com as a result of recent site enhancements made today. We are actively working on this issue, and expect to have it resolved momentarily.

Update: DynDNS.com accounts with passwords containing capital letters were not able to login to their accounts on DynDNS.com for approximately 10 minutes. All logins are operating normally as of 1950 UTC June 3. We apologize for the inconvenience.

Dynect Platform ns2 and ns4 performance degradation

At 0925 UTC June 2 , the Dyn Inc. NOC noticed degraded performance from our NYC PoP for Dynect Platform customers affecting the ns2 and ns4 nameservers. The source of the performance degradation is due to a failure in an upstream router at our colocation provider. As a result, Dyn Inc. Operations has re-routed all ns2 and ns4 traffic away from NYC, to our other redundant anycast sites.

Update:As of approximately 0240 UTC June 3, all equipment is back online and our NYC PoP is announcing routes for our anycast network. DNS queries are once again being served from this location.

DynDNS Registration Issues.

This is evening at approx. 00:29 UTC there were some minor domain registration issues which caused an error to be reported from the DynDNS.com website. This issue lasted about 30 minutes after which it was resolved by our Operations Team. Customers are encouraged to simply retry their requests.

MailHop Relay Rejections

There was a configuration error on one of our MailHop servers that may have caused mail delivered to this particular server to be rejected. This configuration error only affected MailHop Relay customers that made changes to their configuration after May 28th. The rest of the MailHop servers were not affected by this problem. The problem has been resolved and we apologize for an inconvenience this may have caused.

DDoS Against MyDynDNS Nameservers

At approximately 1000 UTC today the MyDynDNS nameservers became the targets of a distributed denial of service attack. These nameservers provide DNS service for our Custom and Secondary DNS products. During the attack there were brief outages of ns1.mydyndns.org and ns5.mydyndns.org, though not at the same time, and at no time were all five nameservers offline.

Service was restored at approximately 1115 UTC and all services are currently working normally.

Emergency Database Maintenance

At approximately 1905 UTC, we experienced a failure of our database server in our Newark datacenter. This problem led to an outage of our DynDNS.com website and nicupdate services. All other services were unaffected. This problem has been repaired and all services are online.

We apologize for any inconvenience this has caused.

nsX.mydyndns.org DDoS Attacked

Between approximately 1230-1330 UTC, the mydyndns.org name servers came under the fire of a distributed denial of service (DDoS) attack. During this period, ns4.mydyndns.org and ns5.mydyndns.org may have been unavailable from some locations but DNS resolution continued from our redundant datacenters. Dyn Inc Operations has taken steps to mitigate the attack and DNS resolution is now performing as expected across our network.

Voice Mail Delays

Today we discovered a problem in which voicemail messages to both support and individuals at Dyn-Inc were received and queued in the phone system, but not delivered to the recipient. We have corrected the problem and voicemail is now processing normally. Messages were not lost, merely delayed.

If you have recently left a message for support, someone from our support team will get in touch with you as soon as we can. We apologize for any inconvenience this may have caused and will be taking steps to prevent this from happening in the future.

Maintenance in Hong Kong

On Tuesday, May 19, 2009 between 1400 and 1500 UTC, we will be performing firmware upgrades to our switching hardware in our Hong Kong facility. This will result in a brief site-wide outage. Expected downtime is less than a minute. This may affect ns5.dyndns.org and ns5.mydyndns.org. Anycasted Dynect services in this facility will be routed elsewhere during the outage. All other services will be unaffected. The other four nameservers will continue serving Dynamic, Custom, and Secondary DNS normally.

Yahoo Blocking Confirmation Emails

Yahoo is currently blocking e-mail originating from our web site, including account creation confirmation messages. We have requested that they unblock our servers.

In the meantime, if you are creating a new account, please use a non-Yahoo address to ensure that you receive your confirmation e-mail to complete the account creation process.

Update:As of May 18th, Yahoo is no longer blocking e-mail originating from our web site.

Offline.dyndns.org DDoS Attack.

At 21:56 UTC, offline.dyndns.org was the target of a distributed denial of service (DDoS) attack. The attack lasted until 22:20 UTC. 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 have temporarily disabled offline.dyndns.org. The rest of the services are back to normal.

Update: As of 0600 UTC, offline.dyndns.org is back online.

MailHop Forward and Relay Blocked by AT&T

AT&T has blocked all mail coming from the MailHop Forward and Relay servers. We have contacted them, requesting the block to be removed. We will update this status posting when we have further information.

Due to the amount of mail that MailHop Forward users have reported as spam, AT&T has currently stated that they will not unblock our servers. We are continuing to try to work with them on this issue. Please note that when you report an email we forward for you as spam, AT&T sees our servers as the spam source and not the actual original source.

Planned Maintenance in Hong Kong

On Thursday, May 14, 2009 between 2100 and 2200 UTC we will be performing firmware upgrades to our switching hardware in our Hong Kong facility. This will result in a site-wide outage. Expected downtime is less than a minute. This may affect ns5.dyndns.org and ns5.mydyndns.org. Anycasted Dynect services in this facility will be routed elsewhere during the outage. All other services will be unaffected. The other four nameservers will continue serving Dynamic, Custom, and Secondary DNS normally.

Update:This maintenance was rescheduled.

Maintenance in Newark

We are preforming routine maintenance in our Newark, NJ facility this week which may result in a few servers being offline for brief periods of time starting on Wednesday, May 13, 2009 and ending on or before Friday, May 15, 2009. These outages will be very brief, less that 5 minutes per server. This may affect ns1.dyndns.org, ns1.mydyndns.org, and MailHop Outbound. All other services will be unaffected. The other four nameservers will continue serving Dynamic, Custom, and Secondary DNS normally.

ns1.dyndns.org DDoS Attacked

At 1800 UTC, ns1.dyndns.org came under the fire of a distributed denial of service (DDoS) attack. Dyn Inc Operations is currently taking steps to mitigate the attack. DNS resolution service to ns1.dyndns.org was temporarily unavailable for approximately 45 minutes, however, DNS resolution continued from our redundant datacenters.

Dynect NS2 Nameservers Routing Changes complete

Our routing changes for the ns2.p##.dynect.net have been completed.

This concludes our maintenance for the routing modifications. We are continuing to monitor DNS traffic and will make minor modifications as necessary.

There was no downtime for DNS resolution during this time.

Dynect NS4 Nameservers Routing Changes complete

Our routing changes for the ns4.p##.dynect.net have been completed. We continue to make minor tweaks to improve performance.

There was no downtime for DNS resolution during this time.

Dynect Nameserver Maintenance Starting

We are starting our adjustment of anycast routes for nameservers ns2.pXX.dynect.net and ns4.pXX.dynect.net.

During this time each of these nameservers may not answer DNS queries for short periods of time. At no time will more than one nameserver be impacted. We do not expect any degradation of service as DNS queries will be answered by our redundant nodes (ns1.pXX.dynect.net and ns3.pXX.dynect.net).

Update: At 3:14pm EDT we completed our maintenance period.