The outage appears to have been caused by an automatic failover in our image database, where our servers could not establish connections to the new database instance. We've restarted affected services, and activity is returning to normal. We'll continue to monitor the situation.
Posted Apr 12, 2016 - 08:00 AEST
Identified
The issue has been identified and a fix is being implemented.