DynStatus

dyndns

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.

dyndns

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.

dyndns

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.

dyndns

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.

dyndns

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.