This was resolved and we are currently investigating the cause to prevent a repeat.
Update @ 10:40 - This is now resolved, apologies for the issue.