At 10:10am PST on July 1st we saw two spikes in CPU for mobile dashboard queries that we believe overloaded the database. Once the CPU load went down, we were able to get the server back online. Our engineering team pushed out a fix to the problematic queries as well as a backup reader in case the system is overloaded again.