It may be entirely possible that you experienced a momentary availability affecting multiple customers in the MySQL SmartPool, referred to as the "bad neighbor effect". Although we have systems in place to handle these situations automatically, because of the shared environment of the (gs) Grid-Service, these brief outages can happen from time-to-time. Automatic procedures and our administrators, quickly took steps to resolve the issue, by bursting the offender to an isolated container, to free up load on the SmartPool.

We apologize for this inconvenience, and appreciate your patience, while we dealt with this matter. I have verified that MySQL is currently fully operational on your (gs) Grid-Service. 
You can also use a proxy server to verify the domain is still/back up. This will essentially reroute your web request through a different path than normal.

Although this is a rare occurrence, the only recommendation to completely prevent these types of outages in the future is to migrate to a (dv)Dedicated-Virtual Service or add a MySQL Container to your account. The latter gives your databases dedicated resources (cpu, memory, storage) and does not rely on the shared resources of the MySQL SmartPool of the (gs). You can learn more about MySQL containers at the (mt) Media Temple website:

http://mediatemple.net/webhosting/gs/features/containers.php#mysql

If you have any further questions regarding your (mt) Media Temple services, please feel free to contact us at any time.

It may be entirely possible that you experienced a momentary availability affecting multiple customers in the MySQL SmartPool, referred to as the "bad neighbor effect". Although we have systems in place to handle these situations automatically, because of the shared environment of the (gs) Grid-Service, these brief outages can happen from time-to-time. Automatic procedures and our administrators, quickly took steps to resolve the issue, by bursting the offender to an isolated container, to free up load on the SmartPool.

We apologize for this inconvenience, and appreciate your patience, while we dealt with this matter. I have verified that MySQL is currently fully operational on your (gs) Grid-Service. If you continue to see an error message or unable to view your domain, it may be that your browser or DNS, has cached the incorrect result.

Clearing Your Browser's Cache
http://kb.mediatemple.net/questions/726

Flushing DNS Cache
http://kb.mediatemple.net/questions/1664

You can also use a proxy server to verify the domain is still/back up. This will essentially reroute your web request through a different path than normal.

proxify.com
anonymouse.org
downforeveryoneorjustme.com

Although this is a rare occurrence, the only recommendation to completely prevent these types of outages in the future is to migrate to a (dv)Dedicated-Virtual Service or add a MySQL Container to your account. The latter gives your databases dedicated resources (cpu, memory, storage) and does not rely on the shared resources of the MySQL SmartPool of the (gs). You can learn more about MySQL containers at the (mt) Media Temple website:

http://mediatemple.net/webhosting/gs/features/containers.php#mysql

If you have any further questions regarding your (mt) Media Temple services, please feel free to contact us at any time.

Database connectivity problems (HUGE)

mysql, database, support

Other