Between 7:56 and 8:19 AM Pacific time today (August 26, 2022), a network outage at our data center caused most sites to be unavailable.
The underlying cause of the problem has been identified and resolved, and should not recur.
We apologize to our customers affected by this incident: we take reliability seriously, and don’t consider any outage normal or acceptable.
Between 5:18 PM and 5:41 PM Pacific time today, our “My Account” control panel was intermittently unavailable. This problem has been fixed and services are operating normally; we apologize for any inconvenience this caused.
Between 4:06 PM and 5:03 PM Pacific time today (Aug 22, 2019), sites hosted on the “web08” server were intermittently unavailable due to a technical problem.
The problem was caused by a flood of connections that our systems failed to automatically block as they should. We’ve modified the software that handles this, and we do not expect the problem to recur.
We sincerely apologize to customers affected by this problem; we don’t consider it normal or acceptable, and strive to avoid incidents like this.
There was an intermittent interruption of service for certain customers this morning (July 23rd, 2019) from about 9:15 AM – 10:00 AM Pacific Time.
During this time, a hardware failure in a router at one of our upstream data providers would have dropped incoming traffic for sites hosted in the 74.114.88.0/22 IP address range.
Once aware of the issue, we were able to reroute all traffic for that range through our own routers directly and avoid the issue. We’ve confirmed with the upstream provider that the faulty hardware has been identified and replaced.
We apologize for the trouble this caused customers who were affected.
There was a brief interruption of service for customer websites on the “web11” server this morning (March 20, 2019) between 7:24 AM and 7:34 AM Pacific time. (Other servers were not affected.)
This problem was caused by a bug in a script that resulted in a configuration error. The bug has been fixed so that it will not recur.
We apologize for the trouble this caused customers who were affected.
Between 10:58 and 11:09 AM Pacific time today (October 19, 2018), the “web03” server experienced an outage that led to an interruption in service for some customer websites and email.
The problem has now been resolved, and other servers were not affected. We apologize for the inconvenience this caused our customers.
We’re investigating the root cause (a Linux “kernel panic”) to ensure it does not recur.
Between 5:58 and 6:04 AM Pacific time today (June 1, 2018), the “web04” server experienced a partial outage that led to some sites being unavailable or slow to respond.
The problem has now been resolved, and other servers were not affected. We apologize for the inconvenience this caused our customers.
Between 6:06 PM Pacific time (December 28 2017) and 05:15 AM Pacific time (December 29 2017) some Web sites on our web13 server were inaccessible for periods of time due to MySQL database corruption problems. During that time customers will likely have experienced a “Error Establishing Database Connection” message when viewing their Web site.
By 8:49 PM Pacific time (December 28 2017) most Web sites were working although a small number needed databases manually restoring by our technicians. That process was completed by 05:15 AM Pacific time (December 29 2017).
We don’t consider this acceptable and will strive to make sure this doesn’t recur. Finally we apologize for the inconvenience this caused.
Between 5:10 and 5:23 PM Pacific time today (Nov 14, 2016), the “web12” server was intermittently unavailable due to a hardware failure.
The problem has now been resolved, and other servers were not affected. We apologize for the inconvenience this caused our customers.
Between 4:38 and 5:11 AM Pacific time today (September 26, 2016), one of our upstream network providers had intermittent packet loss that may have caused slow performance when accessing our servers.
This problem has been resolved by the provider. Please accept our apologies for any trouble this caused.
