yep, i agree. we have DB’s at work that can reach over 2GB before we have to perform maintenance to clean up old records from old transactions to reduce the size, improve performance, and decrease the risk of corruption.
if there is a problem with the DB, we should still be able to load a vBulletin page displaying teh SQL error message. i think it’s an issue with the web server configuration.
once in a while, i get the 500 message, other times a timeout (which is why i suggested a traceroute - maybe there are issues with their WAN provider or LAN configuration as well - an issue with the DB shouldn’t cause a complete loss of connection to the web server and break the route.)
just a thought.