The PHP developers recently released versions 5.4.38 and 5.5.22 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers within 24 hours.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
2:16 PM Pacific time: We’re receiving scattered reports that some Comcast users, particularly in the San Francisco Bay Area, are unable to reach some sites on our servers (but others are fine).
This appears to be a general Comcast problem; there are many similar reports on Twitter unrelated to us.
Update: The problems were resolved by Comcast at 4:23 PM Pacific time, according to several Internet reports and our own testing.
Between 9:00 PM and 11:59 PM Pacific time on Friday January 30 2015, the MySQL database software on each of our servers will be upgraded from version 5.5.40 to 5.5.41. This will cause an approximately 60 second interruption of service on each MySQL-using customer Web site at some point during this period.
This upgrade is necessary for security reasons. We apologize for the inconvenience this causes.
Update 9:57 PM Pacific time: The maintenance was completed and all services are running normally.
The PHP developers recently released versions 5.4.37 and 5.5.21 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers within 24 hours.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
Between 10:00 PM and 11:59 PM Pacific time on Saturday, January 24, each of our hosting servers will be restarted. This will cause a brief interruption of service (less than 10 minutes) for each site at some point during this 2 hour period.
Although we haven’t offered the long-obsolete PHP 5.2 series to new customers for some time, some who signed up long ago are still using it.
(New customers have defaulted to using PHP 5.5 for the last few months, and PHP 5.3 was the default for several years before that. We’ve also previously nagged everyone still using PHP 5.2 by e-mail, asking them to upgrade to at least PHP 5.3.)
For those customers still using PHP 5.2 despite the nagging, this is just a quick note that we’ve “rebuilt” PHP 5.2.17 for technical reasons to allow it to keep running on our systems. It now uses slightly newer versions of various libraries, including libxml, FreeType, ImageMagick, MySQL, and OpenSSL. The rebuilt version will be deployed on all our servers within the next few hours.
These changes should not be noticeable. In the unlikely event you experience any trouble, don’t hesitate to contact us.
The PHP developers recently released versions 5.4.36 and 5.5.20 that fix several bugs. We’re upgrading PHP 5.4 and 5.5 on our servers as a result. This will be complete on all servers by 5 PM Pacific time on Monday (January 6).
In addition, PHP 5.3.29 has been upgraded to use ionCube Loader 4.7.3.
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
The PHP developers recently released versions 5.3.29, 5.4.34, and 5.5.18 that fix several bugs. We’re upgrading PHP 5.3, 5.4 and 5.5 on our servers as a result (this will be complete on all servers within 24 hours).
These changes should not be noticeable, but in the unlikely event you experience any trouble, don’t hesitate to contact us.
Between 9:00 PM and 11:59 PM Pacific time on Friday October 24 2014, the MySQL database software on each of our servers will be upgraded from version 5.5.38 to 5.5.40. This will cause an approximately 60 second interruption of service on each MySQL-using customer Web site at some point during this period.
This upgrade is necessary for security reasons. We apologize for the inconvenience this causes.
Update 9:23 PM Pacific time: The maintenance was completed and all services are running normally.
Between 5:29 and 5:42 PM Pacific time, one of our upstream network providers had connectivity problems, causing many people to be unable to reach any of our servers.
We have resolved this by removing that provider from our network while we investigate the issue with them, and all services are now working normally.
