Please check here for updates on this server’s status.

Update: 02:19 AM PST. it looks like the problem was with the raid controllers BBU that was preventing it from booting. It has been replaced and should be back up shortly.

Update 02:30 AM PST. Ok the server and all its services should be restored.

If anything goes horribly wrong, all services will be affected except this blog! It will be updated with information if anything happens.

Edit: 1:45 AM Saturday April 11th Success! We migrated over 6 links to a new router and all is working hunky dory near as we can tell! Please contact support if you are having any problems.

Please stay tuned for updates.

Update: 16:55 April 7th: First off we would like to apologize for the recent database errors we have been experiencing that cause your panel access to go down. We are getting all our heads together to try to resolve these central database issues once and for all. We have stabilized the central database machines now and we are working on finding the source of these issues. All services are up and running currently but we are watching the database closely. Once again we are really sorry about the problems this has caused you and we aim to have this repeat issue completely resolved as soon as possible.

appa arizona astore bambi barqs brisk cactuscooler caprisun chai chunky coffee crush crystallight culligan dietrite dominion doubleosting downside espresso fanta fiji flipside frappe fresca fuze gingerale grapico hansens hiball horchata ibc inko koolaid ksharpie ladyanne lipton martinellis minutemaid mountaindew nehi nesbitt odwalla oj orangebang ovaltine perrier pinoysoft pom powerade propel ps5035 rakofi refresco right riptide rootbeer samhall schweppes shasta smoothie sobe sonsuztasarim sprite stewarts tampico tea tropicana trs voss welchs yoohoo zoot

Should be resolved shortly. You can check this by going to the panel > Account Status > Your Email Server. If it’s listed as “Spacey” this may be affecting you.

We will keep you updated!

Update 5:42PM: The issue with the filer is now resolved and everything should be up and running now. If you’re still experiencing issues, please contact our support team!

If you have our “AutoPay” feature enabled you can leave things as they are because the system will re-attempt to process your charge weekly until it goes through successfully. We do have a 60 day billing grace period, so as long as your account is settled within 60 days it won’t be suspended.

If you’re trying to make a manual payment please wait a few hours and try again.

We apologize for the inconvenience.

UPDATE: 7:50 PST - It looks like we’ve got this problem resolved. Manual credit card payments are being processed successfully again. We suspect that “AutoPay” payments will go through normally as well. We’re still going to keep an eye on this for a while - just in case.

For those of you whose accounts were up-to-date and had just this previous “AutoPay” payment fail you can leave things as they are and the system will automatically attempt to process the charges next week. However, if you were behind on your payments you should make a manual payment immediately or risk having your account suspended for non-payment by the system.

Update Sat October 11th, 2008. 12:02 PM PST This issue was resolved minutes after the initial post. Our admins had to restart courierauthd on all mail machines on our network. Sorry for the delayed update.

This is a reminder about the network maintenance we will be performing July 11, 2008 starting at 10pm Pacific time. All of DreamHost will be inaccessible during this downtime, including email, websites, jabber, streaming, mysql, etc. No data will be lost during this time, and email will be deferred until the network is back online and delivered over the course of the night by the sending servers.

Update 7/12/08 12:32am PDT:
The network was back up briefly before being taken down by an unexpected hardware fault on one of the central routers. It’s currently coming back up and with any luck, things will be returning to normal shortly.

Update 7/12/08 2:58am PDT:
Everything’s been back up for a while now and we’ve been monitoring everything very closely. From what we can tell, the previous issues are all gone and everything’s running smoothly. We’ll continue to monitor the network very closely over the next 24 hours to be absolutely certain no strangeness pops up.

We now have a critical patch from our file server vendor which they believe will fix the crashing problems we’ve had. It takes 20 minutes to install, and unfortunately requires a reboot. We’ve decided to schedule this upgrade for 11:30pm PDT tonight, Sunday April 6th, 2008. That is pretty much the lowest usage time across all our users in a week, and we’ve decided we can’t wait another week before applying this patch in order to give more notice.

Our apologies for the very short notice! We received notice that the patch was ready this morning. Hopefully by midnight (PDT) tonight, Blingy will finally be happy again…

UPDATE 12:15AM PDT:

Still haven’t started the upgrade yet.. it took them a little longer to get the patch than expected, however, we should have it in the next 2 minutes, and then the upgrade will begin, probably around 12:30 now, and be done before 1am Monday morning PDT. Hang in there!

UPDATE 12:54AM PDT:

A few more bumps! Still no changes.. and now we’re afraid we’ll have to push off the upgrade to about 1:45AM (9:45AM GMT) it looks like.. hopefully all finished by 2:15AM PDT (10:15AM GMT), our apologies to blingy customers in Europe.

UPDATE 02:10AM PDT:

All done! The actual reboot only took about 3 minutes, and then there were some residual effects from the reboot on various web and mail servers for up to ten minutes after that. But things seem settled down now and the upgrade “took”. We all hope it did the trick. BIG TIME.

I apologize for this mistake. I was intending to be editing our non-live access-list, and edited the live one by mistake.

Update 9:54 PM Pacific: We have unblocked the firewall and our routing is coming back online. Sites should start working again as soon as our router finishes loading its tables. I use “resolving” because it is still processing the routes.

Update: Things seem to be working again, we apologize for the outage.