We are monitoring the database service going forward, we know this issue is being caused by the high processing needs of our content processing service however we're unable to switch the processing onto a more efficient connection type due to a bug we have yet to identify. We hope that once we complete the software update to Mastodon this bug should be resolved.
