MoFuse Premium may become unresponsive for a short period tonight while we continue our large infrastructure migration.
Downtime, if any, will be short. Not all users or mobile sites will be affected.
MoFuse Premium will be offline for a few short minutes sometime after 1am ET.
This is scheduled maintenance that requires one of our database servers be taken offline.
MoFuse Premium is undergoing scheduled maintenance. We are not accepting new users, or allowing users to login between 1:30am and 8:30am ET. (updated)
This should not affect your mobile site. Your mobile site will continue to work and function during this period.
Any questions please email: support@mofusepremium.com
You should start to notice your mobile sites coming back online now.
We are still doing work, so the service may be interrupted as we continue to do maintenance on our servers.
Status update on MoFuse for Blogs from Founder David Berube.
We are aware of the problems with some mobile sites not displaying.
We are working on this issue and fully expect all mobile sites to be back online any moment now.
Note: This does not affect MoFuse Premium customers.
We needed to do a quick reboot of the entire MoFuse for Blogs network. This was is an unscheduled maintenance that is needed to complete an upgrade to our network.
Everything will be back to normal in a few minutes.
This does not impact the MoFuse Premium Network or any Premium customers.
We’re sorry, but the upgrade has obviously taken longer than expected. It will be back shortly.
UPDATE: We should be back by 3pm EDT, although we’re shooting for earlier.
For MoFuse Premium, click here.
Your mobile sites that are hosted with MoFuse for Blogs may be down for a short period tonight as we are doing unscheduled maintenance on the mobile web site servers.
The mobile web site servers will be back online sometime between 8 am and 12pm(Noon) EDT Saturday June 27, 2009.
We are aware that for some users, accessing analytics on the MoFuse for Blogs platform can take a while to load or not load at all.
We are working to resolve this.
